Deliberately not an AI receptionist. The questions being asked were fixed, small in number and identical every time, which makes a recorded menu the correct tool: it cannot mishear, cannot invent an answer, cannot be talked into a quote, and costs a few dollars a month to run. We reached for the simplest thing that solved the actual problem.
📞
Personal number stays personal
A Real Business Line
The shop got its own local number, which is now what the Google listing, the signage and the invoices point at. The owner's personal mobile went back to being personal, and it sits behind the system rather than in front of it. The business number is an asset the shop owns and can hand to a future employee; a personal cell never was.
Stack: Dedicated local business number, Google Business Profile and public listings repointed to it.
🔢
Hours, address, or a person
Three-Option Menu
Callers hear a short greeting and pick: opening hours, the address and directions, or put me through. The two informational branches answer completely and then offer the same choice again, so a caller who listened to the hours and then decided they do want to speak to someone is one keypress away rather than having to hang up and redial.
Stack: Serverless call-handling functions, keypress routing with return-to-menu on every branch, invalid-input handling that repeats rather than hangs up.
🔀
Only the calls worth taking
Connect on Request
Choosing to speak to someone forwards the call to the owner's mobile, which now rings for a caller who has already self-selected as needing a person. The interruption still happens, but it happens for a booking or a diagnosis rather than for what time you close on a Saturday.
Stack: Call forwarding to the owner's handset, with the business number as the presented identity.
🎙️
One voice, every time
Consistent Recorded Prompts
Every prompt is synthesized in a single voice rather than recorded on a phone in a noisy workshop, so the shop sounds the same on every call and does not sound like a man shouting over a compressor. Changing the hours means regenerating one audio file and replacing it, which takes minutes and needs no re-recording session.
Stack: Synthesized voice prompts as hosted audio assets, referenced by the call functions via one configurable base path.
💵
A few dollars a month
Costs Almost Nothing to Run
Around a dollar a month for the number and cents per minute for calls, with the hosting and the functions free at this volume. There is no per-seat answering-service subscription and no monthly fee to us. For a one-bay shop that is the difference between a system that survives a slow month and one that gets cancelled in January.
Stack: Usage-priced telephony, free function and asset hosting at this call volume, no recurring agency fee.
📗
Handed over, documented
Owner Runs It
The shop was handed a written guide covering how the menu is wired, how to change the hours, how to add a fourth option, and what every line item on the bill is. The accounts are the shop's own. Nothing about keeping it running depends on us being reachable, which for a build this size matters more than it would for a big one.
Stack: Step-by-step runbook, client-owned telephony account, source for both call functions handed over.