Prompt engineering is never the long pole — carrier registration is. Twilio’s docs put a Customer Profile at “72 hours or more” and warn that A2P 10DLC campaign reviews are “currently taking 10–15 days”; AWS documents US campaign registration at “Up to 4 weeks”. Voice-only goes live in days; the SMS leg costs weeks.
Ask how long it takes to get an AI voice agent live in the United States and you get a range, not a plan. The ranges are not wrong so much as unattributed: they average a fast path and a slow path into a number that tells you nothing about which gate you are standing in front of. The durations that actually govern the calendar are published — by Twilio, by Amazon Web Services, by A2P messaging specialists such as Telgorithm — but they sit in six different sets of CPaaS documentation and nobody assembles them into one critical path.
So here is the critical path, with every duration attributed to the party that published it, the named rejection codes that send you back to the start, and — the part that turns a list into a plan — what can be running in parallel while each gate is pending.
How long does it take to launch an AI voice agent in the US? The critical-path table
Read the last column first. Almost everything a buyer thinks of as “the build” — the prompts, the call flows, the CRM writes, the objection handling, the evaluation set — sits in the parallel column of every single row. It blocks nothing.
| Gate | Documented duration | Who publishes it | Named failure state | What it blocks | What can run in parallel |
|---|---|---|---|---|---|
| Customer Profile / business identity (Trust Hub) | Twilio documents: “It may take 72 hours or more for Twilio to approve your Customer Profile.” | Twilio, Direct Standard and Low-Volume Standard Registration Guide | Profile not approved; resubmit with corrected entity data | Brand registration, toll-free verification, Voice Integrity | Twilio’s own instruction: “While it’s pending approval, you can continue to the next step.” Agent build, call flows, integrations |
| A2P 10DLC brand registration | TCR review “typically occurs within a few minutes after submitting”; if it drops to IN_REVIEW, “Manual reviews take seven business days or more”. AWS: 1–2 business days for US companies, up to 3 weeks for international |
Twilio docs; AWS End User Messaging SMS docs | FAILED brand status |
Campaign registration — nothing downstream starts without an approved brand | All voice-side work; number research; disclosure scripting |
| Brand vetting (external vetting score) | AWS documents 1–2 business days for US companies; up to 3 weeks for international companies | AWS End User Messaging SMS docs | A low vetting score, which AWS documents as determining “the capabilities of your 10DLC campaigns” | Throughput above the default — AWS documents 1 message part per second per associated 10DLC number until you separately request an increase | Everything voice; the whole agent build |
| A2P 10DLC campaign review — the long pole | Twilio’s warning banner: “currently taking 10–15 days”. Twilio’s body text on the same page: “This process can take between two to three weeks to complete.” AWS: “Up to 4 weeks”. Telgorithm, a vendor estimate: “most Campaigns can still be approved within ~24–72 hours” | Twilio; AWS; Telgorithm (vendor blog) | Campaign rejected or suspended; resubmission re-enters the queue | All A2P SMS from 10-digit long codes | Every hour of agent engineering you will ever do |
| Number request and campaign association | AWS documents “Up to 10 days” to request your 10DLC number, and separately that “Associating a phone number with a 10DLC campaign can take approximately 14 days to complete.” | AWS End User Messaging SMS docs | Number cannot be reused across campaigns; each campaign needs at least one unique number | SMS on that specific number | Live voice testing on a separate, voice-only number |
| Toll-free verification (if you use a toll-free number) | Twilio: “Twilio reviews TFV requests within three business days.” AWS: “It can take up to 15 business days for your registration to be processed after it is submitted.” | Twilio docs; AWS End User Messaging SMS docs | Twilio publishes these as error codes: 30444 Disallowed: Fraud · 30445 Could not validate business information · 30489 Website must be established and active. Twilio sets the edit window “to seven days from the initial request”, after which the request expires and you create another |
Messaging traffic on that toll-free number | Voice traffic on the same number; the agent build |
| Business Registration Number on the toll-free submission | Twilio’s changelog states it is required for all new toll-free submissions from 17 February 2026 | Twilio changelog, “Business Registration Numbers Required for Toll-Free Messaging Traffic” | A missing or mismatched BRN. Twilio’s 2025 notice states the EIN “should match the legal business name you list during verification”; we have not seen Twilio name a specific rejection code for a BRN mismatch | The toll-free submission itself | Nothing — this is day-one document collection |
| Voice Integrity (spam-label remediation) | Twilio documents Business Profile vetting — “The time to vet can be between 24 to 48 hours” — and remediation: “The time to remediation can be between 24 to 48 hours.” The same page warns that “The API flow for Voice Integrity Private Beta is subject to change.” | Twilio, Voice Integrity Onboarding | Numbers stay labelled by the carriers’ analytics vendors | Clean caller-ID presentation — not the ability to place calls | Live calling; branded-calling enrolment |
| Porting an existing number in | We could not locate a published typical elapsed time in Twilio’s Porting API documentation, which carries a “Public Beta” notice; the one published deadline is on you — Twilio documents that “The authorized representative has 30 days to sign this document or the port-in request will be canceled automatically.” | Twilio, Port phone numbers using Twilio APIs | Action Required / Port Rejected from the losing carrier; review the rejection reason code and resubmit |
Cutover to your existing business number | Everything, if you launch on a newly provisioned number and port later |
| Agent build: prompts, flows, integrations, evaluations | No carrier or registry publishes a duration for this, in anything we could locate — it is your engineering, not their queue | You | A bad agent — recoverable in an afternoon | Nothing on the carrier path | All nine rows above |
The Registration Clock: the rule this table produces
Name it so it survives being summarised:
The Registration Clock. On a US AI voice deployment the calendar belongs to carrier registration, not to the agent. Voice-only, the documented gates clear in days. Add the SMS follow-up leg and the published ranges run to weeks — up to four weeks for campaign review alone, on AWS’s own table. So the day-one task is not the prompt. It is the entity paperwork: legal name, EIN or business registration number, registered address and a live, established website — submitted before anyone writes a script, because every gate downstream re-uses those same details and every rejection restarts a queue measured in weeks.
The corollary is the uncomfortable one. If your programme slips, the post-mortem will almost never find that the agent was late. It will find that an EIN did not match a legal business name, or that a website was not live when a reviewer looked at it — which is precisely what Twilio’s 30445 and 30489 rejection codes are named after.
Two lanes, and the one decision that moves your go-live date
The single largest lever on the calendar is not which platform you buy. It is whether the deployment sends SMS.
| Lane | Gates you inherit | Fastest documented path | Slowest documented path |
|---|---|---|---|
| Voice-only, newly provisioned local number | Customer Profile; optionally Voice Integrity | Customer Profile at 72 hours, Voice Integrity vetting at 24–48 hours — days, not weeks | A Customer Profile that needs correcting and resubmitting |
| Voice plus SMS follow-up on 10DLC | Everything above, plus brand, vetting, campaign, number request and campaign association | Telgorithm’s vendor estimate of ~24–72 hours for campaign approval, on a clean submission | AWS’s published table: 1–2 business days brand + 1–2 business days vetting + up to 4 weeks campaign + up to 10 days for the number |
| Voice plus SMS on a toll-free number | Toll-free verification, with a Business Registration Number since 17 February 2026 | Twilio’s “within three business days” | AWS’s “up to 15 business days”, plus a fresh cycle for every rejection |
| Keeping your existing published number | Porting, on top of whichever lane above applies | No published typical duration we could locate; launch on a new number and port behind it | A carrier rejection plus a 30-day LOA signature window |
This is why the go-live question and the channel question are the same question. Zian AI’s agents run live phone, SMS, email and WhatsApp outreach, with SmartReach AI™ orchestrating which channel fires when — so a deployment that includes the SMS follow-up leg inherits the 10DLC clock on day one, and we treat brand registration as a kickoff task rather than a launch-week one.
Where the published durations disagree, and why that is useful
Two disagreements are worth carrying into a project plan, because each one is a planning assumption in disguise.
Toll-free verification: three business days or fifteen? Twilio’s toll-free verification API documentation states that “Twilio reviews TFV requests within three business days”. AWS End User Messaging SMS documentation warns that “It can take up to 15 business days for your registration to be processed after it is submitted”. Both are product documentation, not marketing. They are not necessarily contradictory — Twilio is describing its own review step, while AWS is describing the whole submission-to-processed window — but the gap tells you that a provider’s stated SLA covers the segment that provider controls, not the end-to-end clock. Plan against the longer figure and treat the shorter one as the best case.
Campaign review: 72 hours or four weeks? Twilio’s Direct Standard registration guide contradicts itself on one page: a warning banner says campaign reviews are “currently taking 10–15 days”, while the body text below says the manual vetting process “can take between two to three weeks to complete”. AWS documents “Up to 4 weeks”. Telgorithm’s 2026 post says most campaigns are approved within roughly 24 to 72 hours — but that is a vendor estimate drawn from its own book of traffic, prefaced in its own words by “Based on our experience”, and it is describing well-prepared submissions handled by a provider that specialises in getting them right first time. Telnyx makes a similar claim on its 10DLC registration product page — a marketing page, not documentation — and dates it: “In mid 2023, most registrations through our API were completed within 3 business days – others take 20 days or longer.”
The honest reading is that submission quality, not provider choice, explains most of the spread — which is exactly why the day-one task is document collection.
And published dates move. Twilio’s June 2025 changelog told customers that “By January 2026, a BRN will be required for all new Toll-Free verifications”. The requirement actually landed on 17 February 2026, per the changelog entry titled “Business Registration Numbers Required for Toll-Free Messaging Traffic”. Plan against the gate, not the announcement.
Apply For Partnership — Zian AI is in a partnership-application beta, and we work through the registration critical path with partners before the first prompt is written.
What makes the timeline slip
Every gate above has a failure state, and the failure states are not symmetrical. A bad prompt is fixed in an afternoon. A rejected registration puts you back in a queue.
- Entity data that does not match. Twilio’s
30445— “Could not validate business information” — is the rejection Twilio documents when the business name or address cannot be confirmed, or when the submitted website “is not live, is inaccessible, requires a login, points to an aggregator or ISV site, or uses a placeholder or generic page”. The Business Registration Number requirement that took effect on 17 February 2026 makes this stricter, not looser: Twilio’s toll-free verification API reference marksBusinessRegistrationNumber“Required for all business types except SOLE_PROPRIETOR.” - A website that is not ready.
30489is literally named “Website must be established and active”. If the landing page describing the messaging programme goes up the week before launch, it is a gate, not a marketing task. - The seven-day edit window. After a toll-free rejection, Twilio sets the resubmission deadline “to seven days from the initial request. After that date, the TFV request expires and you need to create another.” Miss it and you are not resubmitting — you are starting over.
- Use cases that trip fraud review.
30444, “Disallowed: Fraud”, is the code for a business or messaging programme associated with fraud or deceptive messaging. Twilio’s page for that code states that messaging traffic on the toll-free number is blocked until the number is successfully verified for messaging to the United States and Canada — so the penalty for landing here is a dead number, not a delayed one. - Porting on the critical path. If your go-live depends on moving an existing published number, you have added a losing carrier’s queue to your plan, plus a 30-day LOA signature window. Launching on a new number and porting afterwards takes that dependency out of the path entirely.
What to start on day one
Sequenced against the table, not against a project-plan template:
- Day 0 — collect the entity documents. Legal business name exactly as registered, EIN or equivalent business registration number, registered address, business website live and describing what you actually do, and an authorised contact who can sign. This one bundle is re-used by the Customer Profile, the 10DLC brand, the toll-free submission and any porting LOA.
- Day 0 — submit the Customer Profile, then keep moving. Twilio’s guidance is explicit that you continue while it is pending.
- Day 1 — submit the brand. Brand approval gates campaign registration, and campaign registration is the long pole. Everything else is downstream of this being in the queue.
- Days 1 onwards, in parallel — build the agent. Prompts, call flows, knowledge retrieval, CRM writes, evaluations, and the disclosure language. Getting the disclosure right is a genuine workstream in the US, not a line of script: see our breakdown of US state AI call disclosure laws for voice agents.
- In parallel — caller-ID presentation. Voice Integrity vetting and remediation are documented at 24–48 hours each, and branded calling is a separate commercial and standards track with its own lead time; we cover what it takes to get your business name and logo onto the caller-ID screen.
- Only after the campaign is approved — turn up the volume. Throughput tiers, not the launch date, are what registration quality buys you later; the operational side of that is in our guide to scaling AI calling from 100 to 10,000 calls a day.
If the outcome you want is booked meetings rather than a telephony project, the same critical path applies to a managed deployment — the difference is who is holding the paperwork. That is the model behind our AI appointment setting agents.
The honest caveat
Everything above is a documented SLA or a published typical range. None of it is a guarantee. Twilio’s “72 hours or more” has no upper bound in the sentence itself; AWS’s figures are stated as “up to”; Telgorithm’s and Telnyx’s numbers are vendor estimates about their own traffic, not independent measurements. Carrier and registry review queues move with submission volume, which is why Twilio’s page carries a “Due to an increase in campaign submissions” banner at all.
The one thing you can plan around with confidence is the asymmetry: a single rejection can add more calendar time than the entire agent build. That is the whole argument for starting with the paperwork.
Frequently asked questions
More on how we deploy and what buyers ask us is collected in the Zian AI questions and answers hub.
How long does it take to launch an AI voice agent in the US?
A voice-only agent on a newly provisioned number can be live in days: Twilio documents Customer Profile approval at “72 hours or more” and Voice Integrity vetting at “between 24 to 48 hours”. A deployment that also sends SMS inherits A2P 10DLC, where AWS End User Messaging SMS documents campaign registration at “Up to 4 weeks” and Twilio’s console guide currently warns of 10–15 days.
Is building the AI agent the slowest part?
No. On the critical path above, the agent build blocks nothing — it sits in the parallel column of every registration row. The stage that dominates the calendar is A2P 10DLC campaign review, which the fastest vendor estimate we found puts at roughly 24 to 72 hours and which AWS documents at up to four weeks.
Do I need A2P 10DLC if my AI agent only makes calls?
A2P 10DLC governs application-to-person messaging on 10-digit long codes, so a voice-only deployment does not enter that queue. The moment an SMS confirmation, reminder or follow-up is added, the brand, vetting, campaign and number-association gates apply. This is the single decision with the largest effect on your go-live date.
What happens if my toll-free verification is rejected?
Twilio publishes the rejection reasons as error codes — 30444 (Disallowed: Fraud), 30445 (Could not validate business information) and 30489 (Website must be established and active). If the response includes an edit allowance you can correct and resubmit, but Twilio’s toll-free verification API docs state that it “sets this property value to seven days from the initial request. After that date, the TFV request expires and you need to create another.”
What changed for toll-free numbers in February 2026?
Twilio’s changelog entry “Business Registration Numbers Required for Toll-Free Messaging Traffic”, dated 17 February 2026, states that from that date a business registration number is required for all new toll-free submissions for every business type other than sole proprietorships. Twilio’s earlier notice, in June 2025, had said the requirement would apply by January 2026 — a useful reminder to plan against the gate rather than the announcement.
Why do the timelines I am quoted differ so much from these?
Because most quoted ranges come from vendor blogs rather than product documentation, and the two describe different things. Telgorithm’s 2026 post says most campaigns are approved within roughly 24 to 72 hours based on its own experience; Twilio’s registration guide currently warns that “campaign reviews are currently taking 10–15 days” and its body text says two to three weeks. Treat a vendor estimate as a best case for a clean submission, and the documentation figures as the planning number.
Apply For Partnership — Zian AI has been running outbound acquisition since 2017 and is currently in a partnership-application beta.