Never Miss a Call With an AI Receptionist

A missed call rarely gets a second chance - the caller already has the next number in the search results. The most reliable fix is to never let the phone ring out in the first place - switch the number to an AI receptionist that picks up every time, even at midnight or on the busiest day of the week.

Where calls get lost in the first place

Every volai number always has a routing setting: it either goes to an AI receptionist, forwards to another phone, routes over a custom SIP connection, or has nothing set at all. The most common trap is forwarding to the owner's mobile - it works great until the owner is not reachable, and a mechanic under a car, a shop owner meeting a supplier, or restaurant staff mid-service simply do not pick up. The call just rings and disappears, as if it never happened. The same trap catches a tradesperson found through nothing more than a business card with a phone number on it - if they do not pick up, the next lead just calls someone else.

To the caller, this does not read as a minor inconvenience - it reads as a business that does not answer its phone. The difference between "nobody could take it right now" and "this business cannot handle calls" comes down to how quickly the next ring gets answered - and that is exactly what an AI receptionist now handles, for a fraction of what a lost job is worth.

What happens to a call nobody answers

Without an agent, a call like that has no safety net - no voicemail box to leave a message in. volai still records the call with a missed status, and if a webhook is enabled in the portal, it sends a call.missed event about it. That at least makes it possible to find out afterwards that a call happened and when - even though its content stays unknown, because no one ever picked up.

How an AI receptionist fixes it

The fix is simple: switch the number's routing from forwarding to an agent. Both the portal and the API do it in a single request - set routing.mode to agent and add the ID of the agent that should answer:

curl -X PATCH "https://volai.cz/v1/numbers/+420601234567" \
  -H "Authorization: Bearer vk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"routing": {"mode": "agent", "agentId": "ag_kx91fa2b"}}'

From that moment on, the number is always answered by the AI receptionist following its system prompt - no more depending on whether someone happens to be near a phone. It can also transfer a call to a human when the caller asks for one or runs into something it cannot handle itself (how that gets turned on is covered below). A transfer is then billed as a regular outbound call (0.92 CZK/min), with no agent surcharge, because the agent is no longer on the line. There is one honest caveat: a transfer does not carry a summary of what was already said, so the caller has to repeat the reason for the call.

What needs to be ready first

Switching the routing is one request, but for the receptionist to actually be useful, it needs an agent with a system prompt already set up - who it is, what it can handle, and how it wraps up a call - before the number gets pointed at it. Without a prompt the agent does not know what to say, and the call would go worse, not better. A guide to writing one, plus three ready-made samples to copy, lives on the voice agent page. Transferring to a human is set up separately, too - without a transfer number in transferTo, the agent cannot transfer a call no matter what the system prompt promises.

What is left behind even when a call cannot be resolved

Even an unresolved call leaves something behind. The agent can capture its own custom fields from the call - a name, a phone number, the reason for calling - even when it cannot handle the request itself. After the call, a full transcript and a short summary are available through the REST API, or both arrive straight away as a call.completed webhook. Compared to an empty ring, that is a real difference: instead of nothing, there is at least a contact to call back.

What an AI receptionist honestly cannot do

This is not a cure-all: a call lasts at most ten minutes before the agent ends it itself, and if the caller stays silent for twenty seconds, the agent treats that as the end of the call and hangs up. The agent also cannot do anything outside its system prompt or connected tools - a well-written prompt tells it explicitly what it must never make up, and in that moment it should say it does not know rather than invent an answer. That is a boundary to plan around, not a bug - and it still beats a phone nobody ever picked up.

Can this be wired up to a text message alert?

Not automatically out of the box - volai does not document a built-in feature that texts a missed-call summary on its own. It can be assembled from existing pieces in a few lines of code: a webhook on your own server subscribed to the call.missed event (and optionally call.completed too), which then makes a plain POST /v1/messages call to text the owner the moment something happens. The exact webhook shape and how to verify its signature are on the webhooks page.

Where this matters the most

This helps most where staff are physically away from the phone - a workshop, a shop floor, a job site. Auto repair is a typical case: a mechanic dealing with a customer is dealing with a car, not email, and the phone rings while their hands are covered in oil. A concrete prompt and scenario for this trade is on the AI receptionist - auto repair page, alongside other industries. The receptionist also speaks English, Slovak, German and Polish on top of Czech, so a call from a customer who does not speak Czech does not disappear either.

How many calls a business is losing today can be checked without an AI receptionist at all - a week of watching how many calls to the business line go unanswered, compared with what an average completed job is worth. A calculator that turns those two numbers into a rough monthly benefit lives on the AI receptionist page.

Switching a number's routing itself is free and takes a couple of minutes. A minute answered by the AI receptionist costs 3 CZK - the incoming call plus the agent surcharge, billed by the second and excluding VAT. The full rate card is on the pricing page, and the complete list of what the receptionist can do is on the AI receptionist page.

What's next