An AI receptionist that answers your calls and books the next step
When the lines are busy or the office has closed, the agent picks up. It answers from information you approve, takes the caller’s details, then books a slot or takes a message for the right person.
What happens on a call
- It picks up. The agent greets the caller with the opening line you agree.
- It finds out why they called. A new enquiry, an existing booking, a question for accounts, a supplier. You decide the list.
- It handles or routes. Routine questions get an answer, bookings go into your calendar, and existing customers hear their booking or order status if your system can share it. New enquiries for sales, payment questions for accounts and anything outside the brief become a callback for a person.
- It leaves a note. Your team sees who called, what they wanted and what was agreed.
When a person takes over
The agent hands over when a question falls outside what you approved, or when the caller asks for a person. Your team calls the caller back. If you prefer, the call can transfer live to a staff phone instead. Whoever picks it up gets the notes from the call, so the caller does not repeat themselves.
After hours and missed calls
We can set the agent to take calls outside office hours and leave a callback task for the morning. We can also build a missed-call number: a customer gives a missed call and the agent rings them back.
Reminders and callbacks to people who booked or enquired are covered on the follow-ups page.
Where the details go
Bookings and call notes can go straight into your calendar or CRM where it offers an API (integrations), and the agent can check open slots before it books. Otherwise they arrive by email or in a shared sheet. The work after the call, like sending a quote, is automation.
What it runs on
We run real-time voice on a self-hosted LiveKit setup for our own voice work (LiveKit). We use Plivo for Indian numbers (Plivo). Our own sales team makes its calls through Microsive Dialer, software we built (Microsive Dialer).
How we build it
You get a written scope and a fixed quote before work starts. Changes are quoted before they are done. You see the agent working at regular demos. The code and repository are yours at handover.
Calls or chats?
Some customers would rather type. The same answers and handoff rules can run in a WhatsApp or website bot (AI bots). For sector examples, see voice agents by industry. For clinics, see the AI receptionist for clinic bookings.
FAQ
Can we keep our current business number?
Yes. Numbers are bought in your own provider account, and an existing number can be ported to that account. How long a port takes sits with the operators, so we do not put a date on it.
How many calls can it take at once?
That depends on your telephony plan and what we scope. We agree how many calls should run at the same time before launch and write it into the scope, so there is no single number to quote here.
Are calls recorded?
Yes. Calls are recorded, and the agent says so at the start of the call rather than leaving the caller to find out later. The recordings and the call notes sit in an account you own.
Who runs the agent after launch?
It runs in an account you own. We deploy it and host it, and what we cover after launch follows the support level agreed in your scope.
Which language will the agent speak?
The one your callers use. Language is a project decision rather than a fixed list: tell us who the agent will talk to, and we test a model in that language before we commit to it in the scope. That includes languages spoken outside India.
Which calls go unanswered today?
Someone from our team replies within one business day.