The United States and Canada, and what actually changes between them when an AI voice agent answers your phone.
Two markets, two different conversations. AI voice agents for US businesses run under one federal statute and a patchwork of state disclosure and recording law, while AI receptionists for Canadian businesses answer to the CRTC on the call and to whichever privacy act covers the province on the data. Agencies selling into either market license the white label AI voice agent platform and put their own brand on it; buyers who cannot let call audio leave their environment take the on-premise AI voice agent license and run the stack themselves.
Licensing by territory
The licence terms are the same wherever you are. What changes by territory is who carries the regulatory obligation when your client’s agent dials, and where the call data is allowed to sit.
The Canadian go-to-market layer: regulatory responsibility between you and your client, and the hosting question that decides deals.
The reseller liability chain under the TCPA, and the consent rule most competitors still describe as if it existed.
Deployment inside your own Canadian environment, and an honest account of when residency is required rather than merely preferred.
The sub-processor chain argument, the oversight duty financial institutions carry, and why state AI guidance keeps going stale.
How a deployment runs
What changes by location is the numbering, the consent script and the hosting region. The engagement itself does not.
01
We map how your calls arrive today, which of them you are losing, and what a good outcome looks like — including which jurisdictions you take calls in.
02
The script, the voice and the escalation rules are written around your call flows, then wired to your CRM, calendar and phone numbers.
03
You hear the agent handle your real call types before a customer does, and the consent, disclosure and recording language goes past your counsel.
04
Numbers are ported or provisioned, the agent goes live, and the transcripts drive the next round of changes.
Worth being clear about
Centricall is a remote company with one published address, in Cumming, Georgia. These pages describe territories we take calls in. None of them claims a local office, and none of them carries local-business markup saying otherwise.
A page exists here only where the rules, the numbering or the industry mix genuinely change. Somewhere with nothing of its own to say would just be this page with the place name swapped, so it does not get one. Pages are published as they are written rather than generated in a batch.
Every regulatory statement names the instrument it comes from and links the primary source with the date we read it. Rules in this area move — one widely-cited FCC rule was struck down before it took effect — so the date matters as much as the claim.
FAQ
The ones that come up before anyone looks at a specific territory.
No, and no page here says otherwise. Centricall is a remote company with a single published address in Cumming, Georgia. What is genuinely local is the phone numbers we provision, the calling rules the agent follows, and — on a self-hosted deployment — the region your call data sits in. Delivery is remote from discovery through to go-live.
Yes, and a lot of deployments do. The thing worth planning for is that the two countries do not share a rulebook: an outbound campaign that is fine in Ohio has a different calling window and a different consent record in Ontario. Cross-border deployments are scoped with per-territory settings rather than one global configuration, which is most of what the country pages are about.
On the hosted plans that depends on the hosting region, and it is settled during scoping rather than assumed. If your requirement is that recordings and transcripts never leave a particular country, that is what the on-premise licence is for: the platform runs inside your own cloud account or your own hardware, and nothing leaves it.
If you are buying to resell, or to run the platform inside your own environment, go straight to the licensing pages — each one carries the regulatory detail for its market. Country, state and province pages are published as they are written; each covers who is calling in that market and what its businesses actually need from a phone line, and they link back up rather than repeating the federal position.
The hosted plans speak English, Spanish, French, German, Hindi and Japanese, and the caller chooses by answering rather than by working through a menu first. Licensed and self-hosted deployments extend to more than twenty-five languages, so if you need something outside the six it is a scoping question rather than a no.
No. These pages state what published rules say, name the instrument, and link the source with the date we read it, because a vendor page that hand-waves at compliance is worse than useless during a security review. What goes into your consent script, your disclosure line and your retention policy should be signed off by your own counsel — regulators hold the business making the call responsible, not the platform underneath it.
Connect with our experts
Tell us which countries and states or provinces your calls come from, and we will map the numbering, the consent script and the hosting region before quoting anything.
Book a discovery call