Answering service vs. AI receptionist: which fits a 5-person shop?
A 5-person plumbing operation has three trucks, a dispatcher who also does invoicing, and an owner who's still on his tools most days. They miss enough calls that they finally decide to fix the phone situation. The shortlist comes down to two options: hire a human answering service that's been around for decades, or layer an AI receptionist onto the existing line. Both can technically handle the inbound. The decision usually comes down to one feature only one of them has.
This post is about that feature. Call-answering quality isn't the deciding factor (both are competent). Price math matters but doesn't settle it either. The real decision driver is the bidirectional owner-side AI, and no human answering service has anything like it.
What a human answering service is built to do
A traditional answering service is an inbound-only product. The customer calls your forwarded number, a human receptionist picks up, follows your script, takes the message, dispatches the lead to you. That's the loop. It's a clean, mature product. Smith.ai, Ruby Receptionists, AnswerConnect, PATLive, and Abby Connect all do it well in slightly different flavors.
The economics: per-minute billing against a monthly bucket, starting around $250-$329/month for the smallest tiers and scaling up by call volume. A 5-truck shop pushing 150 calls a month at 4-minute average will run around $450-$700/month depending on which vendor.
The product loop is one-directional in a specific way that matters. The receptionist talks to your customer when your customer calls in. The receptionist does not talk to your customer when YOU want to send a message to your customer. That second direction is a thing you need, often, in service-business operations. And no human answering service offers it.
The bidirectional gap
Here's the operational scenario. A plumber is finishing a job in Mississauga at 1:47pm. He's running late for his 2pm appointment in Etobicoke. The customer at the 2pm needs to know. The plumber doesn't want to dial her directly because he's still in the previous customer's basement and his hands are full. He texts the office: "Tell Janet I'll be there at 2:30."
If the office is a human dispatcher, the dispatcher reads the text, dials Janet, leaves a message, sends a text. Done in 30 seconds.
If the office is a human answering service like Ruby or Smith.ai, the situation breaks. The receptionist on your account is configured to receive inbound calls from your customers. They're not set up as an outbound communication relay for you. You can't text "Tell Janet I'll be there at 2:30" to Smith.ai's number and have them pick up the phone and call Janet on your behalf. That's not what they sell. Their product is inbound, not bidirectional.
This isn't a hypothetical edge case. For a 5-person plumbing operation without a dedicated dispatcher, customer-facing communication during the workday is a constant. The owner and the lead tech are both on tools. The two helpers are out on jobs. Someone needs to relay "running late," "we're 10 minutes out," "the part we need is back-ordered, we'll come Thursday," "we found something extra in the basement, can we extend by an hour" multiple times every day. Without a dispatcher, that someone is the owner, while he's still under a sink.