Quick answer: Twilio’s general bundle article gives two review windows, “up to two business days” and “up to 3 business days” plus any mailer time. Its UK KYC article gives none. Its Australian KYC article says up to 5 business days. Telnyx says about 72 hours once it has your documents. One rejection more than doubles the wait: 7 business days in the UK or 11 in Australia, if the fix takes a day and (our assumption) the resubmission gets a full window.
If you’re asking “how long does Twilio regulatory bundle approval take?” because an AI voice agent is ready and the UK (+44) or Australian (+61) number isn’t, this page gives you the answer three ways. First, what Twilio and Telnyx each publish, word for word and dated. Second, a day-by-day timeline for a UK and an Australian business bundle. Third, all 21 of Twilio’s listed rejection reasons with the fix for each. Everything about Twilio comes from its help centre, its GB and AU regulatory guideline pages and its Regulatory Compliance API reference. Everything about Telnyx comes from Telnyx’s own requirement pages. On the regulators (Ofcom in the UK; ACMA and the Scams Prevention Framework in Australia), we report only how the providers describe them.
This is the UK and Australian companion to our US AI voice agent go-live timeline, which covers A2P 10DLC and toll-free verification. For choosing an Australian number type in the first place, see our guide to Australian +61 numbers for AI voice agents. This page covers only the bundle clock.
How long does Twilio regulatory bundle approval take? Three published windows
Twilio publishes three different review windows, and two of them are in the same article. Here they are verbatim, with the article and the date Twilio last updated it. Telnyx’s figures are included for comparison. Note that they are in hours, not business days.
| Provider | Where it says it | Last updated | Exact wording | What it covers |
|---|---|---|---|---|
| Twilio | How to Submit a Regulatory Bundle, step list | 14 May 2026 | “the review process will take up to two business days” | All regulatory bundles (not country-specific) |
| Twilio | Same article, “Regulatory Bundle approval process” section | 14 May 2026 | “The approval process may take up to 3 business days, plus any processing time for mailer delivery confirmation.” | All regulatory bundles (not country-specific) |
| Twilio | Know Your Customer (KYC) in Australia, FAQ | 3 June 2026 | “The review can take up to five business days.” | Australian local, mobile and toll-free bundles |
| Twilio | UK KYC Regulatory Framework | 22 May 2026 | No review duration stated | UK long codes (local, national, mobile, toll-free) |
| Telnyx | United Kingdom (UK) DID Requirements | No date shown on the page (page metadata: 17 July 2026); read 24 Sep 2026 | “once the documentation is received, it will take approximately 72 hours to validate the information and activate the number for use” | UK local, national, toll-free and mobile |
| Telnyx | Australia DID Requirements | No date shown on the page (page metadata: 17 July 2026); read 24 Sep 2026 | “once the documentation is received it will take approximately 72 hours to validate the information and activate the number for use” | Australian numbers |
Twilio’s own help centre disagrees about the review window: “up to two business days” and “up to 3 business days, plus any processing time for mailer delivery confirmation” appear in the same article. We have not picked one and hidden the other. Neither sentence mentions a country. The UK KYC article gives no duration. The Australian article’s five business days is the only country-specific number of days we found in Twilio’s help centre for a bundle review in either market. Twilio’s United Kingdom Porting and Australia Porting articles, which also send you to Bundles, say only that “Processing of the compliance documents may take up to several business days.” Twilio’s submission article doesn’t say which countries need a mailer. So the mailer clause is open-ended, and we can’t tell you whether it applies to a UK bundle.
For planning, use the longest window that could apply. That is 3 business days for a UK bundle, plus mailer time if Twilio asks for one, and 5 business days for an Australian bundle. None of the articles says whose business days these are: a UK, Australian or US calendar. So a public holiday in any of them can stretch the window.
A day-by-day timeline for a UK and an Australian business bundle
The table below assumes a business applicant, one rejection, and one business day to fix it. It uses Twilio’s longer UK window (3 business days) and its Australian window (5). It also assumes the resubmission gets a full window again. Twilio doesn’t publish a separate window for resubmitted bundles, so this is a planning assumption, not a Twilio figure. The status column uses five of the six status values in Twilio’s Bundles API reference. The sixth, provisionally-approved, is listed as a possible value but is not described in that page’s status table.
| Business day | UK business bundle (local or national number) | Australian business bundle (local number) | Bundle status you will see |
|---|---|---|---|
| Before day 0 | Collect business name, registration authority and number, website, a UK business address, and the authorised representative’s name, mobile number and work email. The GB guideline lists “No documentation required” against each business field. | Get the ASIC long form extract (it shows officer names and business address), the ABN or ACN, an Australian street address (no PO Box) with proof, the representative’s ID, and an LOA if the representative is not on the extract. | none yet |
| 0 | Create the bundle, attach End-User and Supporting Documents, run an Evaluation, submit. | draft → pending-review (status callback fires) |
|
| 1–3 (UK) / 1–5 (AU) | Twilio reviews the bundle. Build and test the agent on a test number in the meantime. | pending-review → in-review (no callback for this change) |
|
| 3 (UK) / 5 (AU) | Latest published result day. Email from [email protected] to the bundle’s notification address. | twilio-approved or twilio-rejected |
|
| 4 (UK) / 6 (AU) | If rejected: read the reason on the bundle and on each Supporting Document, fix it, “Edit and Resubmit”. | pending-review |
|
| 5–7 (UK) / 7–11 (AU) | Second review, assumed to take the full window again. | in-review |
|
| 7 (UK) / 11 (AU) | Approved: buy the number, or assign the bundle to numbers you already own. The agent can now go live on that number. | twilio-approved |
|
The review itself is not the slowest part. On an Australian business bundle, a first-time approval takes up to 5 business days. The same bundle rejected once takes up to 11, if the resubmission gets a full window again. All six extra days come from the rejection: one more review window plus one day to fix it.
The stage that takes longest is the rejection, not the review
We call this the Rejection Multiplier: each rejection adds a full review window plus your fix time. The formula is below, so you can put in your own numbers.
Total business days = W × (R + 1) + F × R, where W is the review window, R is the number of rejections, and F is the business days you spend fixing each one. Add your own preparation time before day 0. No provider publishes that, because it depends on how fast you can get the documents together.
| Scenario | W (business days) | R | F (business days) | Arithmetic | Total business days |
|---|---|---|---|---|---|
| UK, approved first time, using Twilio’s shorter figure | 2 | 0 | – | 2 × 1 | 2 |
| UK, approved first time, using Twilio’s longer figure | 3 | 0 | – | 3 × 1 | 3 (plus any mailer time) |
| UK, one rejection, fixed in a day | 3 | 1 | 1 | 3 × 2 + 1 × 1 | 7 |
| AU, approved first time | 5 | 0 | – | 5 × 1 | 5 |
| AU, one rejection, fixed in a day | 5 | 1 | 1 | 5 × 2 + 1 × 1 | 11 |
| AU, two rejections, each fix needs a director’s signature (2 days) | 5 | 2 | 2 | 5 × 3 + 2 × 2 | 19 |
On the same full-window assumption, two rejections turn a one-week wait on an Australian bundle into nearly four working weeks: 19 business days against 5. That is why the useful question is not how long review takes. It is how to avoid a rejection. The next three sections deal with that.
A worked example with real inputs: your agent passed testing on a Monday, and you submit an Australian local-number bundle that afternoon. That is day 0. If the representative isn’t on the ASIC extract and you didn’t include an LOA, the rejection can arrive as late as day 5, the following Monday. The director signs on day 6, you resubmit, and the second window, assumed to be a full five business days, ends on day 11. That is the Tuesday of the third week, before any public holidays. With the LOA in the first submission, the latest approval date would have been day 5.
What a UK bundle needs, and the two traps for AI voice agent teams
Twilio’s UK KYC article sets out its rollout dates. From 27 May 2024, “all new long code purchases require an approved Regulatory Compliance (RC) bundle before buying”. From 30 September 2024, all UK long codes needed an approved bundle. From January 2025, non-compliant numbers “may be expected to experience brownouts”. Twilio says it is implementing updated KYC guidelines from the UK regulator and ties the September 2024 date to “Ofcom’s new regulatory guidelines”. We report that as Twilio’s description. Ofcom’s own guidance was not reachable from our research environment, so we have not quoted it. The rule covers “local, national, mobile, and toll-free phone numbers”.
For a business, Twilio’s GB regulatory guideline page lists “No documentation required” against every business field for every UK number type. That includes business name, registration number, address, authorised representative and business classification. So on a UK business bundle, the rejections you are most likely to see are field and data-matching reasons, not document reasons. That is our inference from the guideline page; Twilio does not say it. Individuals still upload a government-issued ID and, for local numbers, a proof of UK address.
Trap one: the non-UK company. UK local and national numbers need “a valid United Kingdom address”. Twilio’s answer for a business that isn’t registered in the UK is direct: “You should use UK mobile or UK toll-free phone numbers.” For those number types, the guideline says the address “May be anywhere in the world”. If you are an Australian or US company launching an AI voice agent into the UK, choose the number type before you start the bundle. A local-number bundle for a company with no UK address is a rejection you can predict.
Trap two: the representative’s phone number. The GB guideline says the authorised representative’s phone number “must be a valid mobile number only where the customer can be reached. This cannot be a number which you’ve acquired from a CPaaS provider such as Twilio.” Teams that build voice agents often have a Twilio number close at hand and use it as their contact line. On this form, that will fail. Use a real person’s mobile.
Two more points from Twilio’s UK FAQ. First, “there are no fees to register UK long codes”. Second, each number should sit under the bundle of the business that owns it, and one bundle can cover many numbers. So a company with ten UK local numbers needs one approved bundle for them, not ten.
What an Australian bundle needs in 2026, and why it may change
Twilio’s Australian KYC article begins with a notice. The requirements are tied to the Scams Prevention Framework, and Twilio is “currently awaiting the final requirements from the regulator”. As at its 3 June 2026 update it says: “Final guidelines from regulators have not yet been issued.” Twilio’s AU guideline page adds that “The regulatory updates outlined herein are applicable to porting services as well.” So a number you port in from another carrier faces the same checks. Read the article again on the day you submit. What follows is what Twilio published as of that update.
For a business, Twilio asks for:
- the business name and ABN or ACN;
- the ASIC Current Company Extract or Record of Registration. Twilio says “All businesses must provide the long form extract, which includes the officer names and business address”;
- an address and proof of it. For local numbers the address “Must be an address within Australia (not a PO Box)”. For mobile and toll-free it “May be located anywhere in the world”;
- the authorised representative’s name, government-issued ID or passport, and contact email;
- proof of authorisation. No LOA is needed if the representative is listed on the extract as a director or officer (Twilio’s AU guideline page also accepts an “other official contact person” listed there). If they aren’t listed, a director named on the extract signs one.
The AU guideline page adds two points about the representative’s email that cause rejections. For local-number business bundles: “Use of personal email domains may require additional vetting; alias emails are not permitted.” For toll-free business bundles, that email’s domain “should match business name or website”. Twilio also lists one reason specific to Australia on its rejection page: “ABN/ACN number might be missing in Document number field”. As covered in the rejection table below, Twilio’s best-practice guidance says the Business ID Number for an AU mobile bundle goes into the Document Number field, because no field has that name.
Australian local numbers also carry a note on the AU guideline page. If the number comes from a different charging district from the one you use it in, calls to it “will be charged as if you were located within the relevant charging district”, and “You may not be able to port the number to another service provider.” For more on choosing between local, 1300/1800 and mobile numbers for an outbound agent, see the Australian number types guide. It covers that decision; this page covers only the bundle.
Why was my regulatory bundle rejected? All 21 of Twilio’s listed reasons, with the fix
Twilio lists 21 reasons a Supporting Document can be rejected. They are all below in Twilio’s wording, not just the ones about UK and AU requirements. Where a reason doesn’t normally apply to a UK or Australian bundle, the table says so and gives the reason. Twilio also gives one general reason, “The document you have uploaded does not match our Regulatory Requirements criteria”, for any document that doesn’t meet a country’s requirements. Its example is a screenshot of an email about utility costs uploaded instead of an actual utility bill. The Australia-specific reason is covered in the section above.
| # | Twilio’s rejection reason (verbatim) | Where it shows up on a UK or AU bundle | Fix |
|---|---|---|---|
| 1 | The Supporting Document is not legible. Please upload a readable Supporting Document. | Any uploaded document: the ASIC extract, an ID, a proof of address. | Re-upload a clean scan. Twilio’s ID rules ask for a colour scan, not a photo, with every edge and corner visible. |
| 2 | The Supporting Document you uploaded has expired or it does not show an expiration date. Please provide a valid Supporting Document. | The authorised representative’s ID or passport. | Upload an ID that is in date and shows its expiry date. |
| 3 | The Proof of Identity needs to show the front and back of the ID. Please upload a copy of the front and back of the ID. | An ID card used as proof of identity. | Merge front and back into one file and upload it into one document category, as Twilio’s best-practice table asks. |
| 4 | The Authorized Representative is not shown on the Business Registration. Please upload a Supporting Document that shows the Authorized Representative of the business. | AU business bundles where the person submitting is not an officer on the ASIC extract. | Either upload the long form extract that lists them, or add a Letter of Authorization signed by a director named on that extract. |
| 5 | Please upload the Supporting Document without any redactions/information covered. | Any document with a field blacked out, often a masked ID number. | Upload the unredacted document. Twilio’s best-practice table says contents “cannot be redacted”. |
| 6 | You’ve uploaded Business Registration as a Supporting Document. Please ensure the Business Registration shows the legal representative and upload an ID of the legal representative. | AU business bundles that include the registration but not the representative’s ID. | Make sure the registration names the legal representative, then upload that person’s government-issued ID. |
| 7 | A Letter of Authorization (LOA) is required. The LOA needs to be signed and recently dated. | AU business bundles where the representative is not on the extract. | A director named on the extract signs and dates the LOA. Twilio says “recently dated” without giving a number of days, so sign it the day you submit. |
| 8 | Business Registration is missing. Please upload Business Registrations as a Supporting Document. | AU business bundles (the proof of business identity). | Upload the Current Company Extract or Record of Registration from ASIC. Twilio asks for the long form extract that shows officer names and business address. |
| 9 | Please provide a document issued in the last three months. | Proof of address, most often for individuals. | Twilio’s rule is 3 months for an individual’s address document (unless an ID confirms the address) and 1 year for a business’s. Get a newer utility bill or a bank statement, which Twilio accepts for all bundle types. |
| 10 | There is missing information. Please fill out the required form fields. | Both markets: a required field left empty. | Fill every required field. For an AU mobile bundle, Twilio says the Business ID Number goes into the Document Number field, because no field carries that name. |
| 11 | Please amend information provided in the Regulatory Bundle, the data does not match the Supporting Document provided. | Both markets: typed data that differs from the document. | Type every field exactly as it appears on the document: the full legal name, not an abbreviation or a trading name, unless a document confirms the trading name. |
| 12 | The date of birth indicates an age under 18. Please ensure the birth date is at least 18 years old. | Not normally. Twilio’s GB and AU guideline pages do not list a date-of-birth field. | If you see it, check the birth date entered on the End-User. The reason belongs mainly to other countries’ bundles. |
| 13 | Required information is missing. The Birth Date, Birth Place, Tax Code, Document Type, Number, and Issue Date are required. | Not normally. Birth date, birth place, tax code, document type and issue date do not appear on Twilio’s GB or AU guideline pages. The only overlap is the AU local-number form for individuals, which asks for the ID document number. | Usually a sign the bundle was created against another country’s regulation. Check the country and number type you picked. |
| 14 | The name on the Supporting Document does not match the information entered on the Identity. Please ensure the names match exactly. | Both markets: the representative’s or individual’s name. | Enter all names exactly as on the ID. Twilio’s own example: “Nick” in the bundle against “Nicholas” on the document is rejected. |
| 15 | The nationality of the government office that issued the document does not match the information on the Proof of Identity. Please ensure the document and the information you provided match. | AU local numbers for individuals, where Twilio’s guideline says proof of identity “Must be issued in Australia”. | Use an Australian government-issued ID or an Australian passport. |
| 16 | Please provide a Supporting Document that shows a local address. | UK local and national numbers need a valid UK address. AU local numbers need an address in Australia. | Upload an address document for an address in that country. If you have none in the UK, see the mobile or toll-free route in the UK section above. |
| 17 | Please amend the data entered in the Address fields to match exactly the address in the documents you have provided and ensure it is entered appropriately and in the correct sections. | Both markets: the address fields. | Copy the address from the document into the correct fields. If you saved the wrong address country, Twilio says to remove the document and upload it again. |
| 18 | A partial address is not accepted. Please provide a complete physical address. | Both markets. | Give a complete street address: number, street, locality, postcode. |
| 19 | The Proof of Identity does not show a visible address. Please upload a Supporting Document that shows an address. | An ID used as proof of address that does not show one. | Add a separate proof of address: a utility bill, tax notice, rent receipt or title deed. |
| 20 | A PO Box is not acceptable where a local address is required. Please provide a full physical address. | AU local numbers, AU mobile numbers for individuals, and AU toll-free business bundles (the guideline says “a PO Box is not acceptable”). | Use a street address. Twilio also rules out virtual offices. |
| 21 | The End-User’s valid, government-issued photo identification with an address is missing. Please upload the End-User’s government-issued photo identification with an address. | Individual bundles. | Upload a photo ID that shows the address, or add a separate proof of address. |
Twilio’s rejection article adds a rule that changes how you fix things. “We cannot approve a bundle unless all the documents within are approved.” If a document was rejected for what it is, remove it before uploading a replacement. If it was rejected only because of how you typed its details into the bundle, keep the document and fix the fields.
What makes bundle approval slip
Every item below comes from Twilio’s own articles. Each one either causes a rejection or hides a result you already have.
- The result goes to an inbox nobody reads. Twilio sends the status email “only” to the address in the bundle’s Notifications section “at the time the bundle was created”. Everyone else has to check Console. A bundle approved on day 2 and noticed on day 6 has cost you four days.
- Nothing happens between submission and result. Twilio’s Bundles API sends a status callback on every status change except the move from
pending-reviewtoin-review. After the callback for submission, the next one is the result. Silence during the window is normal, so don’t open a support ticket on day 1. - A document that is too old. Address documents: 3 months for individuals, 1 year for businesses. Twilio also says that if a business document “has been issued longer than 1 year ago”, its team checks public databases and rejects the document if the details don’t match.
- Merged or partial documents. One document category holds one document. Twilio says it “cannot accept multiple pieces of documentation merged together”, the exception being the two sides of an ID card. It also doesn’t accept application forms, and accepts rental contracts only if all signatures are visible.
- Configuration errors you could have caught first. Twilio’s Evaluations API says a bundle “can be evaluated” at “any point” in its lifecycle. It returns
compliantornoncompliantwith failure reasons. That checks the bundle’s setup against the regulation. It does not mean a reviewer has accepted a scanned utility bill. Run it before you submit anyway: it catches missing items instantly, where Twilio’s review takes days. - A bundle you can’t clear out. Twilio says bundles in draft, approved or rejected status can be deleted via API only (no longer from Console), and only with no phone numbers assigned. Plan the clean-up and don’t leave duplicate drafts lying around.
What to start on day one, and what can run alongside
Submit the bundle on the day the build starts, not the day it finishes. Nothing in the agent build depends on the bundle, and in the worst case in our table the bundle takes 19 business days. Script design, voice choice, CRM hooks and call testing can all run on a test number while the bundle is in-review. Our pre-go-live testing checklist for AI voice agents is laid out so it fits inside that window.
Your day-one list:
- Choose the number type. For a non-UK company in the UK, that means mobile or toll-free.
- For Australia, get the long form ASIC extract and check whether the representative is named on it.
- Get an LOA signed now if they aren’t.
- Use a real mobile number and a monitored business email for the representative.
- Set the bundle’s notification email to a shared inbox.
- Run an Evaluation before you submit.
One question to settle before signing with any agent platform, Zian AI included: whose telephony account will the bundle sit in? Twilio’s UK FAQ says each number should be assigned to a bundle “that represents the owner of the phone number according to the business name”. Both of Twilio’s guideline pages also ask whether an ISV (independent software vendor) will assign numbers to end customers. If the platform provisions numbers under its own account, ask which business the bundle will name and who receives the rejection emails. If you bring your own Twilio account, the bundle, the notification inbox and the resubmissions are all yours. Comparing platforms on this point is part of our comparison of AI voice agents for outbound calls. Zian AI is currently in partnership-application beta. If you want to talk through your UK or Australian rollout with us, Apply For Partnership.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| “up to two business days” review; “up to 3 business days, plus any processing time for mailer delivery confirmation”; result email from [email protected] | Twilio (article updated 14 May 2026) | help.twilio.com/articles/8338625205147 | 24 Sep 2026 |
| Australian review “up to five business days”; ABN/ACN, long form extract, non-PO-Box local address, LOA rule; “Final guidelines from regulators have not yet been issued” | Twilio (article updated 3 June 2026) | help.twilio.com/articles/49291010297883 | 24 Sep 2026 |
| UK dates 27 May 2024, 30 September 2024, January 2025; no fees for UK long codes; non-UK businesses use mobile or toll-free | Twilio (article updated 22 May 2026) | help.twilio.com/articles/21038555454875 | 24 Sep 2026 |
| 21 listed rejection reasons; Australia-specific ABN/ACN reason; 3-month (individual) and 1-year (business) address document rules; “recently dated” LOA | Twilio (article updated 5 June 2026) | help.twilio.com/articles/16066152436507 | 24 Sep 2026 |
| Deletion via API only, for draft, approved or rejected bundles with no numbers assigned | Twilio (article updated 22 May 2026) | help.twilio.com/articles/9556985762459 | 24 Sep 2026 |
| UK: “No documentation required” for business fields; representative phone cannot be a CPaaS number; address rules by number type | Twilio (page undated) | twilio.com/en-us/guidelines/gb/regulatory | 24 Sep 2026 |
| AU: email domain and alias rules; charging-district and porting note; updates apply to porting | Twilio (page undated) | twilio.com/en-us/guidelines/au/regulatory | 24 Sep 2026 |
| Six bundle status values (one, provisionally-approved, not described); no callback for pending-review to in-review | Twilio (API reference, undated) | twilio.com/docs/…/api/bundles | 24 Sep 2026 |
| Evaluation at “any point” in the lifecycle; compliant / noncompliant | Twilio (API reference, undated) | twilio.com/docs/…/api/evaluations | 24 Sep 2026 |
| UK “approximately 72 hours” after documentation is received | Telnyx (page undated) | support.telnyx.com/…/1311457 | 24 Sep 2026 |
| Australia “approximately 72 hours” after documentation is received | Telnyx (page undated) | support.telnyx.com/…/3505912 | 24 Sep 2026 |
| “Processing of the compliance documents may take up to several business days” (bundles lodged for a port) | Twilio (UK article updated 25 May 2026; AU article updated 10 July 2026) | help.twilio.com/articles/226194807; help.twilio.com/articles/226287108 | 24 Sep 2026 |
| 2, 3, 5, 7, 11 and 19 business-day totals (the Rejection Multiplier) | Zian AI’s arithmetic from the Twilio windows above, assuming each resubmission takes a full window (Twilio publishes no separate figure) | This page | 24 Sep 2026 |
Frequently asked questions
How long does Twilio regulatory bundle approval take?
Twilio gives three different windows in its own help centre. Its bundle submission article says the review “will take up to two business days”, and further down the same article says “up to 3 business days, plus any processing time for mailer delivery confirmation” (Twilio, updated 14 May 2026). Its Australian KYC article says “The review can take up to five business days” (Twilio, updated 3 June 2026). Plan on 3 business days for a UK bundle and 5 for an Australian one. Twilio publishes no separate window for a resubmitted bundle, so plan on a full window again for every rejection.
Can I get a UK phone number if my business is not registered in the UK?
Yes, but not a UK local or national number. Twilio’s UK KYC article answers this directly: “You should use UK mobile or UK toll-free phone numbers.” Its GB guideline page backs this up. Local and national numbers need a valid UK address, while the business address for mobile and toll-free numbers “May be anywhere in the world”.
Do I need a Letter of Authorization for an Australian Twilio bundle?
Only if the person named as the authorised representative is not on your ASIC extract. Twilio says that if the representative is listed on the extract as a director or officer, “no LOA is required”. If they are not listed, a director named on the extract has to sign the LOA. Twilio’s rejection list also says the LOA must be “signed and recently dated”.
Does resubmitting a rejected bundle restart the review clock?
Twilio does not say. None of the Twilio help articles cited on this page gives a separate window for a resubmitted bundle. Treat each resubmission as a new review of the same length. On an Australian bundle, one rejection then turns 5 business days into 10, plus the time you spend on the fix.
Can I delete a Twilio regulatory bundle?
Yes, through the API, and only when no phone numbers are assigned to it. Twilio’s How to Delete a Regulatory Bundle article says bundles in draft, approved or rejected status can be deleted via API but not from Console. You have to release the numbers or move them to another approved bundle first.
Are there fees to register a UK long code with Twilio?
No. Twilio’s UK KYC article says “there are no fees to register UK long codes”. You still pay the normal number and usage charges, which that article does not cover.
Is Telnyx faster than Twilio for UK and Australian numbers?
You can’t tell from the published figures, because the units differ. Telnyx’s UK and Australian requirement pages say it takes “approximately 72 hours to validate the information and activate the number” once documents are received. Twilio publishes business-day windows for its review. Compare the two only after converting to your own calendar, including weekends.