Ruby, Smith.ai, AnswerConnect. When human receptionists still win, when AI wins, and the hybrid that beats both in 7 of 10 setups.
Ruby, Smith.ai, AnswerConnect — the virtual receptionist services have been around since before AI was a hype cycle, and they still win meaningful percentage of bake-offs. Here is the honest framework for when each wins, and the hybrid that beats both in seven of ten deployments.
Most teams measure too many things and then measure nothing. The 30-day measurement plan is short:
Five metrics, one dashboard, one Monday review. If the metric is not on the dashboard, it does not exist for the first 30 days.
After 30 days you can add CSAT, conversion-to-revenue, and channel attribution. Adding them earlier just adds noise.
Every architecture choice in this category is a tradeoff. Here are the ones we have made consciously, and the alternative we did not pick.
We use Pipecat instead of building our own orchestration. The win is months of saved engineering. The cost is being a release behind on a few model integrations.
We use Anthropic as the default LLM with OpenAI failover, not the other way around. The win is consistently lower hallucination rates in our eval set. The cost is slightly higher cost-per-token at the equivalent model tier.
We run a custom eval harness instead of using a vendor product. The win is the eval set lives in the same Git repo as the prompts, so PRs that change prompts fail the build if they break an eval. The cost is we own the upkeep.
We use Twilio over a cheaper telephony provider. The win is concurrency ceiling and the depth of the diagnostic tools. The cost is roughly 18 percent more per minute.
We deploy on Fly.io, not Vercel. The win is real persistent connections and global edge POPs that survive long-lived voice sessions. The cost is more devops overhead.
These tradeoffs are not laws. They are starting points. If you tell us you have an existing GCP estate, we will adapt the stack. The principles do not move; the implementations do.
Below: the matrix we walk clients through.
| Factor | Human receptionist wins | AI wins |
|---|---|---|
| Call volume | < 50/mo | > 200/mo |
| Avg call complexity | High emotion, novel | Routine intent, structured |
| Hours coverage needed | Business hours | 24/7 |
| Languages | 1-2 | 1-6 |
| Vertical regulation | Heavy HIPAA/legal | Light to moderate |
| Cost ceiling per call | > $5 acceptable | < $1 required |
| Integration depth | Loose (write notes) | Tight (CRM, calendar) |
The hybrid that beats both: AI as front-line, human escalation within 60 seconds for emotion/complexity. We deploy hybrid in roughly 70% of our voice projects. The economics: AI handles 75% of volume at $0.18/call, humans handle 25% at $4.50/call. Blended: $1.26/call versus all-human at $4.50 or all-AI at $0.18 but with a quality floor.
Looking back at the last six deployments in this category, three things we would do differently:
Start the eval harness on day zero. We have always said this and we have always slipped it. The first time we shipped without a regression eval, we caught a prompt change that silently degraded conversion by 11 percent for two weeks before anyone noticed. Now we treat the eval harness as the first deliverable, before the first prompt.
Get the executive sponsor in the first user-acceptance session. Not the project manager, not the ops lead. The owner or the C-suite person whose name is on the budget. Their reaction to the first live test changes the trajectory of the project. Their feedback in week four is too late.
Document the human escalation paths before the AI ships. Every project we have shipped that did not have written escalation procedures had a moment in week two when an unexpected case hit, the AI escalated, and nobody knew who was supposed to handle it. Documenting the human side before the AI ships is half a day of work that prevents a week of fire-fighting.
If you want to talk through how any of this applies to your specific situation, grab a 20-minute call. We do not pitch on the call. If you would rather read more first, the docs and our comparisons cover most of the underlying technology choices in writing.
The most common failure mode with voice for virtual-receptionist businesses is treating the problem as a model selection problem. It is not. The model is the easy part. The hard parts are the data pipeline feeding it, the eval that catches regressions, and the human ownership layer that keeps the system honest after the implementer leaves the building.
We have shipped this category of system enough times to recognize a few patterns. The teams that win allocate roughly 20 percent of project time to the model and prompts, 40 percent to data and integrations, 25 percent to evals and observability, and 15 percent to change management. The teams that lose flip those numbers, spend 70 percent on prompts, and end up with a great demo that nobody trusts.
The good news is that none of this is novel engineering. The patterns are well-understood now. The discipline to follow them is the rare part.
Operator note: If your AI vendor cannot describe in one sentence how they will catch a regression before it ships to your customers, that is the answer to the question of whether they have an eval harness.
This post is the short version. The long version takes 90 minutes and a whiteboard. If you want the long version, grab a slot and bring your worst metric. We will work backward from there.
Or, if you are still in the read-and-think phase, our docs and comparisons pages have most of the answers in writing.
The fastest way to validate this for your business is to pull 30 days of relevant call, chat, or interaction logs and run them past whatever stack you are considering. The vendors who can show you, on your data, what their agent would have done are the ones worth a second meeting. The vendors who want to skip that and jump straight to a pricing call are not.
If you want help running that exercise, book a 20-minute call and we will walk through it on the call. We do not bill for the working session and we do not pitch on it. Bring your own data; leave with your own conclusions. If you would rather poke at the math yourself first, the ROI calculator and the cost estimator cover most of the common scenarios in five minutes each.