Quick answer: Twilio says to allow approximately 3–5 business days for toll-free verification, and its API docs say it reviews requests within three business days. Add any wait for your Trust Hub profile (Twilio’s 10DLC guide says it “may take 72 hours or more”) and a second review if rejected. Until approved, texts to US and Canadian numbers are blocked with error 30032.
Scope: Twilio’s toll-free verification (TFV) for 8XX numbers texting the US and Canada, covering the Trust Hub profile, the Console and Messaging Compliance API, the business registration number (EIN, CBN, ABN or ACN), the September 2026 policy-URL fields, CTIA opt-in rules, Campaign Verify and A2P 10DLC. Every timing is from Twilio’s help centre or Docs, read 30 October 2026.
Where Zian fits while a toll-free number is in review
File the toll-free verification before you switch an AI agent on, because nothing the agent writes reaches a US or Canadian handset until Twilio approves the number. Zian AI’s agents answer inbound calls 24/7 as an AI receptionist and follow up by voice calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger, so a verification queue changes which channel carries the first touch rather than stopping follow-up altogether.
Twilio says the toll-free messaging restrictions “do not apply to Voice or any other non-SMS use of that TF number” (Twilio, Toll-Free Verification and Developers). SmartReach AI™ orchestrates message, channel and timing for each lead. During Zian’s partnership-application beta, whose business details a toll-free registration is filed 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. If you would rather hand the whole programme over, LeadsNow.ai runs managed, pay-per-result appointment setting on Zian.
How long does toll-free verification take on Twilio?
Twilio publishes two different windows for the same review, on three pages, and none of them is a guarantee. Here is which page says what, with its hedge words intact:
- “approximately 3-5 business days” — Toll-Free Message Verification for US/Canada (help centre, updated 1 June 2026): “Upon receipt of your submission, Twilio reviews and processes your verification request. Please allow approximately 3-5 business days for this process.”
- “can take approximately 3-5 business days” — Best Practices for Using Toll-Free SMS and MMS in the US and Canada (help centre, updated 14 May 2026): “The Toll-Free traffic verification process can take approximately 3-5 business days for completion.”
- “within three business days” — Get started with toll-free verification using the API (Twilio Docs, modified 18 September 2026): “Twilio reviews TFV requests within three business days.”
The two help articles agree; the Docs page, the newest of the three, is the outlier. Both help articles carry the label “legacy Twilio Console”, so the honest reading is a published range of three to five business days, with three as the API guide’s ceiling. We plan to five. We found no Twilio toll-free page giving a time for the priority re-review after a rejection, or for a request deleted and resubmitted, which the Console guide says “puts the new verification request in the back of the review queue”.
The one-line version worth remembering: Twilio’s toll-free review is a three-to-five-business-day queue, and the clock that actually moves your launch date is the second queue after a rejection.
The Twilio toll-free verification timeline, step by step
Toll-free verification on Twilio is one review, but it sits inside a short chain of steps. The table lists each step, who acts, what Twilio publishes for it and where. “Not published” means we could not find a time for that step on the Twilio toll-free pages listed in the source table, as at 30 October 2026.
| Step | Who acts | Published time, exact wording | Source (read 30 October 2026) |
|---|---|---|---|
| 1. Upgrade from trial | You | No time; Twilio’s Console guide says TFV needs “a paid Twilio Account (not in trial)” | Twilio Docs, Console onboarding guide |
| 2. Primary compliance profile (Business Profile) in Trust Hub | You submit; Twilio reviews | “may take 72 hours or more” (stated in Twilio’s 10DLC registration guide; not published on the toll-free pages) | Twilio, Direct Standard registration guide (updated 27 Oct 2026) |
| 3. Buy or port the toll-free number | You | No time for a purchase. A toll-free port “Normally … takes anywhere from 1-4 weeks, though this process can take longer” if the losing carrier rejects it, and toll-free SMS routing to Twilio “usually takes an extra 2-3 business days” after the port (Twilio porting articles). Ported or hosted numbers: verify “as soon as a hosting or porting order is completed” | Twilio, Hosted and Ported Numbers |
| 4. Submit the TFV request (Console or API) | You | Status starts as Pending review (Console) or PENDING_REVIEW (API) | Twilio, How do I register a toll-free number |
| 5. Verification Ops review | Twilio | “approximately 3-5 business days” (help); “within three business days” (Docs) | Twilio help; Twilio Docs |
| 6a. Approved | Twilio | Status TWILIO_APPROVED; default throughput “3 SMS segments per second” | Twilio help |
| 6b. Rejected, resubmittable | You fix; Twilio re-reviews | Seven-day edit window for a priority re-review; no re-review time published | Twilio Docs, Console guide; error 30437 |
| 6c. Rejected, window missed or deleted | You resubmit | Goes into “the same queue as new toll-free verification requests” | Twilio Docs, Console guide |
Two rows decide most timelines. First, the profile. In the current Twilio Console, “Create registration stays disabled until you have an approved primary compliance profile” (Twilio), so on a new account the profile review sits on the critical path. The API is more forgiving: the Docs say that if you do not have a Trust Hub customer profile, “you can create one at the same time as submitting your TFV request”. Individual profiles do not qualify; Twilio says toll-free verification “requires a Business profile with a legal entity or business name” (Twilio). Second, the rejection branch, covered in the calendar below.
A worked calendar: submitting on Monday 2 November 2026
We counted business days by script, skipping weekends. The rules: the Docs’ “within three business days” is the floor and the help centre’s five is the ceiling; the “may take 72 hours or more” for the profile (a figure from Twilio’s 10DLC registration guide; the toll-free pages publish none) counts as three calendar days with a plus sign; a fix takes one business day; and a priority re-review is assumed to take the same three to five business days, because Twilio publishes no figure for it. Veterans Day (Wednesday 11 November 2026) is a US federal holiday; Twilio does not say whether its business days skip it, so we did not, and a real date could land a day later.
| Scenario | Business days counted | Earliest first send to a US or Canadian handset |
|---|---|---|
| A. Approved profile already on the account | 3 to 5 | Thu 5 Nov 2026 to Mon 9 Nov 2026 |
| B. New account, Console route: profile first | 3 calendar days (+), then 3 to 5 | Tue 10 Nov 2026 to Thu 12 Nov 2026, later if the profile takes “more” |
| C. Scenario A, rejected on day 3, fixed next day | 3 + 1 + 3 to 5 | Wed 11 Nov 2026 to Fri 13 Nov 2026 (re-review time assumed) |
| D. Scenario A, rejected on day 5, fixed next day | 5 + 1 + 3 to 5 | Fri 13 Nov 2026 to Tue 17 Nov 2026 (re-review time assumed) |
Scenario D worked: Monday 2 November plus five business days is Monday 9 November; the fix takes Tuesday 10 November; three to five more business days lands on Friday 13 to Tuesday 17 November.
The seven-day edit window: Twilio’s pages disagree on when it starts
Scenario D exposes a real ambiguity. Twilio’s Docs API guide says of the edit_expiration property: “Twilio sets this property value to seven days from the initial request” (Twilio Docs), and the error 30032 page repeats “seven days from the initial request” (Twilio Docs, 30032). But the error 30437 page lists as a cause “You did not update and resubmit the rejected verification within seven days of the rejection” (Twilio Docs, 30437), the Console guide says “you have seven days to resubmit”, and the help-centre rejection article says the review process “gives you seven days to amend a rejected submission while retaining its review priority” (Twilio help).
If the window runs from the initial request, a rejection that arrives on business day five (Monday 9 November in our example, exactly seven calendar days after submission) leaves you no priority window at all. If it runs from the rejection, you have until Monday 16 November. Do not guess: read edit_allowed and edit_expiration on the record, or the “days left” message on the number’s Regulatory Information tab, the moment a rejection lands.
Planning an SMS launch around a toll-free number? Zian’s agents answer inbound calls 24/7 and follow up by voice, SMS, email and WhatsApp, with SmartReach AI™ pacing each touch while a sender is in review. Apply For Partnership
What Twilio asks for in a toll-free verification in 2026
A complete submission keeps the timeline at its floor. Twilio’s Docs: “To reduce review times and minimize the risk of rejection, provide your business registration number and related details.” What the Twilio pages read on 30 October 2026 require:
- Required API fields. The Docs list ten as required: business name, business website, notification email, use-case categories, use-case summary, production message sample, opt-in image URLs, opt-in type, estimated monthly message volume and the toll-free number’s SID (Twilio Docs). The same Docs page, modified 18 September 2026, still marks the Privacy Policy and Terms URL fields Optional; Twilio’s onboarding guide says submissions missing them are rejected, so treat both as required.
- Business registration number (newer, now mandatory). Twilio’s policy article says BRNs could be supplied from 30 September 2025 and that “Beginning February 17th 2026, BRNs will be mandatory for all new TFV submissions” (Twilio). The Docs mark the number, authority and country “Required for all business types except SOLE_PROPRIETOR”. US entities give a 9-digit EIN matching the IRS CP 575 or 147C letter; organisations outside the US give their national number, issuing country and registration authority. The accepted authority values include ABN and ACN, so an Australian company can file with its own number.
- Separate Privacy Policy and Terms URL fields (newest). Twilio’s onboarding guide: “Starting September 15, 2026, toll-free verification submissions must include separate URL fields for your Privacy Policy and Terms and Conditions. Submissions missing these links will be rejected with error 30493. This applies to new submissions only; existing verifications do not need updates.” (Twilio)
- The end business, not the platform. If you are an ISV or agency, “you must use the end business’s details, including their Legal Name, website, address, and contact information, rather than your own agency’s information”. Twilio’s ISV guide allows an exception where the ISV manages opt-in and is the sole content creator.
- Opt-in that a reviewer can open. A direct https:// link to where numbers are collected, checkboxes that “must load blank and unchecked by default”, optional consent, separate opt-ins per message type, and disclosures beside the phone field: business name, message type, frequency, rates and HELP/STOP.
- A privacy clause, verbatim. The checklist asks for: “All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.”
- Volume and number count. Volume is chosen from fixed increments (10 up to 10,000,000+). Up to five numbers per entity is standard; more needs a justification in the additional information field.
- Political senders. A 527 organisation using POLITICAL_ELECTION_CAMPAIGNS “MUST provide a Campaign Verify (CV) token”, obtained from Campaign Verify before you file.
Can I send texts while my toll-free verification is pending?
No, not to US or Canadian handsets. Twilio’s status table says “As of January 31, 2024, ALL Pending traffic is blocked in the US”, and Restricted numbers (never submitted, or not approved) have been blocked since 8 November 2023 (Twilio). Blocked messages “will return Error 30032 (any message sent from a Restricted or Pending TFPN) or Error 30007 (if spam/unwanted on a verified TFPN), and are subject to messaging fees.” A pending number costs you money if your agent keeps sending.
What still works while you wait, on Twilio’s own pages:
- Voice. The restrictions “do not apply to Voice or any other non-SMS use of that TF number or SMS messages sent to numbers outside the US” (Twilio).
- Testing. Twilio’s Virtual Phone is useful “while you’re waiting for that Toll-Free verification application to be processed”, because messages to it never cross a carrier network.
- Ported numbers already verified elsewhere. Verification does not transfer between providers, but Twilio says your toll-free SMS traffic “should remain treated as Verified until your new submission (via Twilio Console/API) is reviewed”. Submit only after the port completes, or the request may be rejected with error 30447 (Twilio).
In the Console guide’s status table a rejected but resubmittable number shows as Pending, reverting to Restricted after seven days; a non-resubmittable one is Blocked. All three block US and Canadian traffic. A pending appeal changes nothing either: Twilio says “A pending correction or appeal does not verify the number” (Twilio). If you are seeing 30007 on a number that is already verified, that is filtering, not verification, and our guide to AI SMS carrier filtering and error 30007 covers the diagnosis.
Why toll-free verifications get rejected on Twilio, and the fix for each
Twilio’s rejection article tabulates 127 distinct error codes as at 30 October 2026, counted by script from its tables, and says the guidance is written for rejections under its 15 September 2026 release (Twilio). The decoder below picks the codes most likely on a business submission; each fix is Twilio’s instruction, shortened. Use the code you actually received: Twilio warns “do not substitute another code because its title looks similar.”
| Code | What Twilio says it means | The fix |
|---|---|---|
| 30445 | Business information could not be verified | Make business name, corporate website and email domain agree; “Any mismatch on the information or confusing details can cause this denial.” |
| 30472 / 30527 | Business registration details missing or invalid | Give a verifiable BRN, with entity type, registration type and issuing country; name and number must “align character-by-character” with official documents. |
| 30484 | Business name must match official records | Use the legal name; put trade names in the DBA field. |
| 30474 | End business details must be accurate and complete | ISVs file each client separately, on a dedicated toll-free number, with the client’s details. |
| 30489 / 30491 | Website not established, or behind a login | Submit a live, public site with business information and contact details, or a screenshot if it cannot be public. |
| 30476 | No opt-in provided | Supply the opt-in URL or attach the image. |
| 30505 | Agreeing to receive messages must be optional | Let users complete the form without opting in; tie consent to the checkbox, not the submit button. |
| 30508 | Opt-in checkbox is pre-selected | Remove pre-ticked options. |
| 30518 | Call-to-action missing required disclosures | Add business name, message type, frequency, rates, STOP and HELP, plus Terms and Privacy Policy links. |
| 30493 | Terms of Service missing, inaccessible or incomplete | Publish public Terms with SMS rates, frequency and opt-out wording. Since 15 September 2026 Privacy Policy problems are a separate code, 30536. |
| 30536 | Privacy Policy URL missing, inaccessible or empty | Provide a live Privacy Policy with the required disclosures. |
| 30496 | Use case and summary inconsistent | Describe every selected use case in the summary. |
| 30525 | Public URL shorteners not allowed | Use a branded URL or a privately owned branded short domain. |
| 30468 and the Disallowed family | Prohibited content, for example third-party lead generation | Do not continue that messaging; resubmission “does not permit prohibited content”. |
| 30437 | Submission editing timed out | Resubmit anyway; it loses priority and joins the standard queue. |
Resubmission, in Twilio’s words. The rejection article says that “corrected or misclassified submissions can be resubmitted for review” for the denial reasons it lists, and that you must not “change only its description to obtain approval”. The older overview article puts it more bluntly: “Rejections for content, or Acceptable Use Policy / Messaging Policy violations are ineligible, and can’t be re-submitted” (Twilio). In the Console, a rejected registration keeps its previous values and offers Edit & resubmit (Twilio). Deleting and recreating the request is the last resort; Twilio says it sends you to the back of the queue. For an AI agent, the samples and opt-in you file are where most rejections start, and our page on 10DLC and toll-free campaign rejections for AI SMS agents covers how to register messages a model writes fresh.
Toll-free verification vs A2P 10DLC on Twilio
The two US routes ask for much the same evidence (identity, use case and samples, opt-in), but they run on different clocks and costs. The 10DLC side of this table is summarised; the stage-by-stage 10DLC figures are on our page about how long A2P 10DLC registration takes.
| Question | Toll-free verification | A2P 10DLC |
|---|---|---|
| Review steps | One Twilio Verification Ops review after the profile | Profile, brand, campaign vetting, then number registration |
| Published review time | Approximately 3–5 business days (help); within three business days (Docs) | 5 to 23+ business days summed on Twilio’s stage figures (our 10DLC page) |
| Registration fee | “Twilio offers this verification service free of cost” | “A2P 10DLC registration is NOT free”: one-time and monthly fees |
| Business ID | BRN required except for sole proprietors | US EIN or non-US tax ID; Sole Proprietor route for individuals |
| Default throughput | 3 SMS segments per second, can be increased | Varies with the brand’s Trust Score |
| Sending while pending | Blocked to US and Canada (30032) | Blocked from unregistered 10DLC numbers |
| Who reviews | Twilio’s Verification Ops, with carrier approval | Third-party vetting partners and carriers |
Sources for the table: free of cost (Twilio best practices); “NOT free” (Twilio developers article); business ID and throughput (Twilio number-type comparison and Twilio toll-free MPS); Verified status “Upon a successful review of your verification submission and carrier approval” (Twilio). Fees for the 10DLC side are on our page about A2P 10DLC costs for two-way AI SMS agents. Twilio points individuals without a business tax ID to the 10DLC Sole Proprietor route instead.
What makes a Twilio toll-free verification take longer
We found no single Twilio page listing what delays a toll-free review, but its pages name the things that push a request off its three-to-five-day track:
- No approved Business Profile. In the current Console you cannot create the registration until the primary profile is approved, and an Individual profile will not do.
- Trial accounts. The Console guide makes a paid account a prerequisite. An older help article (updated September 2025) still describes trial accounts completing verification and then sending only to verified numbers, so if you are on a trial, upgrade before you file rather than test which page is current.
- Submitting a port too early. A request filed before the port completes “may be rejected with error 30447”.
- Mismatched identity. A legal name that differs from the IRS letter by punctuation, spacing or a DBA fails BRN validation; Twilio says to avoid “helpful” edits.
- A new business. Twilio’s BRN article has a step headed “Account for Timing (New Businesses)”: if the inputs are right and validation still fails, open a ticket with the verification ID and your CP 575 or 147C letter.
Twilio does say what can speed things up. Its Docs ask for business metadata “To avoid rejection and accelerate vetting”, and the onboarding guide says the additional information field “may accelerate approval” when it explains a complex opt-in, a data mismatch or a high-risk-looking model. That is the whole of the published acceleration path; we found no paid or support-ticket expedite on Twilio’s toll-free pages as at 30 October 2026.
What it costs to run toll-free verification yourself
The verification itself is free on Twilio, so the cost is people and time. One business, one number, done carefully, is an afternoon of gathering the EIN letter, policy URLs, opt-in screenshots and samples, then three to five business days of waiting. The work multiplies with every client: Twilio wants each end business filed separately on its own number, with Terms and a Privacy Policy that match its opt-in page, and each rejection starts a seven-day window someone has to watch. Twilio offers ISVs a free Compliance Embeddable to collect this inside their own app. Count your clients, multiply by the ceiling above, and decide whether that is a side task or a job.
Frequently asked questions
How long does toll-free verification take on Twilio?
Twilio publishes two windows for the review itself. Two help-centre articles say to allow “approximately 3-5 business days”, and the Twilio Docs API guide says Twilio “reviews TFV requests within three business days”. If your primary compliance profile is not yet approved, add that step first: Twilio’s 10DLC guide says profile approval “may take 72 hours or more”.
Can I send SMS from my Twilio toll-free number while verification is pending?
Not to the US or Canada. Twilio’s Toll-Free Message Verification article says that since 31 January 2024 messages from Restricted or Pending toll-free numbers are blocked, return error 30032 and “are subject to messaging fees”. Voice calls, SMS to numbers outside the US, and tests to Twilio’s Virtual Phone are not blocked.
Why was my Twilio toll-free verification rejected?
Twilio’s rejection article lists 127 distinct error codes as at 30 October 2026, grouped into submission status, business identity, consent and opt-in, Terms and Privacy Policy, and prohibited content. The commonest fixable ones are a business name or registration number that does not match official records, a missing or pre-ticked opt-in, and missing Terms or Privacy Policy links.
How long do I have to fix a rejected toll-free verification?
Seven days, but Twilio’s pages disagree on when the clock starts. The Docs API guide sets edit_expiration to “seven days from the initial request”, while error 30437 refers to “seven days of the rejection”. Inside the window your resubmission goes to a priority queue; after it, the request goes to the standard queue.
Do I need an EIN or business registration number for Twilio toll-free verification?
Yes, for every business type except a sole proprietor. Twilio’s policy article says the registration number became mandatory for new submissions from 17 February 2026. US businesses give a 9-digit EIN that matches IRS records; others give their national number, issuing country and authority, and Twilio’s list of accepted authorities includes ABN and ACN for Australia.
Is toll-free verification faster than A2P 10DLC on Twilio?
On Twilio’s own figures, usually. Toll-free review is approximately 3–5 business days in one review step, while 10DLC runs a brand, a campaign vetting stage and number registration in sequence. Toll-free verification is also free, where Twilio says A2P 10DLC registration “is NOT free”. Neither route sends to US handsets while pending.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Approximately 3-5 business days; status table; pending blocked since 31 Jan 2024; restricted blocked since 8 Nov 2023; 30032 and fees; 3 segments per second; ported numbers stay Verified; content rejections not resubmittable | Twilio | https://help.twilio.com/articles/5377174717595 | 30 October 2026 |
| Can take approximately 3-5 business days; free of cost; short codes best for high-volume marketing | Twilio | https://help.twilio.com/articles/360038172934 | 30 October 2026 |
| Reviews TFV requests within three business days; edit_expiration seven days from the initial request; ten required fields; BRN required except SOLE_PROPRIETOR; Campaign Verify token | Twilio Docs | https://www.twilio.com/docs/messaging/compliance/toll-free/api-onboarding | 30 October 2026 |
| Paid account prerequisite; seven days to resubmit for priority review; standard queue after; deleting goes to the back of the queue | Twilio Docs | https://www.twilio.com/docs/messaging/compliance/toll-free/console-onboarding | 30 October 2026 |
| Seven days of the rejection; standard queue after expiry | Twilio Docs | https://www.twilio.com/docs/api/errors/30437 | 30 October 2026 |
| Seven days from the initial request | Twilio Docs | https://www.twilio.com/docs/api/errors/30032 | 30 October 2026 |
| 127 distinct error codes; 15 Sep 2026 release; seven days to amend; pending appeal does not verify | Twilio | https://help.twilio.com/articles/9321443984155 | 30 October 2026 |
| Privacy Policy and Terms URL fields from 15 Sep 2026; error 30493; end-business details; volume increments; five-number limit; verbatim privacy clause | Twilio | https://help.twilio.com/articles/13264118705051 | 30 October 2026 |
| BRN optional from 30 Sep 2025, mandatory from 17 Feb 2026; 9-digit EIN; ABN and ACN accepted | Twilio | https://help.twilio.com/articles/38266268244507 | 30 October 2026 |
| Restrictions do not apply to Voice or non-US SMS; Virtual Phone; 10DLC is NOT free | Twilio | https://help.twilio.com/articles/20212966914075 | 30 October 2026 |
| Create registration disabled until profile approved; Pending review, In review, Approved or Rejected | Twilio | https://help.twilio.com/articles/55716218497563 | 30 October 2026 |
| Individual profiles not eligible for toll-free | Twilio | https://help.twilio.com/articles/37852251306011 | 30 October 2026 |
| Customer Profile may take 72 hours or more | Twilio | https://help.twilio.com/articles/52182476727195 | 30 October 2026 |
| BRN required except sole proprietorships; 10DLC throughput by Trust Score | Twilio | https://help.twilio.com/articles/360038173654 | 30 October 2026 |
| Default 3 MPS on toll-free | Twilio | https://help.twilio.com/articles/4411046744987 | 30 October 2026 |
| ISV exception where the ISV manages opt-in and content | Twilio | https://help.twilio.com/articles/13263383206299 | 30 October 2026 |
| Verify ported or hosted numbers once the order completes | Twilio | https://help.twilio.com/articles/19613116154907 | 30 October 2026 |
| Rejected registration keeps its values; Edit and resubmit | Twilio | https://help.twilio.com/articles/55716210376091 | 30 October 2026 |
| Toll-free port normally 1-4 weeks, longer after a carrier rejection | Twilio | https://help.twilio.com/articles/223131767 | 30 October 2026 |
| Toll-free SMS routing usually an extra 2-3 business days after a port | Twilio | https://help.twilio.com/articles/223131807 | 30 October 2026 |
| Trial accounts complete verification and use the Virtual Phone (updated September 2025) | Twilio | https://help.twilio.com/articles/11853148778523 | 30 October 2026 |
| Compliance Embeddable offered for free | Twilio | https://help.twilio.com/articles/31769870199707 | 30 October 2026 |
Business days in the worked calendar were counted by script from the published windows above, under the rules stated in that section. The priority re-review time is our assumption; Twilio publishes none.
Want your follow-up running on the channels that are open while a sender is in review? Zian is in partnership-application beta. Apply For Partnership