> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Twilio regional routing

> Prepare region-specific Twilio credentials and edge choices while distinguishing accepted configuration from deployed routing.

Use regional configuration to record the intended Twilio region and edge for a deployment review. Saving these fields does not move a running service or establish where every system processes data.

Twilio Regions and Edge Locations serve different purposes. Region-specific credentials differ from the default region's credentials; an edge selects an entry or exit location. See [Twilio's regional usage documentation](https://www.twilio.com/docs/twilio-cli/general-usage/regional).

## Accepted configuration

The current Threetone `region_config` requires `region_id`, `token`, and `edge_location` when supplied.

| Field | Current request values |
| - | - |
| `region_id` | `us1`, `ie1`, `au1` |
| `edge_location` | `ashburn`, `dublin`, `frankfurt`, `sao-paulo`, `singapore`, `sydney`, `tokyo`, `umatilla`, `roaming` |
| `token` | Regional Auth Token for the intended account and region. |

These enums are an input contract. They do not certify every combination or automatically accept regions added by the provider.

## Review a regional route

<Steps>
  <Step title="Identify the region owner">Confirm the account, number, and intended regional resources with your Twilio administrator. Avoid combining a regional endpoint with credentials from another region.</Step>
  <Step title="Match the accepted fields">Compare the proposed values with [Import phone number](/api-reference/agents-platform/import-phone-number). Keep enable\_sms false and omit account\_auth\_token as required by the [Twilio import guide](/agents-platform/deploy/telephony/twilio/native-integration).</Step>
  <Step title="Review runtime delivery">Document how the future runtime will receive the regional credentials and choose its endpoints. Import redacts credential metadata; saving the regional token does not demonstrate usable secret delivery.</Step>
  <Step title="Plan regional acceptance checks">When the runtime is supported, verify the selected route in provider records and measure signaling and media separately. Keep a known fallback and document how it will be restored.</Step>
</Steps>

For an authentication failure, verify the account and regional credential pair before changing network routes. For latency, inspect the complete caller-to-runtime path rather than assuming the nearest edge resolves every delay.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I use any region supported by Twilio?" id="twilio-regional-faq-enum">Only the current schema's region values are accepted. Provider support can be broader than the Threetone request contract.</Accordion>
  <Accordion title="Does a saved region provide a data-residency guarantee?" id="twilio-regional-faq-residency">No. Review the actual provider, application, model, logging, and storage paths and the applicable agreements separately.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.