Your Workspace's Email Is Now Sent From Your Region

On October 23 we wrote that sign-in, your team and the routing behind your numbers had moved into your region. Email was on the list of what still ran in the United States. As of November 2, it is not: your workspace's email is sent from the same region as your contacts and call records.

What moved since October 23

• Account, verification and service email. The messages we send about your account and the service you use.
• Booking confirmations. The ones your scheduling page sends.
• Live call updates in Asia-Pacific. Since October 25, the events that update your dashboard and inbox during and after a call pass through Singapore instead of the United States. A call answered in the United States, such as one on a number on your own carrier account, has its event written there first, then carried to Singapore and stored.

Until November 2, Postmark sent this email from the United States for every workspace. It no longer sends any. It may still hold messages it sent earlier until we close the account, and the sub-processor register will announce that when it happens.

Why it matters

One answer to "where does it run?", email included. A password reset or a booking confirmation carries personal information: a name, an address and a message. It now leaves from the region where your contacts and call records are kept.

Nothing to set up. The switch happened on our side.

We say where our part ends. Once an email leaves us, where it goes depends on the recipient's own email provider. That part is not ours to promise.

What still runs outside your region

Without rounding up: payments and some phone and text-message services run in the United States, every visit reaches us through a global network edge first, and for workspaces outside Europe our monitoring tools are in the European Union. We keep a frozen earlier copy of the sign-in, account, team and number routing records in the United States so we can roll back.

Two kinds of email still come from the United States, because they are not a workspace's email: messages from our contact form on distronode.com and our own operations alerts.

One gap is about where you ask. A password reset, activation link or account notice asked for on distronode.com is handed to your region and sent from there for an account that existed before October 10, 2026. An account created in Canada, Europe or Asia-Pacific since then is not yet known to distronode.com, so ask for those on distronode.ca, europe.distronode.com or apac.distronode.com, where every step runs in your region.

The Canada, Europe and Asia-Pacific pages name each exception, and the data residency map lists every kind of data and where it is processed.

Also new: one Publish in District Studio

Until November 1, most pages in District Studio had their own Save, and each Save went live on its own. Change the greeting to mention a new service, then switch on the skill that books it, and for the minutes in between a call could get one change without the other.

Now your edits in Receptionist settings (Identity, Voice, Hearing, Thinking, Skills, Calls and Video) and in Business basics on the Knowledge page go into one draft, apart from the few settings listed further down. Your edits are saved to the draft as you make them, and a draft started on either page shows on both. Nothing in the draft reaches callers until you publish.

What you see:

• A status line. The Receptionist page and the settings dialog say "Everything here is live" or, for example, "2 changes not live yet".
• A test call with the draft. Pick "Test what is on screen" beside Test call to talk to your receptionist in your browser with the draft applied, before anything is live.
• Review and publish. One table with three columns, Setting, Live now and After publish, listing only what changes, in words. Under it: "Calls already in progress keep the current version."
• Publish. All the changes go live together. The status line says, for example, "Published 2 changes. Live from the next call."
• No surprises. If someone changed a setting live after you drafted it, the review says so and offers to update the draft before you publish. Discard draft removes the drafted changes without touching anything live, and you can put the draft back for 10 minutes.

A few settings still save on their own and are marked "Saves on its own": telling callers they are speaking with an AI receptionist, your own "Available for calls" switch, API connectors and the "Answer questions from" choice on the Knowledge page. The Call routing and Integrations pages also save as before.

Why one draft is better. Settings that belong together go live together, so a caller never meets half a change. You see the whole change before it ships, as it will be, not as a list of saves you have to remember. And a mistake costs nothing until you press Publish.

The one Publish is on for every workspace. Anyone whose role can edit the receptionist can publish; everyone else can read what is waiting to go live. Business basics on the Knowledge page stays the workspace owner's to change.