What your receptionist does

What an AI receptionist actually is

An AI receptionist is a service that answers your business phone for you, and answers the written messages you hand it as well. It does not recite a fixed script: it follows instructions you wrote once — your services, your service area, your hours, what you take on and what you turn down — and it speaks English or French depending on the person calling, for businesses across Canada, in a voice you choose among several voices and styles by listening to them.

It is not voicemail. An answering machine records a message and leaves the call-back to you; here the conversation happens. The caller asks a question, gets an answer drawn from your own information, gives a name, an address and the nature of the problem, and hangs up knowing what comes next. On your side, a written request arrives, not a blinking light.

It is not a per-minute human answering service either, where someone outside your business reads a card and tries to guess your trade. The information comes from what you declared, it is corrected in one sentence when it changes, and the corrected version serves every call the next morning.

And it is not a touch-tone phone menu. There is nothing to press and no list to sit through: the caller explains the situation in plain words, and recognising what it is about is the receptionist's job.

What happens to a request, from the first word to your phone

A call comes in. The receptionist introduces itself on behalf of your business and states the recording disclosure at the start, as Quebec's Law 25 requires, before it listens.

It then qualifies: what is the matter, at what address, since when, and does the situation match the urgency rule you set. Water still running is not a dripping tap; a tooth that kept someone awake is not a routine cleaning; a dog hit by a car is not a vaccine reminder. You write that difference once, and it is applied at three in the morning.

It acts inside what you authorised: capture the request, offer a time slot when your calendar is connected, transfer to someone on your team, or state a call-back within the delay you set. Outside those limits it captures and hands over rather than deciding for you.

It leaves a usable trace: a written summary on your phone, the transcript of the exchange, and a request filed with the fields that matter in your trade — the floor and door code for a plumber, the make and mileage for a garage, the species and weight for a veterinary clinic.

How all of this is organised

Zenvox is sold as eight industry bases at a fixed monthly price. Every base covers phone reception, qualification, the written request, one local number and 50 Standard calls included each month. There is no setup, activation or onboarding fee: that is not a launch discount, it is how the product is sold.

Around that base, extra capabilities are added one at a time, when they are of use to you. Nothing is switched on by default, nothing is preselected during signup, and removing one add-on leaves the others alone. Each add-on has a page of its own stating what it does, what it meters, and which decision it asks of you.

The six groups below are not technical modules: they are the six things owners ask us for. You rarely go looking for a feature; you go looking to fix something that has been slipping for months.

What runs without you, once you have decided it

An automation here is not an intelligence that starts doing things on its own. It is a follow-on you decided once: when this happens, if that condition holds, then this action runs. An estimate sits unanswered for five days? A follow-up goes out. A call does not connect? A text goes to the number that tried. A job finishes? A review request follows.

The difference from doing it by hand is not speed, it is consistency. Nobody forgets a follow-up on a busy Tuesday, and nobody follows up twice with the same person because two people on the team had the same idea.

There are two families, and the line between them is a decision, not a technical limit. What answers a person who already approached you — the missed-call text, the written summary, the acknowledgement of a request, the reminder before an appointment, the follow-up on an open file — runs on its own. What speaks in your name to the whole world — a social post, a reply to a public review, a page on your website, a campaign — is prepared automatically and waits for your approval. Between the two, consent decides: a follow-up stops at the first reply, at a refusal, or at an opt-out expressed on any channel of the same file.

Every rule carries a version and every run leaves a log: you see what went out, to whom, and why the condition held. A rule stopped mid-run does not leave half a job behind, a technical retry does not repeat the same effect twice, and an automation pauses: it is a switch, not a final decision.