Product
AI receptionist for small business: what it handles, what stays human
Aug 12, 2026 · 9 min read
Updated Aug 17, 2026
An AI receptionist is a digital front desk that reads every inbound request, answers the routine questions from your own material, qualifies what came in and logs the run. At Unistaff.ai it works over text channels, a person sends every reply, and one AI employee costs $149 a month on the Starter plan.
Phone answering sits outside that today. Unistaff ships no telephony connector, no SMS provider and no calendar connector, so the front desk that runs at 3 a.m. is the text one: a form submission at 3 a.m. is read, drafted and queued at 3 a.m., ready for whoever opens the inbox. The section on calls below gives the full position.
The four things it does on every request
Reception work breaks into four moves, and the role runs all four in one pass. Each move is a step in code with a validator behind it, which is why the same request handled on a Tuesday and on a Sunday comes back with the same shape.
- Intake. A web form or quiz posts to the lead endpoint and the request lands in Postgres before anything else runs. The body is capped at 10 KB, a hidden field absorbs bots with a response identical to a real submission, and a submission carrying no contact channel comes back with the reason.
- Answer. The role writes the first reply from your brief, service list and house rules — two to four sentences, 100 to 500 characters, ready to send as it stands. A price can only appear marked as pending your approval, because an invented number in a first reply is the expensive kind of mistake.
- Qualify. The form answers travel with the request as structured fields, so the reply is written against what the person actually asked for. Contact details stay out of the prompt: the role works from an initial and the form answers, never the full name, the phone number or the email.
- Journal. Every run is written with its inputs, its outcome and its error text. A run that failed stays visible as a run that failed, so the week's numbers are a query rather than a memory.
The loop runs on a timer — every fifteen minutes in the reference deployment — and each pass picks up at most five requests that have no draft yet. A burst of enquiries on a Friday night is worked through in batches, and the drafts are waiting before anyone opens the inbox on Saturday.
What the AI takes on, what stays with a person
The split below is the deployment shape as the platform ships today. Read the right-hand column as the job that remains, and staff for that job rather than for the whole desk.
| Task | AI employee | Person |
|---|---|---|
| First reply to a new enquiry | Drafts it on the next run, 2–4 sentences, in your tone | Reads it and sends it |
| Repeat questions — hours, services, location, what to bring | Answers from the brief, service list and knowledge items | Keeps that material current |
| Qualification | Carries the form answers into the reply as structured fields | Decides which enquiries get priority |
| Prices in a first reply | Marks any number as pending owner approval | Confirms the number before it goes out |
| Booking | Prepares the request with the details the booking needs | Puts it in the calendar — no calendar connector ships today |
| Anything outside the material | Stops and says why it stopped | Takes the conversation |
| Record keeping | Journals every run with its outcome, failures included | Reviews the journal weekly and corrects the brief |
Phone calls, honestly
Most pages selling an AI receptionist put a phone number in the hero. Ours would be a claim we cannot back, so here is the state of it. Text intake runs today: a form posts to the endpoint, the lead is stored, and one email notification goes out with a five-second timeout — the lead reaches the database first, so a mail failure costs a log line while the enquiry stays.
Voice is custom scope. The published plans are Starter at $149 a month, Scale at $599, and Enterprise at custom pricing; custom roles and custom workflows appear on the Enterprise column of the price table only. A voice front desk starts as a scoping conversation about telephony, recording consent and who answers when the AI stops, and the build follows that conversation. Call tracking sits on the integrations roadmap, which is why phone calls stay outside attribution rather than being estimated.
For a small business the practical read is this. If most of your enquiries already arrive in writing, a text-first receptionist covers the volume. If your desk lives on the phone, the first honest step is moving the repeat questions to a text channel and measuring what is left.
The cost against a front-desk hire
The ROI calculator on this site ships a Healthcare front desk role, and the calculator's own defaults answer the cost question without any new arithmetic. One front-desk role, 40 hours a week, $35 an hour, 70% of those hours handed to the AI.
| Input | Value |
|---|---|
| Baseline front-desk hours | 40 per week |
| Hourly rate | $35 |
| Share of hours handed to the AI | 70% |
| Hours handed off | 28 per week |
| Cost of those hours, per month | $4,243 |
| AI employee, per month | $149 — Starter plan |
Read that as a comparison of hours. The 30% left over is the part of the desk that carries judgement — the upset customer, the exception, the call that needs a decision — and it still needs a person. What changes is that the person spends the shift on those thirty per cent instead of retyping opening hours.
“A request that arrives at 11 p.m. is read at 11 p.m. The reply waits for a person, with the work already done.”
Setting one up
Setup is a writing job more than a technical one. The role reads your material on every run, so the quality of the brief sets the quality of the drafts.
- Write down the ten questions your desk answers every week, with the answer you already give. That list is the first version of the knowledge the role reads.
- Set the house rules: what the role may state as fact, what it must mark as pending your approval, and where it stops and hands over.
- Point your web form at the lead endpoint so every enquiry lands in one place with its answers attached.
- Run week one in shadow: read every draft before it goes, count how many went out unedited, and fix the brief where they did not.
By the end of that week you have a number instead of an impression — the share of enquiries the AI answered well enough to send as written. That number decides how much of the desk you hand over next.
Questions people ask before they buy
On Unistaff, no. Text channels run today — a web form or quiz posts to the lead endpoint, the request is stored, and the first reply is drafted on the next run. A voice front desk is custom scope on an Enterprise plan and starts with a scoping conversation about telephony and consent. Call tracking is on the integrations roadmap.
One AI employee is $149 a month on the Starter plan, which includes a 14-day pilot and cancellation at any time. Up to five AI employees with custom briefs and priority support is $599 a month on Scale. Enterprise is custom-priced and carries custom roles, workflows and SLA-backed support.
The draft is written ahead of time, so it is waiting rather than being composed while the enquiry cools. The design target is a first touch inside five minutes for hot enquiries and thirty minutes for standard ones. Sending stays with a person, so your actual response time is the draft plus whoever is on shift.
Today a person reads and sends every reply, so what reaches the customer is your team writing with a head start. When a role starts replying directly, the disclosure goes into the reply template and we set that up with you before it goes live.
It prepares the booking with the details the booking needs, and a person puts it in the calendar. Unistaff ships no calendar connector today, so a deployment that depends on live availability starts by scoping that connection rather than assuming it.
The full name, phone number and email address never enter the prompt. The role works from an initial and the answers on the form, and the contact record stays in the database where the reply is sent from. Every run is journaled with its inputs and outcome.
An afternoon of writing for the brief, the service list and the house rules, then a shadow week to measure how often the draft is right. There is no code to write: a role is picked from the registry and briefed in plain language.