Messaging Compliance & 10DLC
Messaging Compliance & 10DLC
Grunlo sends SMS through carrier-approved routes. For US local numbers, carriers expect 10DLC (10-digit long code) campaign registration tied to your business number. Registration is handled when your dedicated number is onboarded — it is not something every tenant completes as a self-serve wizard in-app.
Why outbound SMS might be blocked
- Campaign / registration — If your sending number is not associated with an approved use case, outbound SMS may be blocked until registration is complete or corrected.
- Platform gate — The product may enforce outbound SMS rules based on registration metadata on the number record.
- Consent — Customers who have not opted in to SMS, or who have opted out, must not receive marketing texts; transactional messages should stay concise and expected.
Shared vs dedicated numbers
- Dedicated number — Messages originate from your local caller ID; branding matches your business once provisions complete.
- Shared platform number — Traffic may use the platform's sender under policies designed for trial or fallback scenarios; content may include identifying prefixes per carrier rules.
Acceptable use policy (AUP)
Before messaging features are enabled for your tenant line, an admin accepts the messaging AUP. When acceptance is needed, a card appears at the top of Settings → Phone & SMS — this applies whether you send from a shared platform number or a dedicated number, and whether or not a number is assigned yet. Updates to policy versions may require re-acceptance when the product prompts you.
Opt-out language
Marketing-style SMS should include clear opt-out instructions where required. Customers who reply STOP or use unsubscribe flows must be honored system-wide.
Getting help
If sending fails or you see registration warnings, contact support with your tenant name and the sending number — we coordinate carrier registration and compliance checks.
Related
Was this article helpful?