How AgentMessage handles 10DLC for you
About a 2-minute read.
10DLC involves several parties: you, AgentMessage, a central registry, and three wireless carriers. You only ever deal with AgentMessage. Here's what's happening behind the scenes, so you understand what you're responsible for and what we do.
What you do
- Provide your business information through the brand registration form.
- Provide your campaign details: use case, how people opt in, sample messages, and your HELP/STOP behavior.
- Publish a compliant privacy policy and terms on a live URL (the carriers check them).
- Wait for approval, then attach your numbers and start sending.
What AgentMessage does
- We're a registered Campaign Service Provider (CSP). That means we can file brands and campaigns directly with The Campaign Registry (TCR), the central database every US carrier reads from. Your registration lives there, filed by us on your behalf.
- We give you a guided flow instead of a raw registry form. You fill out plain fields in the dashboard; we translate them into what the registry expects and submit them.
- We track the outcome and surface it to you. Brand verification and campaign approval happen asynchronously. We reflect the status in the dashboard and can push webhook events (brand vetting, campaign approval) to your application.
- We connect your phone numbers to the approved campaign so carriers know your traffic is allowed.
- We pass carrier fees through at cost. Per-segment carrier surcharges are set by the carriers, not by us, and we don't mark them up. See What it costs.
What we don't do
- We don't write your privacy policy or terms. Those have to come from you or your counsel. We can tell you what they need to contain, see Privacy policy and terms, but we can't generate them.
- We don't override carrier decisions. If a carrier rejects or suspends a campaign, we help you understand why and resubmit, but we can't force an approval.
- We can't register a business without an EIN. The EIN-less sole-proprietor lane isn't supported. See I don't have an EIN.
Who decides what
When something is rejected, it helps to know who decided it:
- AgentMessage, we validate your submission before and as we file it, and we're the layer you talk to. If something's fixable, we'll tell you what.
- The Campaign Registry (TCR), holds your brand and campaign records and runs the identity check that makes a brand "Verified."
- The carriers (AT&T, T-Mobile, Verizon), review campaign content and make the final call on approval, throughput, and suspensions.
The status and any reason we get back appear in the dashboard. If a rejection isn't clear, How rejections work walks through it.
When to handle it yourself vs. reach out
Handle it yourself:
- Writing your use case, CTA, samples, privacy policy. The campaign guides cover these.
- A brand that came back Unverified for a name/EIN mismatch, the fix is in your hands.
Reach out to us (we handle these directly today):
- Editing or deactivating an existing brand or campaign.
- Re-verifying a brand or appealing a verification result.
- A carrier suspension.
- A use case that isn't in the dropdown (charity, political, emergency, etc.).
- Needing a large pool of numbers on one campaign.
- Moving registrations from another provider.
Full list: When to contact support.