Quick answer: On providers’ own published figures, read on 24 October 2026, A2P 10DLC registration takes from 1 business day (the low end of Sinch Engage’s range) to 34 (AWS’s step-table ceilings for a US-based company, summed). Twilio’s stage times add up to 5 to 23+ business days, or 10 to 38+ after one campaign rejection. The longest stage at most providers is manual campaign vetting by a carrier-side partner, not The Campaign Registry.
Where Zian fits in a 10DLC timeline
If an AI agent will text your US leads, file the 10DLC registration before you build the agent: the queue is the long pole. Zian AI’s agents follow up by SMS as well as voice calls, email, WhatsApp, Instagram DMs and Facebook Messenger, and an SMS from a US 10DLC number cannot reach a handset until its campaign is approved and the number is linked to it.
During Zian’s partnership-application beta, the question of whose 10DLC brand the messages run under, and who files it, is part of the application conversation. Raise it there rather than assume an answer. Each of Zian’s three listed plans, including Intel + Widgets (Free Forever), starts with a partnership application. Voice is not held in the same queue: Twilio’s guidance on unregistered traffic, in its answer on what to do when a registration is rejected, notes that its “Programmable Voice product is not subject to the same carrier restrictions as SMS”, and Zian’s AI receptionist answers inbound calls 24/7 and books appointments from them. SmartReach AI™ orchestrates message, channel and timing for follow-up, so a registration delay can change which channel carries the first follow-up.
How long does A2P 10DLC registration take, stage by stage?
A2P 10DLC registration is not one approval but four or five sequential steps, each with its own clock. The steps, in the order the providers we read describe them, are:
- Account or customer profile. Twilio says its Customer Profile “may take 72 hours or more” to approve, but adds “While it’s pending approval, you can continue to the next step” (Twilio Direct Standard registration guide). It is not on the critical path, so the calculation below leaves it out.
- Brand registration. Your business identity, filed with The Campaign Registry (TCR). A Sole Proprietor brand is for an individual without a business tax ID; a Low-Volume Standard brand has an EIN but skips secondary vetting; a Standard brand includes it. Twilio’s Campaign Vetting FAQ lists a secondary vetting fee in the Standard column only.
- Secondary vetting. A third-party check that sets the Trust Score behind your throughput.
- Campaign registration and manual campaign vetting. Your use case, sample messages and opt-in flow, reviewed manually by a Direct Connect Aggregator (DCA) or another vetting partner. Twilio states that all three brand types’ campaigns “are subject to a manual vetting process”.
- Number provisioning. After approval, each 10DLC number is linked to the campaign and registered with the carriers. Twilio calls this Number Registration; Telnyx, Plivo and Vonage call it assignment or linking.
TCR says plainly that it is not the reviewer: “The Campaign Registry (TCR) does not review, approve, or reject campaigns. This is solely done by the CSPs and their upstream connection partners” (TCR Resources FAQ). It publishes no number either: approval time “can vary from use-case to use-case, as well as from CSP to CSP”, and “Typically, the more partners there are in the connection chain, the longer the campaign approval time.” Every figure below therefore comes from a provider, not the registry.
The 10DLC timeline by provider, in each provider’s own words
Every stage, every provider, the exact published wording with its hedge, and the page it came from. We read every page on 24 October 2026; the “updated” date is the one the page itself shows, where it shows one. Twilio, Plivo (legacy help centre) and Vonage articles were read through their public help-centre APIs, and Sinch’s pages through a text reader, because those sites block or script-render for automated readers.
| Stage | Provider | Published time, exact wording | Source (read 24 October 2026) |
|---|---|---|---|
| Brand registration | Twilio | “typically be completed in a few minutes (in some cases, may take up to 24 hours)” | Overview of US A2P 10DLC (updated 26 Sep 2026) |
| Brand registration | Twilio (Sole Proprietor) | “Approval typically occurs within a few minutes of submitting”; the OTP must be answered “within 24 hours” | Direct Sole Proprietor guide (updated 3 Aug 2026) |
| Brand registration | Telnyx | “Instant” | Getting Started with 10DLC |
| Brand registration | Vonage | basic verification “usually takes around 10 seconds”; if still pending “after 48 hours, please reach out to our support team” | Brand verification issues FAQ (updated 18 Apr 2023) |
| Brand registration | Vonage (public companies, Authentication+) | basic verification “usually between 10 seconds and 48 hours” | Brand Authentication+ update (updated 29 Jul 2025) |
| Brand registration | AWS End User Messaging | “1-2 business days” (US-based); “Up to 3 weeks” (international) | US 10DLC registration |
| Brand: manual or secondary vetting | Twilio | “can take up to 7 days” (Overview); “Manual reviews take seven business days or more” (registration guide) | Overview; Direct Standard guide (updated 15 Sep 2026) |
| Brand: manual or secondary vetting | Telnyx | “Standard vetting takes 1-7 business days”; “You can create campaigns before vetting completes” | Getting Started with 10DLC |
| Brand: manual or secondary vetting | AWS End User Messaging | “1-2 business days” (US-based); “Up to 3 weeks” (international) | US 10DLC registration |
| Campaign vetting | Twilio | “currently takes up to 5 business days for standard use cases” | Campaign Vetting FAQ (updated 15 May 2026) |
| Campaign vetting | Twilio | “currently takes about 7 business days”; banner: “can take up to 10 business days” | Overview (updated 26 Sep 2026) |
| Campaign vetting | Twilio | “currently taking 5–10 days” | Campaign Registration Recommendations (updated 29 Sep 2026); MPS and Trust Scores (updated 9 Sep 2026) |
| Campaign vetting | Twilio | “currently taking 10–15 days”; “between two to three weeks” | Twilio Docs, Direct Standard registration guide |
| Campaign vetting | Twilio (Sole Proprietor) | “might take several weeks” (Docs); “between 5-10 days” (help article) | Twilio Docs, Sole Proprietor overview; help article |
| Campaign vetting | Telnyx | Telnyx review “same day or next business day”, then carrier review “3 business days or less” | How to create a 10DLC campaign |
| Campaign vetting | Telnyx | “typically takes 72 business hours after Telnyx approves”; elsewhere “Wait for carrier approval (1-5 business days)” | 10DLC Campaign Compliance Guide; Phone Number Assignment |
| Campaign vetting | Plivo | “Processing time is 1-2 weeks”; “Campaign reviews now take between 1-2 weeks” | A2P 10DLC (updated 31 Jul 2025); campaign vetting article (updated 19 Jan 2024) |
| Campaign vetting | Vonage | “an average of 3 to 5 weeks for the campaigns to be fully activated” | 10DLC Guide of guides (updated 27 Nov 2024) |
| Campaign vetting | Bandwidth | “3-5 business days for the initial review of a campaign, but it could be longer” | Campaign vetting and provisioning (updated 14 Aug 2026) |
| Campaign vetting | Bandwidth | “Campaigns for standard use cases should be approved immediately” | 10DLC FAQ (updated 13 Aug 2026) |
| Campaign vetting | AWS End User Messaging | “Up to 4 weeks” | US 10DLC registration |
| Number provisioning | Twilio | “often completes within minutes, it can also take up to 24 hours” | Number Registration Best Practices (updated 15 Sep 2026) |
| Number provisioning | Telnyx | “Typical Timeline” column: T-Mobile “Instant to 24 hours”; AT&T and Verizon “1-3 business days”; US Cellular “3-5 business days” | 10DLC Campaign Registration |
| Number provisioning | Telnyx | assignment “typically takes about 2 hours but can range from a few minutes to a few days”; AT&T number registration “can take up to 7 business days” | How to assign a number; 10DLC Troubleshooting |
| Number provisioning | Plivo | “typically within 48 hours” | How to link numbers (updated 23 Aug 2024) |
| Number provisioning | Vonage | “Typically, number linking requests will take from a few minutes to a few hours” | Link a number via the API |
| Number provisioning | Bandwidth | T-Mobile portion “anywhere from minutes to a few days” | Campaign vetting and provisioning |
| Number provisioning | AWS End User Messaging | “Up to 10 days” (request number); associating a number “approximately 14 days” | US 10DLC registration |
| Whole process | Sinch Engage | “Provisioning time” “1-5 business days” (comparison table); “typically get you set up with a new A2P 10DLC number within a few days”; “In some cases, it may take a bit longer” | 10DLC local number page |
| Whole process | Bandwidth | “Expected Time to Market 1 Week” | 10DLC glossary |
| Whole process | The Campaign Registry | no figure: “can vary from use-case to use-case, as well as from CSP to CSP” | Resources FAQ |
Read the hedges: “up to 4 weeks” is a ceiling with no floor, and “currently taking 5–10 days” is a queue report.
Where the published 10DLC times disagree, including inside one provider
Several providers publish more than one figure for the same stage. Twilio alone carries eight different wordings for campaign-vetting time across its help centre and documentation, all live on the same day:
- “up to 5 business days” in the Campaign Vetting FAQ, last updated 15 May 2026;
- “about 7 business days”, under a banner saying reviews “can take up to 10 business days”, in the 10DLC overview, updated 26 September 2026;
- “5–10 days” in five help articles updated between 3 August and 29 September 2026;
- “10–15 days” in a warning box, and “between two to three weeks” further down the same page, in the Twilio Docs version of the Direct Standard guide;
- “several weeks” in the Twilio Docs Sole Proprietor overview;
- “at least 3 weeks” in the unregistered-traffic shutdown article, whose text describes the 2023 deadline backlog although the page was updated in May 2026.
We use 5 business days as Twilio’s floor (the September 2026 help articles) and 15 as its ceiling (the Docs page’s “two to three weeks”), rather than pick one.
The same pattern repeats elsewhere. Bandwidth’s 10DLC FAQ says standard campaigns “should be approved immediately”, while its vetting article says the DCA review takes “3-5 business days … but it could be longer”. Telnyx gives carrier review as “3 business days or less”, “72 business hours” and “1-5 business days” on three pages. Telnyx and Plivo each give two toll-free times that differ by a factor of two or more. When two pages from one provider disagree, plan to the higher figure.
Earliest realistic first send: the worked calculation
To turn the timeline into a launch date, we added the stages up by script, with every input a published figure from the table above. We call the result the first-send sum: the earliest business day a registered 10DLC number can carry a US message, under one fixed set of rules applied to every provider.
The rules. “A few minutes” and “instant” count as 0 business days; “24 hours” counts as 1. A range gives its low end to the floor and its high end to the ceiling. A figure with no floor (“up to”, “within”, “or less”) is used in both columns, because nothing on the page supports a shorter time. A count of “days” without the word “business” is treated as business days, and a week as 5. Open-ended wording (“or more”, “could be longer”, “a few days”) marks the ceiling with a plus sign. A stage a provider does not publish counts as 0 and is flagged, so those sums understate. One rejection means the campaign-review stage runs again in full, with the fix itself assumed to take no time. Weekends are skipped; US public holidays are not, so Veterans Day (11 November 2026) and Thanksgiving (26 November 2026) would push real dates later.
Plivo is the only provider we found that publishes the repeat time we assume: “If one of your campaigns gets rejected and you’re required to submit additional information, it will take the same amount of time to get the campaign approved” (Plivo). Twilio’s rejection article says only that you can “resubmit the same campaign for another review”, and Bandwidth that declines “will prolong the process and timeline”. For everyone except Plivo, the one-rejection column is our assumption, not the provider’s statement.
| Provider | Stage inputs, business days (floor to ceiling) |
|---|---|
| Twilio | Brand incl. secondary vetting 0 to 7+; campaign vetting 5 to 15; number registration 0 to 1 |
| Telnyx | Brand 0 (vetting runs alongside); Telnyx review 0 to 1; carrier review 1 to 5; carrier provisioning and number registration 1 to 7 (floor is AT&T and Verizon’s 1; US Cellular’s 3–5, or the troubleshooting guide’s 3–7 for AT&T number registration, would raise it) |
| Plivo | Brand time not found on Plivo’s pages as at 24 October 2026 (0, flagged); campaign 5 to 10; number linking 2 (ceiling only) |
| Vonage | Brand 0 (basic verification “usually takes around 10 seconds”); campaign to activation 15 to 25; number linking 0 to 1 |
| Bandwidth | Initial brand time not found on Bandwidth’s pages as at 24 October 2026 (0, flagged); DCA campaign review 3 to 5+; T-Mobile provisioning 0 to “a few days” (+) |
| Sinch Engage | One end-to-end figure, 1 to 5+ (“it may take a bit longer”) |
| AWS, US-based company | Brand 1 to 2; vetting 1 to 2; campaign 20 (ceiling only); number 10 (ceiling only) |
| Provider | No rejection, business days | First send if you file Monday 26 October 2026 | With one campaign rejection, business days | First send with one rejection |
|---|---|---|---|---|
| Sinch Engage | 1 to 5+ | Tue 27 Oct 2026 to Mon 2 Nov 2026 | not computable (one end-to-end figure) | — |
| Telnyx | 2 to 13 | Wed 28 Oct 2026 to Thu 12 Nov 2026 | 3 to 19 | Thu 29 Oct 2026 to Fri 20 Nov 2026 |
| Bandwidth | 3 to 5+ (no initial brand time found; counted as 0) | Thu 29 Oct 2026 to Mon 2 Nov 2026 | 6 to 10+ | Tue 3 Nov 2026 to Mon 9 Nov 2026 |
| Twilio | 5 to 23+ | Mon 2 Nov 2026 to Thu 26 Nov 2026 | 10 to 38+ | Mon 9 Nov 2026 to Thu 17 Dec 2026 |
| Plivo | 7 to 12 (no brand time found; counted as 0) | Wed 4 Nov 2026 to Wed 11 Nov 2026 | 12 to 22 | Wed 11 Nov 2026 to Wed 25 Nov 2026 |
| Vonage | 15 to 26 | Mon 16 Nov 2026 to Tue 1 Dec 2026 | 30 to 51 | Mon 7 Dec 2026 to Tue 5 Jan 2027 |
| AWS (US-based company) | 32 to 34 | Wed 9 Dec 2026 to Fri 11 Dec 2026 | 52 to 54 | Wed 6 Jan 2027 to Fri 8 Jan 2027 |
The arithmetic, worked for Twilio: floor 0 + 5 + 0 = 5 business days, so a Standard brand filed on Monday 26 October 2026 can send on Monday 2 November at the earliest. Ceiling 7 + 15 + 1 = 23 business days, or Thursday 26 November, and the plus sign is there because Twilio says manual brand reviews take “seven business days or more”. One rejection adds the campaign stage again: 5 + 5 = 10 at the floor, 23 + 15 = 38 at the ceiling, or Thursday 17 December 2026.
Substitute your own figures and start date. Three cautions. Sinch’s 1–5 business days is a single end-to-end figure for its Sinch Engage product, so it cannot be split into stages or repeated for a rejection. The AWS row is long mainly because AWS publishes ceilings rather than typical times, and it uses the “Up to 10 days” in AWS’s step table for the number; the same AWS page also says associating a number with a campaign “can take approximately 14 days”, which would make the AWS row 36 to 38 business days (56 to 58 with one rejection). And Vonage’s 3–5 weeks sits on an article last updated on 27 November 2024 whose note begins “Currently there are some delays”, so treat it as the oldest figure in the set. The sum is built from what providers publish, not from measured approvals.
Planning a US SMS launch around an AI agent? Zian’s agents answer inbound calls 24/7 as an AI receptionist and follow up by voice, SMS, email and WhatsApp, with SmartReach AI™ pacing each touch. Apply For Partnership
Which 10DLC stage takes the longest, and what makes it slip?
Campaign vetting is the longest stage in the first-send sum at Twilio, Plivo, Vonage, Bandwidth and AWS, at both the floor and the ceiling, on every figure we could count. At Telnyx the picture is different: its carrier review tops out at 5 business days, but its troubleshooting guide says AT&T number registration “can take up to 7 business days”, so the post-approval step is Telnyx’s longest ceiling. Sinch publishes one figure, so it has no stage to single out.
What the providers themselves say stretches each stage:
- A new EIN. Twilio says newly issued EINs “won’t propagate across the relevant database validation systems (around 30- 90 days)”, and that an identity appeal with the IRS letter “usually takes 5-7 business days” (Twilio Brand Approval Best Practices). Bandwidth’s FAQ makes the same point: an EIN letter issued in the last 90 days is probably not yet in the IRS database.
- Details that do not match public records. Twilio says a discrepancy can trigger manual secondary vetting “which can take up to 7 days”.
- Special use cases. Bandwidth says specialty use cases need additional review that it has “seen this take up to a few weeks”. Political campaigns need a Campaign Verify token, which Twilio says, citing Campaign Verify, “can take anywhere between 1-7 business days” (Special Use Cases).
- Public companies. Authentication+ is mandatory for public for-profit brands. TCR’s verification email “will expire in 7 days”, and a CSP can resend it “up to 30 days” after registration (TCR).
- Registering from outside the US. AWS publishes up to 3 weeks each for brand registration and vetting for internationally based companies, against 1–2 business days for US-based ones. If you file from Australia, read our note on why 10DLC campaigns get rejected and how to fix them, which covers the tax-ID question.
- Repeated resubmission. Bandwidth parks a campaign submitted “four or more times without resolving the underlying issues” in Pending (rejection code 6105).
- Being further down the chain. TCR: “Typically, the more partners there are in the connection chain, the longer the campaign approval time.”
The fees for each attempt are on our page about A2P 10DLC costs for two-way AI SMS agents.
Can I send SMS while my 10DLC registration is pending?
No, not on a 10DLC number through Twilio, and Plivo, Bandwidth and Telnyx say the same in their own words. Plivo: “Messages sent from numbers that are not associated with registered campaigns will not be delivered” (Plivo A2P 10DLC). Twilio’s unregistered-traffic article states that all SMS and MMS to US numbers from unregistered 10DLC numbers have been “fully blocked effective September 1st, 2023”, that a number “submitted but still pending approval” counts as unregistered and is blocked with error 30034, and that “Twilio messaging rates will apply” to the blocked messages. It adds that “‘In Progress’ Campaign registrations will be included in the blocks”.
The date you may have seen, 1 February 2025, is not on Twilio’s page. It is on Bandwidth’s FAQ: “As of February 1, 2025, unregistered outbound traffic is being blocked in the industry” (Bandwidth 10DLC FAQ). Telnyx’s help article is headed “10DLC Registration Deadline February 3” and says enforcement began on “February 4” without naming a year on the page. All three agree on the present position: unregistered 10DLC traffic to US handsets is blocked.
Two narrower points are worth knowing. Bandwidth will not let you assign a number to a campaign until the DCA has approved it (error 12219), and says unregistered traffic is blocked with error codes it writes as “(4)476 or (4)773”. Twilio currently runs a temporary exception for numbers in “Pending Registration”, and tells you how to use it: “add your numbers to your Messaging Service BEFORE registering your Campaign” (Twilio Number Registration Best Practices). Twilio also warns that “Once the exception is lifted, customers can expect 30035 errors until the Number Registration process is complete”, and that “Twilio is unable to provide processing time guarantees as these are handled by our ecosystem partners.” The exception covers the last step only.
If the SMS you are waiting to send is a missed-call text-back, the queue is part of its payback period; our missed-call text-back ROI calculator shows where that time sits in the arithmetic.
Is toll-free verification or a short code faster than 10DLC?
On published figures, toll-free verification is faster than the 10DLC first-send sum at Twilio, Plivo, Vonage and AWS, level at Sinch Engage, and not clearly faster at Telnyx or Bandwidth; a short code is slower at every provider that publishes a short-code time. Same rule as above: quote the page, keep the hedge.
| Route | Provider | Published time, exact wording | Source (read 24 October 2026) |
|---|---|---|---|
| Toll-free verification | Twilio | “approximately 3-5 business days” (help); “within three business days” (Docs) | Toll-Free Message Verification (updated 1 Jun 2026); TFV API onboarding |
| Toll-free verification | Telnyx | “normally 5 business days or less” (help); “typically takes 1-2 weeks” (developer docs) | Toll Free Verification Request Guide; Toll-Free Verification docs |
| Toll-free verification | Plivo | “typically takes between 24 to 72 hours” (help); “can take up to two weeks” (blog, 2024) | Toll-Free Verification Process (updated 28 Apr 2025); blog |
| Toll-free verification | Vonage | “between 2-10 business days” | Toll-Free Number Messaging Registration (updated 7 Aug 2026) |
| Toll-free verification | Sinch Engage | “1-5 business days” | number comparison table |
| Toll-free verification | Bandwidth | “can take up to 5 business days to complete” | Toll-free verification handbook (updated 21 Oct 2026) |
| Toll-free verification | AWS End User Messaging | “up to 15 business days” | US toll-free registration |
| Short code | Twilio | “about 4-8 weeks” from payment (2026 guide); “between 6 – 10 weeks” (2024 article) | Short Code onboarding (updated 1 Oct 2026); carrier approval timeline (updated 16 Sep 2024) |
| Short code | Telnyx | “about 6 weeks” after the brief is approved | US Short Code Ordering Process |
| Short code | Plivo | “6-8 weeks” (US random or vanity) | Short Codes FAQ |
| Short code | Vonage | “8-12 weeks” (US, 2024 overview); “6-10 Weeks” (US dedicated short code, 2024) | Short Codes Features Overview; US Dedicated Short Code |
| Short code | Bandwidth | carrier submission “6-8 weeks” for a net new code, after internal steps it lists at up to 2 weeks (brief and setup) and up to 3 weeks (brief compliance) | Short code handbook (updated 9 Feb 2026) |
| Short code | Sinch Engage | “usually takes 8–12 weeks” | Short code page |
Before treating toll-free as a head start, read Twilio’s status table: “As of January 31, 2024, ALL Pending traffic is blocked in the US”, and traffic from toll-free numbers never submitted for verification or not approved (“Restricted”) has been blocked since 8 November 2023 (Twilio). A toll-free number is no more usable mid-review than a 10DLC number. Bandwidth’s toll-free verification handbook says requests “are reviewed manually and can take up to 5 business days to complete”.
A short code is the only route on this page where the published figure is measured in months. Plivo’s overview sums the trade: approval time “Days” for 10DLC, “Days to weeks” for toll-free and “Several weeks” for short codes (Plivo 10DLC overview).
What to do this week if you need to text US customers soon
Our recommendation, from the statements above:
- Check the EIN date today. If the EIN is younger than 90 days, expect brand verification trouble at Twilio and Bandwidth and have the IRS letter ready for an appeal.
- Make the brand record match public records exactly: legal name, address and tax ID. A mismatch turns a few-minute step into a manual review.
- Write the campaign once, carefully. At the floor, the campaign stage is 5 of Twilio’s 5 business days, 5 of Plivo’s 7, 15 of Vonage’s 15 and 3 of Bandwidth’s 3, and a rejection repeats it. The fix list is on our rejection page.
- On Twilio, put your numbers in the Messaging Service before you submit the campaign, which is what Twilio says qualifies them for the current Pending Registration exception.
- If one more week matters, file toll-free verification in parallel. Twilio publishes 3–5 business days for it. Neither route carries traffic while pending, so this buys a second queue, not a bypass.
- Plan peak season from the ceiling, not the floor. If the launch is tied to a date, our eight-week plan for SMS throughput over Black Friday works backwards from it.
The honest cost of running this yourself is somebody owning the queue: every client is its own brand and campaign with its own clock, and every rejection restarts the longest stage. Multiply your expected brands by the ceilings above to see whether that is a side task or a job.
Frequently asked questions
How long does A2P 10DLC registration take?
On the providers’ own published figures, read on 24 October 2026, from 1 business day (the low end of Sinch Engage’s range) to 34 business days (the sum of AWS’s step-table ceilings for a US-based company). Added up stage by stage, Twilio’s figures give 5 business days at best and 23 or more at the top of its ranges. The Campaign Registry publishes no figure.
How long does A2P 10DLC registration take on Twilio?
Twilio’s pages give brand registration “in a few minutes”, up to 7 days for a manual secondary vetting review, campaign vetting from “up to 5 business days” to “two to three weeks” depending on the page, and number registration “within minutes” to “up to 24 hours”. Summed, that is 5 to 23+ business days, or 10 to 38+ with one campaign rejection.
How long does 10DLC campaign vetting take?
Twilio says 5–10 days in its August and September 2026 help articles and “two to three weeks” in its Docs; Telnyx says carrier review takes 3 business days or less (1–5 business days on another page) after its own same-day or next-business-day check; Bandwidth says 3–5 business days but “it could be longer”; Plivo says 1–2 weeks; Vonage’s 2024 note says an average of 3 to 5 weeks; AWS says up to 4 weeks.
Can I send SMS while my 10DLC campaign is pending approval?
Not from a 10DLC number through Twilio. Twilio’s article on unregistered traffic says a number “submitted but still pending approval” is blocked with error 30034 and that messaging rates still apply to blocked messages. Bandwidth says unregistered outbound traffic has been blocked across the industry since 1 February 2025.
Is toll-free verification faster than 10DLC registration?
Often, on published figures. Twilio gives approximately 3–5 business days for toll-free verification, Vonage 2–10 business days and AWS up to 15 business days. But Twilio has blocked all pending toll-free traffic since 31 January 2024, so a toll-free number cannot send mid-review either.
How long does a resubmitted 10DLC campaign take?
Plivo is the only provider we found that states it: a rejected campaign that needs more information takes the same amount of time again, 1–2 weeks on its figures. Twilio and Bandwidth say only that it goes back for another review.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Brand registration “a few minutes … up to 24 hours”; secondary vetting “up to 7 days”; campaign “about 7 business days”, “up to 10 business days” | Twilio | https://help.twilio.com/articles/1260800720410 | 24 October 2026 |
| Campaign vetting “up to 5 business days”; contact support after 10 days; secondary vetting fee in Standard column only | Twilio | https://help.twilio.com/articles/11587910480155 | 24 October 2026 |
| Campaign reviews “5–10 days” | Twilio | https://help.twilio.com/articles/26149060902555 | 24 October 2026 |
| Campaign reviews “5–10 days” | Twilio | https://help.twilio.com/articles/1260803225669 | 24 October 2026 |
| Customer Profile “72 hours or more”; manual brand reviews “seven business days or more”; campaign “between 5-10 days” | Twilio | https://help.twilio.com/articles/52182476727195 | 24 October 2026 |
| Sole Proprietor brand “within a few minutes”; OTP within 24 hours; campaign “5-10 days” | Twilio | https://help.twilio.com/articles/52779180539803 | 24 October 2026 |
| Campaign reviews “10–15 days”; “between two to three weeks” | Twilio | https://www.twilio.com/docs/messaging/compliance/a2p-10dlc/direct-standard-onboarding | 24 October 2026 |
| Sole Proprietor vetting “might take several weeks” | Twilio | https://www.twilio.com/docs/messaging/compliance/a2p-10dlc/direct-sole-proprietor-registration-overview | 24 October 2026 |
| New EIN propagation 30–90 days; identity appeal 5–7 business days | Twilio | https://help.twilio.com/articles/4405758341659 | 24 October 2026 |
| Number registration “within minutes … up to 24 hours”; Pending Registration exception; no processing-time guarantees | Twilio | https://help.twilio.com/articles/19622397178139 | 24 October 2026 |
| Full block of unregistered 10DLC from 1 September 2023; error 30034; “at least 3 weeks” (2023 backlog); Voice not subject to the same restrictions | Twilio | https://help.twilio.com/articles/14910496447771 | 24 October 2026 |
| Rejected campaign can be resubmitted “for another review” | Twilio | https://help.twilio.com/articles/15778026827291 | 24 October 2026 |
| Campaign Verify token “1-7 business days” | Twilio, citing Campaign Verify | https://help.twilio.com/articles/4402972441243 | 24 October 2026 |
| Toll-free verification “approximately 3-5 business days”; pending toll-free traffic blocked since 31 January 2024; restricted since 8 November 2023 | Twilio | https://help.twilio.com/articles/5377174717595 | 24 October 2026 |
| Toll-free verification “within three business days” | Twilio | https://www.twilio.com/docs/messaging/compliance/toll-free/api-onboarding | 24 October 2026 |
| Short code “about 4-8 weeks” | Twilio | https://help.twilio.com/articles/30888460607003 | 24 October 2026 |
| Short code “between 6 – 10 weeks” | Twilio | https://help.twilio.com/articles/223134647 | 24 October 2026 |
| Brand “Instant”; vetting 1–7 business days; campaigns before vetting completes | Telnyx | https://developers.telnyx.com/docs/messaging/10dlc/quickstart | 24 October 2026 |
| Carrier provisioning by network (T-Mobile, AT&T, Verizon, US Cellular) | Telnyx | https://developers.telnyx.com/docs/messaging/10dlc/campaign-registration | 24 October 2026 |
| Carrier approval “1-5 business days” | Telnyx | https://developers.telnyx.com/docs/messaging/10dlc/phone-number-assignment | 24 October 2026 |
| AT&T number registration “up to 7 business days” | Telnyx | https://developers.telnyx.com/docs/messaging/10dlc/troubleshooting | 24 October 2026 |
| Telnyx review “same day or next business day”; carrier review “3 business days or less” | Telnyx | https://support.telnyx.com/en/articles/6339152-how-to-create-a-10dlc-campaign | 24 October 2026 |
| Carrier review “72 business hours” | Telnyx | https://support.telnyx.com/en/articles/16256133-10dlc-campaign-compliance-guide | 24 October 2026 |
| Number assignment “about 2 hours … a few days” | Telnyx | https://support.telnyx.com/en/articles/6325734-how-to-assign-a-number-to-a-campaign | 24 October 2026 |
| Toll-free “5 business days or less” | Telnyx | https://support.telnyx.com/en/articles/10729979-toll-free-verification-request-guide | 24 October 2026 |
| Toll-free “1-2 weeks” | Telnyx | https://developers.telnyx.com/docs/messaging/toll-free-verification | 24 October 2026 |
| Short code “about 6 weeks” | Telnyx | https://support.telnyx.com/en/articles/10245573-us-short-code-ordering-process | 24 October 2026 |
| Enforcement from “February 4” (no year on page) | Telnyx | https://support.telnyx.com/en/articles/10509796-10dlc-registration-deadline-february-3 | 24 October 2026 |
| Campaign “1-2 weeks”; unregistered numbers’ messages “will not be delivered” | Plivo | https://old-support.plivo.com/hc/en-us/articles/360054871572-A2P-10DLC | 24 October 2026 |
| Campaign “1-2 weeks”; resubmission takes “the same amount of time” | Plivo | https://old-support.plivo.com/hc/en-us/articles/18193205054361 | 24 October 2026 |
| Number linking “within 48 hours” | Plivo | https://old-support.plivo.com/hc/en-us/articles/24760897700889 | 24 October 2026 |
| Toll-free “24 to 72 hours” | Plivo | https://old-support.plivo.com/hc/en-us/articles/46297538730137 | 24 October 2026 |
| Toll-free “up to two weeks” | Plivo | https://www.plivo.com/blog/toll-free-verification/ | 24 October 2026 |
| Short code “6-8 weeks” | Plivo | https://www.plivo.com/docs/faq/messaging/short-codes/ | 24 October 2026 |
| Approval time “Days”, “Days to weeks”, “Several weeks” | Plivo | https://www.plivo.com/docs/messaging/api/10dlc/overview/ | 24 October 2026 |
| Campaign activation “average of 3 to 5 weeks” | Vonage | https://api.support.vonage.com/hc/en-us/articles/7990660170908-10DLC-Guide-of-guides | 24 October 2026 |
| Brand basic verification “usually takes around 10 seconds”; pending “after 48 hours” contact support | Vonage | https://api.support.vonage.com/hc/en-us/articles/8440856267036-10DLC-FAQ-Brand-verification-issues | 24 October 2026 |
| Authentication+ basic verification “10 seconds and 48 hours” | Vonage | https://api.support.vonage.com/hc/en-us/articles/15852493708444 | 24 October 2026 |
| Number linking “a few minutes to a few hours” | Vonage | https://api.support.vonage.com/hc/en-us/articles/8151004865564 | 24 October 2026 |
| Toll-free “2-10 business days” | Vonage | https://api.support.vonage.com/hc/en-us/articles/360055483251-Toll-Free-Number-Messaging-Registration-US-Canada | 24 October 2026 |
| Short code “8-12 weeks” (US) | Vonage | https://api.support.vonage.com/hc/en-us/articles/115013144287-Short-Codes-Features-Overview | 24 October 2026 |
| Short code “6-10 Weeks” | Vonage | https://api.support.vonage.com/hc/en-us/articles/360050950831-US-Dedicated-Short-Code | 24 October 2026 |
| Campaign review “3-5 business days … could be longer”; T-Mobile provisioning “minutes to a few days”; errors 12219, 4476, 4773; code 6105 | Bandwidth | https://www.bandwidth.com/support/en/articles/12823080-10dlc-campaign-vetting-and-phone-number-provisioning-process | 24 October 2026 |
| Standard campaigns “approved immediately”; specialty “up to a few weeks”; 1 February 2025 block; EIN under 90 days | Bandwidth | https://www.bandwidth.com/support/en/articles/12823085-10dlc-faq | 24 October 2026 |
| Toll-free verification “up to 5 business days” | Bandwidth | https://www.bandwidth.com/support/en/articles/12823247-tfv-handbook | 24 October 2026 |
| Short code carrier submission “6-8 weeks”; internal steps up to 2 and 3 weeks | Bandwidth | https://www.bandwidth.com/support/en/articles/12823236-bandwidth-short-code-handbook | 24 October 2026 |
| 10DLC “Expected Time to Market 1 Week” | Bandwidth | https://www.bandwidth.com/glossary/10dlc/ | 24 October 2026 |
| 10DLC and toll-free “1-5 business days”; 10DLC “within a few days” | Sinch (Sinch Engage) | https://sinch.com/engage/numbers/10dlc-local-number/ | 24 October 2026 |
| Short code “8–12 weeks” | Sinch (Sinch Engage) | https://sinch.com/engage/numbers/short-code/ | 24 October 2026 |
| TCR does not review campaigns; approval time varies; more partners, longer | The Campaign Registry | https://www.campaignregistry.com/resources/ | 24 October 2026 |
| Authentication+ email expires in 7 days; resend up to 30 days | The Campaign Registry | https://www.campaignregistry.com/authentication-enhances-a2p-10dlc-security/ | 24 October 2026 |
| Brand and vetting 1–2 business days (US) / up to 3 weeks (international); campaign up to 4 weeks; number up to 10 days; association approximately 14 days | AWS | https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-10dlc.html | 24 October 2026 |
| Toll-free “up to 15 business days” | AWS | https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-tfn.html | 24 October 2026 |
| First-send sums, floors, ceilings and dates | Zian AI calculation from the rows above | This page (worked calculation) | 24 October 2026 |
Want SMS follow-up that is designed around the registration queue rather than surprised by it? Zian AI is in a partnership-application beta for teams running AI agents across phone calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger. Apply For Partnership