- 01
Market
Saudi Arabia
- 02
Written for
COO, Head of CX
- 03
Decision
Replace or support a switchboard with a voice agent
- 04
Languages
EN · AR
The call
What happens between ringing and a person
Five steps, with the handover reachable from every one of them. A call that cannot escape the flow is the design defect this arrangement exists to prevent.
A call flow: answer, identify the destination, check availability, transfer with context or take a message, with human handover reachable from every step.
- 01
Answer and listen
Greeting in Arabic with an English fallback, then an open question rather than a menu. Callers state their business faster than they navigate options.
- 02
Identify the destination
A person, a department, or a task. Names are matched against the directory with transliteration handled, because a caller says a name the way it sounds rather than the way it is spelled in the system.
- 03
Check availability
Presence from the phone system and the calendar, so a transfer is offered only where it will be answered.
- 04
Transfer with the context
The recipient sees who is calling and what they said before they answer. That is the difference between an assistant and an obstacle.
- 05
Or take the message properly
Written into the CRM or ticket queue the recipient already works from, with a callback number confirmed back to the caller.
Human handover
Reachable at any point, on request, on a second failed understanding, or on any signal of distress or urgency. The caller never repeats themselves — what was said travels with the transfer.
What decides it
The directory is the hard part
Speech handling is largely solved for this use case. What is not solved for you is your own directory: names spelled several ways, people who moved team last quarter, departments callers know by an old name, and the three individuals everyone actually asks for regardless of the org chart.
So the first week of an engagement is spent on the directory rather than on the model: reconciling it against the phone system, adding the aliases callers actually use, and recording which destinations are allowed to receive a transfer at all. Agents that route badly almost always route against a directory nobody had cleaned.
Edge cases
The calls that decide whether it stays switched on
Every deployment is judged on these rather than on the ordinary call, and each has an answer that is a design decision rather than a model setting.
The caller is angry before the agent speaks
A person within seconds, which is the only acceptable outcome here.
Escalation on the first signal, without attempting to resolve or to ask qualifying questions.
They ask for someone who has left
Told plainly and connected onward, rather than transferred into an unanswered extension.
The directory records the successor, not a dead entry. Where there is none, the department takes it.
Two people share a name
One extra question, which costs less than a wrong transfer costs both of them.
One disambiguating question — department or role — then transfer. Never a guess.
The call is about an emergency or a safety issue
The process your organisation already defined for it.
Routed to the standing procedure immediately, with no automation in the path.
Our role
What a deployment involves
- 01
Evaluation before build
We build an evaluation set from a week of your real calls — accents, code-switching, the names people actually ask for — and measure against it rather than against a demo script.
- 02
Telephony and directory integration
The agent sits in your existing phone system rather than beside it, so transfers, presence and call recording behave the way the organisation already expects.
- 03
The handover path
Built first and tested hardest, including out of hours, because the failure that ends a pilot is a caller trapped in a loop at eight in the evening.
The queue design and who staffs the escalation path stay yours; we make sure the path exists, is reachable from every step and carries the context when it is used.
Common questions
What buyers ask
Should the greeting say it is an automated receptionist?+
They should, and the agent says so in the greeting. Beyond the ethics, it changes caller behaviour usefully: people state their business more directly to a system than to a person, which improves routing. What loses trust is a system that pretends to be human and is then caught by an ordinary follow-up question.
What happens to the people currently on the switchboard?+
In the deployments that work, they move to the escalation path and to the calls that need judgement, and the volume they handle drops rather than the headcount. A deployment planned as a headcount reduction tends to remove the escalation capacity at the same time as it creates the need for it.
How long before it is answering real calls?+
Four to six weeks to a supervised pilot on one number, most of which is the directory work and the evaluation set rather than the agent itself. Running it in parallel with the existing switchboard for a fortnight before any cutover is what makes the difference between a launch and an incident.
In this cluster
See it on your own call flows
A working agent on one number, evaluated against a week of your own calls before anything is switched over.
Start the conversation
