Your District AI Number Is Now Answered in Your Region

Your customers call your business line, and District AI answers. As of October 1, if your workspace is in Canada, Europe or Asia-Pacific and the number came from us, that call is answered on our own servers in your region: Montreal, Frankfurt or Singapore.

That now includes the US numbers we issue. Until this week, a US number we issued a Canadian or European workspace was answered in the United States. Not anymore.

Your contacts, call records and transcripts already live in your region. Now the calls that come in on your District AI numbers are answered there too, so a call and its record sit in the same place.

Picture a property manager in Vancouver with a local line for tenants, who wants a Seattle number for owners who live in Washington. Until this week, a Seattle number from us would have been answered in Virginia. Today it is answered in Montreal, just like the Vancouver line, by the same District AI, with the same contacts and call history behind it.

What's new

Canada. The Canadian numbers we issue have been answered in Montreal since September. Plenty of Canadian businesses also keep a US number for customers south of the border, and until now that line was the exception: its calls were answered in the United States. From October 1, a US number from us is answered in Montreal too, on the same equipment as your Canadian numbers.

Europe. A European workspace can take a local number today. Estonia needs no paperwork, and other EU countries open as their local registrations are approved. Calls on those numbers have been answered in Frankfurt since August. Now the US number you give your American customers is answered in Frankfurt as well, as long as it came from us.

Asia-Pacific. Since September 26, calls on the numbers we issue an Asia-Pacific workspace are answered in Singapore, and for a new workspace the AI that answers them runs in Singapore too.

The calls you place already started in your region, and they still do.

Why it matters

A short answer to a hard question. When a client, your privacy officer or a procurement questionnaire asks where your customer calls are handled, you now have a short answer for every number you get from us: in your region, next to your contacts and call records. If you work under Quebec's Law 25, PIPEDA or the GDPR, you will be asked that question, and now the answer fits in one line.

A US number without a US answer. You can serve American customers on a local US number while their calls are answered at home. One dashboard, one District AI, and the same receptionist on every line, whichever country your caller dials.

Proof, not promises. Our residency map is generated from the same registry that routes your live calls. When the routing changes, the map, our regional pages and our sub-processor change log change the same day. This time, that was October 1.

How we built it

Two carriers, one rule. Telnyx has a Canadian gateway, so a call to a Canadian number we issue through Telnyx goes straight to our equipment in Montreal.

Twilio has no network in Canada, so we built a direct route: Twilio hands each call to us at its hub in Ashburn, Virginia, and we answer it in Montreal. European calls on US numbers reach Frankfurt through Twilio's hub in Dublin, and Asia-Pacific calls reach Singapore through Twilio's hub there.

Before we changed a word on this site, we placed live calls on every new route and watched each one arrive where it should. Only then did the pages change.

Nothing to set up

Get a number from us in your dashboard and it is answered in your region from its first call. There is no switch to flip and no setting to find. District AI answers every number in your workspace, with the same contacts behind it. The numbers you already have keep working as they do today.

Want to keep an existing number? Forward it to a number from us, and its calls are answered wherever that number is answered. Your customers keep dialling the number they know, and you get the regional answer.

The fine print

We would rather tell you exactly where things run than round up:

• A Canadian call on a Twilio number passes through Twilio in the United States before it reaches Montreal.
• A call to a US number in Europe crosses US phone networks before it reaches Frankfurt.
• A number on your own carrier account is answered in the United States.
• Text messages run through our carriers' US systems, and texting on the US numbers we issue Canadian, European and Asia-Pacific workspaces is not set up yet.
• The AI that holds the conversation runs where its voice engine runs, and every engine is labelled with its region before you pick it.

Every detail, per region and per kind of data, is on our data residency map. Our regional pages, our signed data processing addendum and our sub-processor change log were all updated the same day.

See it for your region

Running a business in Canada, Europe or Asia-Pacific? See exactly what runs in Canada, Europe and Asia-Pacific, find out what District AI does, or compare plans.

Already with us? Add a number from your dashboard, and it is answered in your region from the first ring.