AI receptionist for contractors: what it costs and what it should never do
The interesting question is not whether it can answer the phone. It is what happens to the call afterwards, and what the thing is not allowed to decide on its own.
By Eugene Romanov·Published
The short answer
An AI receptionist costs a fraction of a human answering service and does a narrower job. Rosie publishes plans at $49 a month for 250 minutes, $149 for 1,000 and $299 for 2,000, read from its own pricing page on 2 September 2026. Ruby, whose receptionists are people, publishes $250 a month for 50 minutes, $395 for 100 and $720 for 200. Both are real prices for different work. What either one must never do is pretend to be human, book a job, take money, or quote a number that is not already on the estimate.
SHT-02What drives the number
What the two things actually cost
Read off the vendors' own pages on 2 September 2026, and they change. Rosie, an AI answering service, publishes $49 a month for 250 minutes, $149 for 1,000 minutes and $299 for 2,000. Ruby, whose receptionists are people, publishes $250 a month for 50 minutes, $395 for 100, $720 for 200 and $1,725 for 500. The ratio is the story: roughly the same monthly spend buys around twenty times the minutes when a machine is answering. Whether that is a good trade depends entirely on what the calls are.
The arithmetic that decides it, on your numbers and not mine
Count the calls you missed last month, including evenings and Saturdays. Multiply by your average ticket, then by the share of enquiries that actually become jobs for you. That is what the missed calls cost. If the answer is smaller than a subscription, do nothing and spend the money elsewhere. If it is comparable, buy the cheapest thing that answers. If it is several times larger, the question stops being which service to buy and becomes where the call ends up, which is a different question with a different answer.
Five things it must never be allowed to do
Pretend to be a person: besides being dishonest, it breaks the conversation at exactly the moment the caller asks something the agent should not answer, and the handoff then reads as a malfunction rather than as the plan. Book a job: a wrongly booked slot costs a crew a morning, and nobody wants to explain that the software did it. Take money. Quote a number that is not already on the estimate, because an invented price becomes a promise. And record without consent: several states are commonly listed as requiring every party to agree, California, Florida, Illinois, Pennsylvania and Washington among them, so the recording switch should stay off until someone turns it on deliberately and confirms the rule where they work.
What it should do instead
Answer within a ring or two, at nine at night and on a Saturday. Work out whether this is a real enquiry or a wrong number. Take the name, the number, the address and one sentence about the job. Then hand it to a person while the caller is still warm, and leave a record that outlives everyone's memory of the call. That is the whole job, and it is worth paying for.
Where the call lands is the real difference
A standalone service, whether staffed by people or by software, answers into its own product and sends a notification. The enquiry then lives somewhere other than where you work, and getting it into your pipeline is a person retyping it. An agent built inside your own system writes the call into the same database as the estimate, the schedule and the history, raises the caller's card before the phone is answered, and queues the follow-up itself. That is the version built here, and it only makes sense if the system exists: an agent answering into nothing is a toy, and it is not sold separately.
The percentage nobody should give you
Vendors advertise how many calls their agent handles without a human, usually somewhere in the nineties. There is no number on this page, because there is nothing here to defend one with. The honest way to find out is to point it at your own line for a week and count what happened. Any figure offered before that is marketing, including one offered by me.
The text-back that needs paperwork first
The common follow-on is a text message to the caller after a missed call. In the US that is business messaging, and it needs A2P 10DLC registration against the company's EIN before carriers will deliver it reliably. That registration has its own waiting period and it is not a developer task, so it should start before the rest of the build rather than after it.
SHT-03The options, side by side
What each route actually costs you.
| Option | Price | Timeline | The trade-off |
|---|---|---|---|
| Nothing | $0 | n/a | Evening and Saturday calls go to voicemail. The cost is missed calls times average ticket times your close rate, and it is usually larger than owners expect. |
| AI answering service | Rosie publishes $49 to $299 a month by plan, 2 September 2026 | Days | Cheap, quick to start, never tired, answers around the clock. Answers into its own product, so the enquiry lives outside the place you actually work. |
| Live human receptionists | Ruby publishes $250 to $1,725 a month by plan, 2 September 2026 | Days | Best at the unusual conversation: hears irritation, handles an unclear accent, asks the question that is not in the script. The result still arrives as a message somebody has to read in time. |
| An agent inside your own system | Part of a build from $2,000, plus minutes billed to your own provider accounts | 30-45 days | The call becomes a record on the board, with history and a queued follow-up. Requires the system to exist, and costs more to start. |
SHT-04General notes
The questions people actually ask.
- N01How much does an AI receptionist cost?
- Rosie publishes $49 a month for 250 minutes, $149 for 1,000 and $299 for 2,000, read from its pricing page on 2 September 2026. Prices and included minutes vary widely between vendors, so compare minutes and overage terms rather than the headline figure.
- N02Is a human answering service worth the difference?
- For a low volume of high-value, complicated calls, often yes. Ruby publishes $250 a month for 50 minutes against Rosie's $49 for 250, so the difference is buying judgement rather than minutes. If your calls are mostly straightforward, that is judgement you are not using.
- N03Will callers know it is not a person?
- Some will, and the agent should not pretend otherwise. Beyond the honesty of it, a caller who asks something the agent should not answer needs the handoff to look like a normal step rather than a breakdown.
- N04Can it book jobs into my calendar?
- It should not decide a booking on its own. The problem is not technical: a wrong booking costs a crew a morning, and nobody wants to explain that the software did it. Prepare the booking, notify a person, let the person confirm.
- N05Can the calls be recorded?
- It depends on the state. Several are commonly listed as requiring every party to consent, including California, Florida, Illinois, Pennsylvania and Washington, so the switch stays off until it is turned on deliberately. Confirm the rule where you work rather than relying on a web page, this one included.
- N06What percentage of calls will it handle alone?
- No number, because there is nothing here to defend one with. Point it at your own line for a week and count. Any figure quoted before that, including by a vendor, is marketing.