No Canadian statute says the words “you must disclose that this is an AI.” Several make it the only safe option anyway.
The honest answer is that the obligation is indirect, and that the indirect route arrives at the same place.
There is no Canadian law that says a business must announce an AI receptionist as an AI. What there is, is a consent standard that becomes very hard to satisfy if you do not. PIPEDA requires meaningful consent for collecting personal information, and consent is only meaningful if the person understands what they are consenting to. A caller who believes they are speaking to an employee, and is instead speaking to a system that records, transcribes and stores what they say, has not been given what they needed to decide.
Is there a Canadian rule requiring AI disclosure on calls?
Not a specific one. No federal or provincial statute currently states that a business must tell a caller it is using an automated voice system. Anyone claiming otherwise should be asked to name the section, because pages asserting this rule generally cannot.
That is worth stating plainly, because the alternative, repeating a legal requirement that does not exist, is how a lot of compliance content in this category gets written. It sounds responsible and it is wrong, and a business that later discovers the rule was imagined trusts nothing else on the page.
The proposed federal Artificial Intelligence and Data Act, which would have introduced obligations of this kind, died when Parliament was prorogued in January 2025. Quebec's Law 25 requires notification when a decision is made exclusively by automated processing, which is a narrower situation than answering a phone. Neither produces a general duty to announce an AI on a call.
Why does the consent standard get you there anyway?
Because consent has to be meaningful, and meaning depends on what the person understood. PIPEDA requires an organization to make its purposes clear enough that a reasonable person would understand what is being collected and why. A caller who has been left to assume they are speaking to a person has not been given that.
Put the recording guidance beside it and the position gets clearer still. The Privacy Commissioner already requires that a caller be told a call is being recorded, and told the purpose. An AI receptionist necessarily records and transcribes in order to work at all. So the disclosure obligation arrives through the recording door even if it never arrives through an AI-specific one.
There is a second reason that has nothing to do with law. A caller who works out mid-call that they have been talking to a machine, and were not told, does not conclude that the technology is impressive. They conclude that the business was willing to mislead them about something small, and they extrapolate.
What does a good disclosure actually sound like?
Short, at the top, and stated as a capability rather than an apology. The line has to name what it is and what it is doing with the call, in one sentence, before the caller has said anything worth recording.
The disclosure is also load-bearing for the rest of the call. A caller who knows they are talking to a system asks shorter, more direct questions, and the call goes better. Ambiguity produces the worst version of both: a caller talking to a machine as though it were a person, and getting frustrated when it behaves like a machine.
- Name it early. The first thing after the greeting, not after the caller has explained their problem.
- Say what happens to the call (recorded, transcribed, passed to the team) in the same breath as what it is.
- Do not perform humanity. A system that says "I'm doing great, thanks for asking!" has told the caller something false before it tells them anything true.
- Give an exit. A caller who wants a person should be able to get one without arguing about it.
No Canadian statute requires you to announce an AI on the phone, but PIPEDA requires consent to be meaningful, and a caller who thinks they are talking to your receptionist has not meaningfully consented to anything.
Every line we build says what it is in the first sentence. It has never once cost a booking, and it removes the only version of this that ends badly.
Start free pilotWhat this page does not settle
This is a reading of the legislation as it applies to an AI receptionist answering a business phone, not legal advice. Statutes are amended and regulators publish new guidance; check the source links, which are dated, and take advice on anything that matters.
- Where the law is going. AI disclosure rules are actively under discussion in several jurisdictions. This page describes the position as of its date, and that position is more likely to change than most things on this site.
- Sector-specific rules. Regulated professions may impose their own communication standards that go further than privacy law does.
- Outbound calling. This page is about answering a call. Placing one brings CRTC telemarketing rules into scope, which are a separate regime.
Questions this raises
- Is it illegal to use an AI receptionist without telling callers?
- No Canadian statute makes it an offence by name. The exposure is under privacy law rather than a specific AI rule: consent must be meaningful, and an AI receptionist records and transcribes calls, which already triggers a disclosure obligation under the Privacy Commissioner's recording guidance.
- Does the caller have to say yes, or is continuing enough?
- For call recording, the Commissioner treats continuing the call after being told as implied consent. The requirement is that the caller was genuinely told, at the start, in terms they could understand.
- Should the AI say it is an AI, or just that the call is recorded?
- Both, and in that order. The recording notice is the part with clear regulatory footing. Naming what the caller is speaking to is what makes the consent meaningful rather than technically obtained.
- Does disclosure make callers hang up?
- Not in our experience, and the businesses on this site disclose on every call. What loses callers is a system that pretends to be a person and then fails to behave like one.
- What about a caller who insists on a human?
- They should get one. An escalation path to a real person is worth building for its own sake, and it also removes the strongest objection anyone can make to the receptionist existing.
Sources
- Recording of Customer Telephone Calls: guidance for organizationsOffice of the Privacy Commissioner of Canadaupdated 2018-04-18, consulted 2026-08-09
- PIPEDA fair information principlesOffice of the Privacy Commissioner of Canadaconsulted 2026-08-09
Want an AI receptionist built around these rules rather than despite them?
We build a working receptionist on your calls, your booking rules and your escalation rules, and you call it yourself before committing to anything. About 14 days, no call limit during the pilot.
Start free pilot
