How to check your A2P 10DLC registration status

Why you need to check status before go-live

You filed A2P 10DLC registration days ago. Workflows are built. Reminders and missed-call text-back are ready to flip on. Then a customer says they never got a message — and your platform still shows "sent." The leak is not your automation logic; it is registration that never finished or a number that was never linked to an approved campaign.

US carriers gate business SMS on local 10-digit numbers behind brand and campaign approval. The 10DLC dashboard is where you see whether carriers actually accepted your filing — not whether your CRM thinks messages left the server. Checking status takes five minutes and prevents a week of silent delivery failures.

What to look for in the 10DLC dashboard

Every compliant SMS provider exposes a compliance or Trust Center area with three status layers. All three must be green before you treat SMS as production-safe:

• Brand status — your legal business (EIN, name, address) verified against carrier records. States: draft, pending review, approved, or rejected.
• Campaign status — your declared use case (reminders, customer care, marketing) plus sample messages with opt-out language. Same state labels as brand.
• Number linkage — each local number that sends SMS assigned to an approved campaign. A number can show "active" in your phone list but still be unregistered for A2P until linked here.

If you are unsure which items you still owe, run the A2P 10DLC readiness check — it mirrors what support teams ask when texts stop delivering and points you to the exact gap.

What each status means (and what to do)

Draft / not submitted — you started the form but never paid or submitted. Finish brand first, wait for approval, then submit campaign.

Pending / in review — carriers or the registration partner are reviewing. Brand usually clears in one to three business days; campaign often one to five more. Do not resubmit duplicate brands while pending — that creates EIN conflicts.

Approved / verified / active — that layer passed. Confirm the other two layers and number linkage before enabling workflows.

Rejected / failed — read the reason code in the dashboard notification. Fix only what they cite (name mismatch, vague use case, missing "Reply STOP" in samples), resubmit, and budget another review cycle. Full rejection playbook: A2P registration guide — rejection fixes.

Number unregistered / not linked — campaign may be approved but the sending number was never attached. Link the number to the approved campaign in the dashboard, wait for sync (often minutes, sometimes overnight), then retest on a real handset on a different carrier.

Check A2P 10DLC status in GoHighLevel (LC Phone / Trust Center)

We verify registration on live GoHighLevel sub-accounts running LC Phone — the same path most small businesses use for reminders, text-back, and review requests. Menu labels vary slightly by account age, but the Trust Center is always the source of truth.

1. Open the sub-account that owns the phone number sending SMS (agency users: switch into the client sub-account, not the agency shell).
2. Go to Settings → Phone Numbers. Find the Trust Center, A2P 10DLC, or Messaging Compliance tab — often a banner on this page if registration is incomplete.
3. Check brand status. Look for Verified, Approved, or Active. If Pending, note the submit date and wait the review window before opening a ticket. If Rejected, open the notification for the reason code.
4. Check campaign status. Each campaign row shows its use case and approval state. One approved campaign can cover reminders and review requests if your sample messages match what you actually send.
5. Confirm number linkage. In Phone Numbers, select your local sending number. It should show linked to the approved campaign — not "unregistered" or "pending A2P." Assign the campaign if the dropdown is empty.
6. Send a production test. Text a colleague's mobile on AT&T, T-Mobile, or Verizon — not just your own line on the same carrier. "Sent" in Conversations without delivery on the handset means status is still wrong somewhere in the three layers above.

Compliance still applies after approval

Approved registration is not a license to text anyone. Carriers match outbound content to your declared campaign — marketing promos on a Customer Care campaign get filtered. Every recurring automation still needs opt-out handling ("Reply STOP to unsubscribe"), consent for the message type, and quiet-hours discipline on promotional sends. See how to send SMS to customers legally for TCPA basics. If messages fail after full approval, walk the delivery troubleshooting order in business texting not delivering.

What checking status costs (and what fixes cost)

Pricing checked July 2026 on GoHighLevel's LC Phone / Lead Connector flow.

• Checking the dashboard: free — it is part of your SMS provider account.
• Initial registration (if you have not filed yet): ~$4–$15 one-time brand + ~$10–$15 one-time per campaign, plus ~$0.0083 per SMS segment after approval.
• Resubmit after rejection: usually no extra fee for the resubmit itself; the cost is calendar time — another one to five business days per review cycle.

When not to live in the dashboard

Once brand, campaign, and number linkage all show approved, checking daily adds nothing — carriers do not silently revoke registration. Recheck only when delivery symptoms return, you add a new sending number, or you change message types enough to need a new campaign.

Skip SMS entirely if you are not texting US mobile numbers — email-only follow-up or WhatsApp where customers opt in does not need a 10DLC dashboard. Under ~10 customer touches a month, a personal call may beat the compliance overhead; register once when volume justifies automated SMS clusters.

Common questions

Where do I check my 10DLC registration status?

In your SMS provider's compliance dashboard — often labeled Trust Center, A2P 10DLC, or Messaging Compliance. You should see separate status lines for brand registration, campaign registration, and each phone number linked to the campaign. On GoHighLevel, open Settings → Phone Numbers → Trust Center / A2P 10DLC in the sub-account that sends SMS.

How long does 10DLC registration stay pending?

Brand approval usually takes one to three business days once your EIN and legal name match public records. Campaign approval often takes another one to five business days if your use-case description and sample messages are clear. Rejections add a resubmit cycle — budget a full week before treating SMS as production-safe.

What does "campaign approved" mean for my texts?

Carriers accepted your declared use case and sample messages. You still need your sending number(s) linked to that campaign and showing as active or registered. "Approved" on the campaign alone does not guarantee delivery if the number is unassigned or the message content does not match what you registered.

My 10DLC dashboard shows rejected — what now?

Read the rejection reason in the dashboard inbox, fix only what they cite (EIN mismatch, vague use case, missing STOP in samples, website gap), and resubmit the same brand — do not create a duplicate EIN registration. Our registration guide walks the top rejection fixes step by step.

Can I send SMS while registration is pending?

Test messages to your own phone may work; customer volume often gets filtered or blocked until brand and campaign are approved and numbers are linked. Do not promise customers SMS or turn on high-volume workflows until every status line in the dashboard shows approved and numbers are attached to the campaign.