The phone and the chat widget,
answered by the same agent
A ringing phone nobody picks up and a chat bubble nobody answers both cost the same thing: a customer who walks away before your team even knew they called. This agent answers both, in your business's voice, routes what needs a person and books what does not.
The role today
Small businesses lose a predictable share of calls to voicemail that nobody checks until the next morning, by which time the caller has already phoned the next business on the list. The chat widget on the site fares little better: a question typed in at 9pm sits unanswered until someone logs back in. The cost is not visible on any report, it is just a caller who went elsewhere, which is exactly why it keeps happening.
What the agent takes over
The agent answers the phone and the chat widget with the same greeting, tone and knowledge of your business, whichever one the customer picks. It asks the questions a human receptionist would ask, what they need, when, which location, and routes the call or chat to the right person or department based on rules your team sets, or books the appointment directly into your calendar if the request is routine.
For anything it cannot resolve, it takes a message with the caller’s name, number and reason, reads it back to confirm accuracy, and delivers it to the right inbox immediately rather than at the next check-in. Every call and chat is transcribed, so a manager can see exactly what was asked and answered without listening to a recording end to end. The agent runs around the clock, which means the 7pm call and the Sunday chat get the same answer quality as the Tuesday morning one.
The agent also keeps a running profile per caller or chat contact where that helps, a returning client whose usual request is a specific service, a vendor who always asks for the same contact, so routing gets faster the more the business is used, not just consistent from day one. Multi-location businesses get one shared brain with location-specific routing rules rather than a separate setup per branch, so a caller reaching the wrong location by habit still ends up routed correctly. Call volume and chat volume are reported together, not as two separate numbers, since a slow week on the phone and a busy week in chat usually describe the same underlying demand, just arriving through a different door.
What stays with humans
Any request involving a price negotiation, a complaint, or a situation outside the routing rules goes straight to a person, with the transcript attached. Your team sets and updates the routing rules and the calendar availability; the agent follows them, it does not invent new ones.
Guards
Every interaction is recorded and transcribed for review. Booking only happens against calendar slots your team has marked available, with no override path for the agent. A dry run against a week of real call patterns happens before the line goes live, and a fallback to a human-staffed number is always one step away if the agent is uncertain. The line itself can be ported from an existing number or run on a new one depending on what your phone provider supports, and call quality is monitored continuously so a connectivity problem shows up as an alert rather than a string of missed calls nobody notices until a customer complains. Greeting scripts and routing rules are version-controlled, so a change made by one team member cannot silently undo another’s recent fix, and every version is timestamped against when a related complaint or question came in.
Price and timeline
| Option | Price | Timeline |
|---|---|---|
| Agency runs it | from $2,800 + support plan | 3 to 6 weeks |
| Full control, handover-ready | from $4,750 | 6 to 8 weeks |
“Agency runs it” keeps the agent on our infrastructure with a monthly support plan covering tuning and monitoring. “Full control, handover-ready” delivers the agent on your own servers and accounts with documentation, source and credentials, so your team can run and change it without us; it costs more up front because the handover package, your-infra deployment and internal documentation are built in from day one.
Related
See the AI agents overview for how we build and guard these systems, and Development for the services that often pair with this one. Inside the agents catalogue: Booking reminders and no-show agent, After-hours support agent, Helpdesk triage agent. For a narrower, single-process version of this work, see IVR replacement, Missed call text-back in the automations catalogue. For how the same guard patterns held up on real systems: AI sales agent for seven channels.
Want this running for your team? Get in touch and tell us where the messages pile up.
FAQ
How much does an AI receptionist agent cost?
From $2,800 for voice and chat answering with routing and booking, live in 3 to 6 weeks. Multi-location or multi-language setups run higher.
How long before it is live?
3 to 6 weeks, most of it spent getting your routing rules, calendar access and greeting script right before launch.
Which channels and tools does it work with?
Phone lines through your existing provider or a new number, website chat, and WhatsApp or LINE if customers already message you there; it books into Google Calendar, Calendly or your scheduling system.
What if the agent mishears or misroutes something?
Every call is recorded and transcribed, so a wrong message is caught and corrected the same day, and ambiguous requests are routed to a general line with the recording attached rather than guessed at.
Is call and customer data safe?
Recordings and transcripts live in your own accounts and storage, with retention periods you set; the agent reads your calendar and contact data through the access you grant and can revoke at any time.