Can a Small Business Legally Record Calls With an AI Receptionist in Canada?
Can a small business legally record calls with an AI receptionist in Canada? Yes — but "legal to record" and "recording it properly" are two different tests, and your business has to pass both. One is in the Criminal Code. The other is in Canada's privacy law, and it is the one owners trip over.
This is the question I get most often from owners who are otherwise ready to try an AI receptionist. They are not worried about the technology. They are worried about the sentence at the start of the call — what it has to say, who has to hear it, and what happens to the recording afterwards. Fair questions. Here are the answers, in plain language. I run NexAIS (https://www.nexais.ca/) in Richmond Hill, and this is the same checklist we work through when AVA, our AI receptionist, goes onto a business's phone line.
One warning before we start: this is general information from public sources, not legal advice. If you work in health care, law, or finance, or you take calls from Quebec, get thirty minutes with a privacy lawyer before you switch anything on. Everyone else: read on.
Test one: the Criminal Code says one person on the call is enough
Canada's Criminal Code, section 184, makes it an offence to record a private conversation you are not part of. Section 184(2)(a) then carves out the exception everyone calls one-party consent: if you are one of the people on the call, you may record it.
That is the criminal-law layer, and for a business answering its own phone, it is rarely the hard part. Your receptionist — human or AI — is a party to the conversation. The trap is assuming this is the only rule. It is not. A business can pass the Criminal Code test and still get the privacy side wrong, because privacy law asks a different question: not "could you record that?" but "did the caller know, did they agree, and what did you do with the recording?"
Test two: PIPEDA is where the real duties sit
For most Ontario businesses, PIPEDA — the federal private-sector privacy law — is what governs customer calls. The Office of the Privacy Commissioner of Canada (OPC) publishes a plain guide on recording customer telephone calls, and its rules are specific:
- Tell the caller before the recording starts, and say why. Not buried in a privacy policy on your website. At the start of the call.
- State the purpose narrowly and honestly. If the recording is for booking accuracy and staff training, say that. The OPC is blunt about this: do not say "quality assurance" if the recordings will actually be used for marketing, profiling customers, or checking who someone is.
- Get consent. In most ordinary cases, if the caller hears the notice, understands why, and carries on with the call, consent is implied. That is the OPC's own wording.
- Offer another way if the caller objects. Someone who does not want to be recorded should still be able to reach you — by email, through your website, or in person. A caller with no alternative has not really been given a choice.
- Keep recordings only as long as you need them, guard them, and let the customer see theirs. Callers can ask for access to their own recording later. A recording you keep forever, on a laptop anyone can open, is a problem waiting for a date.
None of this is hard. All of it has to be set up on purpose, which is where AI receptionists change the picture — mostly for the better, with one new wrinkle.
What changes when the receptionist is AI
A human receptionist forgets the disclosure when the phones get busy. An AI receptionist says it the same way, at the start of every call, at 3 p.m. and at 3 a.m. That consistency is worth a lot. But three things need your attention:
1. Say it is AI, in the same breath as the recording notice. Callers deserve to know who — or what — they are talking to before they start sharing details. One short opening line does both jobs:
"Hi, you've reached [business name]. I'm the virtual receptionist, and this call is recorded so we can get your booking right and train our team. If you'd rather not be recorded, just say so and we'll help you another way."
Then let the conversation start. Disclosure after the caller has already explained their problem is not disclosure.
2. Voiceprints are a separate, stricter category — and the rules tightened this month. On October 8, the OPC updated its call-recording guidance to deal with voiceprints: using the sound of a customer's voice to recognise them on later calls. The Commissioner's position is that a vague line like "this call may be recorded for identification purposes" is generally not enough, because it does not tell the caller that biometric information is being collected, what it will be used for, or who gets it. Where voiceprints or other sensitive information are involved, express consent — an actual yes, not silence — may be required.
This matters to us directly, because AVA is built to recognise returning callers and keep their call and text history, so a regular is greeted as a regular instead of starting from zero. Recognition done from a customer's booking history is one thing. Recognition done from the biometric pattern of their voice is another, and it needs the clearer conversation with the caller first. If a vendor offers you "voice ID" as a standard feature and cannot explain the consent step, that is a vendor problem, not a detail.
3. Decide who can listen, before anyone needs to. A recording holds names, phone numbers, addresses, sometimes health or payment details. In our own builds, access control is not optional: recordings sit behind named accounts with roles, so the person who books appointments is not automatically the person who can download every call the business has ever taken. If your team shares one login to a call dashboard, fix that first — a small tool like [AFFILIATE: 1Password Business — owner inserts tagged link] costs less than one leaked customer list. And set a deletion date. Thirty to ninety days covers most booking disputes and training needs for a small business; a legal or payment dispute is the only good reason to keep a specific call longer.
Your callers are not all in Ontario
Our own callers are not. AVA answers calls from the United States as well — memorably, one gentleman from the US who asked the receptionist to make him a sandwich. (She took his details politely. The sandwich, sadly, was beyond her.)
Behind the joke is a real compliance point. Several US states — California, Florida, Illinois, Pennsylvania and Washington among them — require every party on a call to consent to recording. Quebec's privacy law, Law 25, is stricter than PIPEDA in its own ways. You cannot ask a caller where they are calling from before you have said anything. The practical answer for a small business is the boring one: use the same clear disclosure, at the start of every call, for every caller. Meet the strictest standard by default and you stop having to think about borders mid-conversation.
The five-minute setup checklist
Before any AI receptionist goes live on your line, confirm these six things in writing with your provider:
1. The greeting names the AI and the recording before anything else is said.
2. The stated purpose matches the real use — bookings, training, dispute records — with no marketing use hiding behind "quality."
3. A caller who objects gets a real alternative, and the AI knows how to offer it.
4. Recordings are stored with named, role-based access. No shared passwords.
5. A retention period is set, and old recordings delete automatically.
6. You can pull up, hand over, or delete one caller's recording on request.
If a provider cannot answer those six, the low monthly price is not the bargain it looks like.
What doing this properly costs
Good consent practice is not a paid upgrade. It is a greeting, a setting, and a habit. AVA's plans are flat for the same reason: Starter at $197 a month (https://crm.nexais.ca/pricing/ai-receptionist) covers the receptionist itself, Professional at $399 adds the CRM and app where call records, bookings and customer history live in one place, and Grow at $599 adds website and Instagram management on top. No per-minute meter, so the longest, most complicated call of your month does not cost more than the shortest.
The honest way to judge any of this is on your own phone line, with your own callers. That is why we run a free 7-day pilot, and why the demo line, +1 (437) 529-0400, answers day and night — call it and listen to how the opening seconds sound. That opening is the whole article in miniature: who you are talking to, what is being recorded, and why.
A missed call can be a missed customer. A badly handled recording can be a missed customer plus a privacy complaint. The fix for both is the same habit: pick up, say plainly what is happening, and write it down properly. Questions about setting this up on your line? Our contact page (https://www.nexais.ca/contact) reaches a real person on our team.
Disclosure: Some links in this article are affiliate links. If you buy through them, we may earn a commission at no extra cost to you. We only recommend tools we genuinely believe help small businesses.
Sources
- Office of the Privacy Commissioner of Canada, "Recording of Customer Telephone Calls" (PIPEDA guidance, including the October 2026 voiceprint update) — https://www.priv.gc.ca/en/privacy-topics/surveillance/02_05_d_14/
- RecordingLaw, "OPC Updates Canada Call Recording Guidance on Voiceprint Consent" (October 9, 2026) — https://www.recordinglaw.com/news/opc-canada-call-recording-voiceprint-guidance/
- RecordingLaw, "Canada Recording Laws: One-Party Consent Rules" (Criminal Code s.184 summary) — https://www.recordinglaw.com/world-laws/world-recording-laws/canada-recording-laws/
- Vendasta, "AI Receptionist for Small Business: 2026 Guide" (recording disclosure practice for AI receptionists) — https://www.vendasta.com/blog/ai-receptionist-for-small-business/


Comments