When a client asks for an agent that texts — a booking link, an appointment confirmation, a dispatch alert to the crew — the build genuinely is a few hours. Backend, the tool, the wiring, a test message to your own phone. Done before dinner.
And then it sits there, because US carriers won't reliably deliver it yet.
The build is hours. The paperwork is weeks.
The part nobody mentions in the demo
Business texting in the US runs through a carrier registration called A2P 10DLC. Two stages. You register a brand, which approves in minutes. Then you register a campaign — what you intend to send, and to whom — and that's the one that takes time. Campaign approval typically runs about five business days, and ten to fifteen when the carriers are backed up. As of mid-2026 you also need Privacy Policy and Terms and Conditions URLs to complete it.
The reason this catches people is the failure mode. Unregistered traffic doesn't bounce with a useful error. It gets silently filtered. Your system reports the message as sent. Your logs look clean. Your customers just never receive anything, and you find out days later from the one person who mentions it.
Testing to your own phone often works unregistered, too — which is exactly what makes it so easy to believe you're fine.
How we handle it
Start registration first, before the build. It's the long pole. Everything else can happen while it's pending.
Check for an existing approved service before assuming you'll wait. More than once we've found a client already had an approved messaging service from some earlier project. A new number can usually be added to that service's sender pool and send immediately. Always worth ten minutes of looking before committing anyone to a week.
If the client is already on a platform with a registered number — GoHighLevel, for instance — sending through that can sidestep the whole registration problem. It's often the lower-effort path.
Have a day-one fallback. Point callers to the website, or capture their info for a human to text manually. The agent should never promise a text it can't deliver.
What this means for you
If someone tells you your AI will be texting customers "tomorrow" on a brand-new number, one of two things is true: they haven't done this before, or they're about to send straight into a carrier filter and call it a launch.
The honest version is less exciting and much more useful: the build is fast, the paperwork is the gate, and we start the paperwork today.
Want us to look at where a phone agent could take work off your plate? Grab a free workflow audit.