How KaiCalls Handles A2P 10DLC Registration So Your Texts Actually Deliver
The exact mechanics of how KaiCalls registers your business number for texting: a shared Customer Care campaign, enrollment before activation, nightly re-checks, a registered fallback sender, and the content and consent rules that keep it approved.
KaiCalls registers your number for texting before it goes live. KaiCalls holds an approved A2P 10DLC brand and a Customer Care campaign with the carriers; every KaiCalls number is added to that campaign's sender list when it is provisioned, the number is held if that step fails, the whole pool is re-checked nightly, and any text that cannot be sent from a registered number is routed through a registered sender instead. If you use a KaiCalls number, there is no form to fill out and no waiting period. If you bring your own Twilio account, you register your own brand and campaign and the dashboard tracks your status.
That is the summary. This post is the long version — the actual mechanics, including the parts that are deliberately conservative, because "we handle compliance for you" is a sentence every vendor writes and very few can explain.
If you are new to the topic, start with A2P 10DLC Explained. This post assumes you know what a brand and a campaign are.
Table of Contents
- The two ways a number can be registered
- Why KaiCalls chose a shared Customer Care campaign
- Step 1: Enrollment happens before activation
- Step 2: Nightly reconciliation
- Step 3: Registered sender or nothing
- Step 4: The rules enforced in code
- What the dashboard shows you
- If you bring your own Twilio account
- What KaiCalls does not do
- FAQ
The two ways a number can be registered
A2P 10DLC registration attaches to a phone number through a campaign. There are two ways a small business ends up with a registered number:
| Register your own | Use a provider's campaign | |
|---|---|---|
| Who files the brand | You | The provider |
| Who files the campaign | You | The provider |
| Wait before texting | 1–2 weeks | None |
| Who is responsible for staying inside the campaign's rules | You | The provider, for every number on it |
| Best for | Businesses with their own Twilio account or unusual use cases | Businesses that want a number that texts on day one |
KaiCalls uses the second model for the numbers it provides. Businesses that connect their own Twilio account use the first. Both are covered below.
Why KaiCalls chose a shared Customer Care campaign
The campaign type is the promise you make to the carriers about what your texts are. KaiCalls' campaign is registered as Customer Care, not Marketing and not Mixed. That was a deliberate choice, and it shapes everything downstream.
Customer Care covers messages to people who have already contacted the business: replying to a missed call, confirming an appointment, continuing a conversation someone started, answering a question. That is a precise description of what Kai does. He is a secretary who texts callers back. He does not run blasts.
The upside of Customer Care is that carriers treat it as low-risk, and consent is straightforward — the customer initiated contact. The cost is that the campaign has rules, and every number on it is bound by them. A single business sending promotional texts from a Customer Care number puts every other number on the campaign at risk. So KaiCalls does not leave those rules to a policy page. They are enforced in the sending pipeline, covered in Step 4.
Step 1: Enrollment happens before activation
When a KaiCalls number is provisioned — at signup, when you buy an extra line, or when a setup call assigns one — the platform immediately adds that number to KaiCalls' registered messaging service, which is the sender pool attached to the approved campaign.
This is a gate, not a background job. If the add fails for any reason, the number is marked as held, it is not activated, and the provisioning step reports the failure instead of pretending it worked. The number waits for reconciliation rather than going live as an unregistered sender.
The reason for that severity is the failure mode it prevents. Before this gate existed, a number could be handed to a business, work perfectly for calls, and silently drop every follow-up text for days because one enrollment call had failed with no one watching. Calls working made the problem invisible. The owner found out from a customer. Making registration a precondition of activation means a number that reaches you is one the carriers already know.
The number pool also prefers already-enrolled numbers when assigning one to a new business, so most signups get a number that was registered before they ever saw it.
Step 2: Nightly reconciliation
Registration state can drift. A number can be removed from a sender pool by an operator, a provider-side hiccup can leave one out, or a number can be moved between services during maintenance.
So every night, a scheduled job pulls the list of every active KaiCalls number, pulls the campaign's actual sender list from the messaging provider, and diffs them. Any active number missing from the campaign is re-enrolled on the spot. A number that is already there is left alone.
This is the boring part, and it is the part that keeps the promise honest over months rather than on the day you signed up.
Step 3: Registered sender or nothing
When Kai sends a text, the platform decides which number it goes from. Ideally that is your business number, so the customer sees the same number they called.
But the sender logic checks a condition first: is this number active and enrolled in the registered campaign? If yes, the text goes out from your number. If no — enrollment is still pending, or the number was held — the text is routed through KaiCalls' registered messaging service rather than sent from the unregistered number.
That means a text that would otherwise have been silently filtered still reaches the customer. It may arrive from a KaiCalls sender instead of your exact number during that window, which is a worse experience than normal. It is a far better experience than the customer never hearing from you and assuming you ignored them. The same check is applied whether Kai sent the text or you typed a reply from the dashboard.
Step 4: The rules enforced in code
A Customer Care campaign stays approved only if the traffic on it looks like customer care. KaiCalls enforces the campaign's rules in the outbound text pipeline, before a message is handed to the carrier. Every outbound text passes through these gates in order:
- Valid destination. The number has to be a real, properly formatted phone number.
- Content screen. Kai blocks marketing language, URL shorteners, messages over 1,600 characters, and messages that are mostly capital letters. These are the patterns that get Customer Care traffic reclassified as spam. One-time codes and account notices skip the content screen, since they are not conversational.
- Consent. The recipient must have a consent record for texts: they called, they texted, or they submitted a web form with a consent box. A number with no consent record does not get a text.
- Opt-out and Do Not Call. If the number ever replied STOP, or is on your Do Not Call list, the text is blocked. STOP always wins, even over a newer implied consent.
- Quiet hours. Texts between 9 PM and 8 AM in the recipient's local time are held and sent the next morning, not dropped.
- Rate limit. A daily cap per business and a per-recipient limit stop bursts.
- Send.
Inbound keywords are handled on every number as well. STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT mark the number opted out and trigger one confirmation reply. START, YES, SUBSCRIBE, UNSTOP, and OPTIN turn texts back on. HELP, INFO, SUPPORT, and ASSIST get a short help reply. Plain-language requests like "take me off your list" are treated as STOP. And the opt-out is saved before the confirmation is sent — if saving fails, Kai does not tell the customer they are unsubscribed. He would rather retry than confirm something that did not happen. The full behavior is documented in STOP, START, and HELP keywords.
None of this is unique to KaiCalls as a set of rules. Every registered campaign is supposed to work this way. What is worth knowing is that on KaiCalls they are gates in the sending code, not guidance to the business owner.
What the dashboard shows you
Under Dashboard > Compliance > A2P Setup, a business on a KaiCalls number sees a status card confirming that texts are sent through KaiCalls' registered campaign and no additional setup is required.
If a number's enrollment is still pending, the dashboard's activation status reads "Live for calls. SMS follow-ups are limited until A2P registration completes." Calls work normally during that window — registration only affects texting — and the note clears once the number is on the campaign. If it does not clear within a business day, that is worth a message to support, because it means reconciliation has not caught it either.
You can also confirm delivery yourself in about a minute: call your number from your cell, hang up before Kai answers, and watch for the missed-call text. Then open Dashboard > Messages and check that it shows as delivered. The step-by-step is in the A2P help page.
If you bring your own Twilio account
Some businesses connect their own Twilio account so their numbers live in an account they control. That changes who has to register: the numbers are yours, so the carriers need your brand and your campaign. KaiCalls' campaign does not cover numbers in someone else's account, and KaiCalls cannot file a brand or campaign on your behalf inside your Twilio account.
For those businesses, the A2P Setup page switches to a tracker. It lists what to gather — legal business name, EIN, address, authorized contact, use case, sample messages, keyword replies, and a consent description — shows your current status, and links directly to the Twilio console where you file. Brand review commonly takes one to two business days; campaign review three to five more.
The campaign filing is where most people get rejected, usually for a fixable wording problem. We wrote up what we learned in How to Write an A2P 10DLC Campaign That Gets Approved. Choose Customer Care as the type if the texts are replies and follow-ups, and make sure every number you want Kai to text from is attached to the messaging service tied to that campaign — a number outside it is unregistered even if the campaign is approved.
What KaiCalls does not do
Being precise about the edges is the point of this post.
- Registration does not make every text deliver. It makes carriers trust the sender. Content that looks like spam can still be filtered from a registered number, which is why the content screen exists.
- KaiCalls does not run toll-free verification. Toll-free numbers use a separate process from 10DLC. Ask support before choosing a toll-free number you plan to text from.
- KaiCalls does not file brands or campaigns in your Twilio account. It tracks status and tells you what to gather. The filing is yours.
- You cannot customize the keyword list or the STOP/HELP reply text per business today. They are the same on every KaiCalls number, which is also what keeps them consistent with what was registered.
- None of this is legal advice. Registration and consent tooling reduce the chance of a mistake and keep a record. Deciding who your business should be contacting is still your call. See How KaiCalls Handles TCPA, Do Not Call, and A2P Compliance for where that line sits.
FAQ
Do I have to fill out A2P 10DLC forms to text with KaiCalls? Not if you use a KaiCalls phone number. Your number is added to KaiCalls' registered Customer Care campaign when it is provisioned. Only businesses that connect their own Twilio account register their own brand and campaign.
What happens if adding my number to the campaign fails? The number is held and not activated. The dashboard shows that texts are limited until registration completes, and the nightly reconciliation retries. If it does not clear within a business day, contact support.
Can I send marketing texts through KaiCalls? No. The campaign is Customer Care. Kai screens outbound texts for marketing language, link shorteners, and excessive caps and blocks them before they leave. That protects your registration and everyone else's on the campaign.
Will customers see my number or a KaiCalls number? Your number, whenever it is active and enrolled — which is the normal state. Only while enrollment is pending are texts routed through a KaiCalls sender so they still arrive.
What if I bring my own Twilio account? Your numbers sit in your account, so the carriers need your brand and campaign. You register in the Twilio console; the A2P Setup page tracks your status and what to gather.
See it for yourself. Call the KaiCalls demo line at (417) 386-2898, hang up before Kai answers, and watch the follow-up text arrive from a registered number. Or visit kaicalls.com.
Topics
Related Posts
A plain-English guide to A2P 10DLC — what it is, why carriers filter unregistered business texts, what brand and campaign registration involve, and how KaiCalls handles it for you.
10 min readHow to Write an A2P 10DLC Campaign That Gets Approved the First TimeA field guide to the campaign registration form: choosing Customer Care over Mixed, writing a use-case description reviewers accept, sample messages with opt-out language, a consent description with real URLs, and the STOP/HELP replies — plus the rejection reasons that catch almost everyone.
12 min readHow KaiCalls Handles TCPA, Do Not Call, and A2P ComplianceWhat KaiCalls actually does to help you follow TCPA, the Do Not Call list, and A2P 10DLC texting rules — and what it can't do for you. This is not legal advice.
9 min read