While registration is in review, show the customer a clear "in review" state with what's happening, what they can still do and when you'll tell them the result. Poll GET /v1/registration on a slow schedule to update it. Most approvals take 2 to 7 days, so the screen has to hold up for a while without feeling broken.
The review stage is where customers get nervous. They've filled in a form, paid, and now nothing visibly happens. A good status screen costs little to build and prevents a stack of "is it working?" tickets. This guide covers the states, the copy and the polling.
Why the pending state needs design
Registration isn't instant, and you don't control the reviewers. A customer who sees a spinner for days assumes failure. A customer who sees "in review, here's what you can do meanwhile" waits calmly.
Our post on how long 10DLC takes explains the timeline. Your job in the UI is to make the wait legible.
Four states to show
Map whatever the registration status returns into a small set of states of your own. Keep the number low so every state has a clear message and a next step. Check the registration API docs for the exact status values the endpoint returns, and map them to these.
| Your state | What the customer sees | Their next step |
|---|---|---|
| Not started | "Turn on texting" with a short form | Fill in business details |
| In review | "Your registration is in review" | Nothing required, keep using the app |
| Approved | "Texting is on" | Send messages |
| Needs changes | "We need a fix before it can be approved" with the reason | Edit and resubmit |
Resist adding a fifth "processing" state. If two internal statuses mean the same thing to the customer, show one state.
Copy you can reuse
Write for a non-technical owner. Say what's happening, then what it means for them.
In review. "Your business registration is with the carriers for review. Most approvals take 2 to 7 days. We'll email you when it's done. You can keep setting up your account while you wait."
Approved. "You're registered. Your texts now go out."
Needs changes. "The carriers asked for a change. Here's what they said: [reason]. Fix it and resubmit. Nothing is lost."
Avoid jargon like TCR, brand score or campaign ID on the main screen. Put those in a "details" expander for the one person in a hundred who wants them. If a rejection happens, our guide to decoding a rejection and resubmitting helps you write specific, useful reasons.
What to let them do meanwhile
A pending screen that blocks everything feels like punishment. Let customers do the work that doesn't need an approved campaign: import contacts, write templates, set up automations and invite teammates.
On sending, the rules are specific:
- An account can send up to 500 texts a month until its registration is approved. Register early, because the limit lifts on approval, not on submit.
- An account that bought its number before registering sends on Ready's shared registration at the same per-text rate while its own registration is in review.
- A card on file and a number of the account's own are required to send.
Tell customers which of these applies, and don't promise sending you can't deliver. If a send is refused, show a plain reason. Our post on pre-send refusal error UX covers wording for that.
Polling GET /v1/registration
Poll from your backend, not the browser, so the key stays on your server. One request returns the current registration status for the account.
curl https://api.tryready.com/v1/registration \
-H "X-API-Key: $READY_API_KEY" A sane schedule for a review that takes days:
- Poll once right after submission, to confirm it landed.
- Then every few minutes for the first hour, since a quick result is possible.
- Then back off to once an hour, and later a few times a day.
- Stop polling when the state is needs changes, until the customer resubmits. Keep polling an approved registration, slowly (once a day is enough): a registration that is later suspended or deregistered sends no webhook, so a poll is the only way your screen learns that texting stopped.
Subscribe to the registration_in_review, registration_approved and registration_rejected webhooks as your main signal, and use polling as the backstop. Sending opens when the brand is approved, while the campaign may still be in review, so base your "texting is on" state on can_send_registered from GET /v1/registration, not on the campaign status alone.
Store the last status you saw. Only notify the customer, by email or an in-app banner, when it changes. Add a manual "check now" button for the impatient, rate-limited on your side so it can't hammer the endpoint. If you run many customers, spread the polls out with a little random delay so they don't all fire at the same second. The API quickstart shows how keys and requests fit together.
Tell them when it changes
Polling updates your database. The customer finds out through a message. Send an email when the state becomes approved or needs changes, and show a banner the next time they open the app. For needs changes, put the reason and an edit button in the first screen they see. Don't make them hunt.
A short build checklist
- Four states, each with copy and a next step.
- A status endpoint call on your backend, with backoff.
- A stored last status, and a notification only on change.
- A "keep going" list of things customers can do while they wait.
- Clear wording on what sending is possible right now.
- A details expander for the technical fields.
Build this once and every new customer gets a calm wait. For the registration steps behind it, read the registration guide and our post on the 10DLC registration API and developer flow.