Voho is delivering Aramco's AI call center.
voho.ai
Integration17 November 20269 min

How to add an Arabic AI voice agent to your existing Avaya, Genesys or Cisco call centre

Add an Arabic AI voice agent to Avaya, Genesys or Cisco without replacing the PBX: route calls to it over SIP, transfer back with REFER, and pass context.

You add an Arabic AI voice agent to an existing Avaya, Genesys or Cisco call centre by treating it as one more SIP destination: the PBX or contact-centre platform routes selected calls to the agent over a SIP trunk, and the agent sends the call back to a queue or an extension when a human should take over. Nothing in the existing estate has to be replaced, and the phone numbers callers already dial stay the same.

The work is in four places: the routing rule that decides which calls go to the agent, the audio format on the trunk, the transfer back to a human, and the context that travels with that transfer. This guide takes them in order, with the questions to put to your telephony team before anyone writes a line of integration.

Why a SIP leg is enough

Avaya, Genesys and Cisco contact-centre platforms all speak SIP, the signalling protocol defined in RFC 3261, either natively or through a session border controller (SBC) or gateway at the edge. A voice agent that also speaks SIP looks to your platform like any other endpoint, trunk or application server. That is why the integration is a routing and configuration exercise rather than a platform migration.

The detail varies by product and by version: which SIP features your platform exposes, whether calls pass through an SBC, and how queues and agent states are modelled. Treat this guide as the shape of the work, and confirm specifics against your own platform documentation and your integrator. Voho does not need your platform to change vendor; it needs a SIP path and a clear rule for when to use it.

Four ways to place the agent in your call flow

PlacementWhen it fitsHow the call reaches the agentHow a human takes over
Front doorThe agent greets every caller on selected numbers and resolves what it can.The platform routes the dialled number to a SIP trunk or route that points at the agent.The agent transfers the call to a queue, skill group or extension on your platform.
OverflowCallers wait too long at peak and some abandon.A queue-time or capacity rule sends excess calls to the agent instead of holding them.The agent hands the call to a human queue as agents free up, or books a callback.
After hoursNobody answers overnight, at weekends or during holidays.A time-of-day rule routes the number to the agent outside staffed hours.The agent resolves the request, logs it, or queues it for the morning team.
Specific intentsOne high-volume request type, such as appointment booking or status checks.An IVR menu option or a dedicated number routes that request type to the agent.Anything outside the intent returns to the normal menu or a human queue.

Most teams start with after hours or overflow, because the risk is lowest: those calls are currently abandoned or unanswered, so the agent cannot make the experience worse. Front door and intent-based routing follow once the containment numbers justify them.

The routing rule is a business decision

In Avaya, Genesys and Cisco environments alike, call routing is already expressed as rules: by dialled number, caller, time, queue depth, IVR choice or skill. Adding the agent means adding one more destination to those rules. The decision worth taking early is the fallback: if the SIP path to the agent is down or the agent does not answer, the call must fall through to your existing queue rather than ring out. Every platform has a way to express this; make it part of the design and test it before go-live.

  • Which dialled numbers or IVR options send calls to the agent, and which never do.
  • What happens when the agent does not answer: a failover route to a human queue or voicemail.
  • How callers who say they want a person are handled on the first turn, with no friction.
  • Which calls are excluded, for example certain callers, or intents you have decided the agent must never attempt.

Audio on the trunk: what to confirm

Telephone audio on a SIP trunk is usually G.711, the ITU-T codec that carries 8 kHz audio in either μ-law or A-law companding. Voho’s agent works with 8 kHz μ-law audio, the format Cisco, Avaya and SIP trunks already carry, so in the normal case no transcoding step is needed on your side. If your trunk carries A-law, an SBC or gateway typically handles the conversion; confirm that with your telephony team rather than assuming.

Two practical checks matter more than the codec name. First, DTMF: if callers press keys for account numbers or menu choices, agree whether tones travel in-band or as RFC 4733 telephone events, and test it with real handsets. Second, audio quality on a real line: dialect recognition is tested on telephone audio, not studio audio, so run your acceptance calls over the same path callers use.

Transferring back to a human

The transfer is where integrations succeed or fail, because a caller who is handed to a human and has to start again has experienced a step added, not removed. The standard SIP mechanism for asking another party to transfer a call is the REFER method (RFC 3515): the agent tells your platform to connect the caller to a target, such as a queue address or extension, and your platform completes it under its own routing rules.

Whether you use a blind transfer, where the agent sends the caller on immediately, or an attended transfer, where the destination is reached first, depends on what your platform supports and what your supervisors want. Either way, the human who receives the call should land in the right queue, with their normal screen pop. That is the platform’s job; the agent’s job is to supply the right destination and the right context.

Context travels separately from the call

SIP carries the call, not the conversation. Caller identity, the summary so far, the detected intent and the actions already taken have to reach the human agent through a second path: SIP headers if your platform reads them, a CTI or screen-pop integration, or an API write into the CRM or ticket that the agent’s desktop already displays. Decide which path your platform supports before the project starts, because it determines what the human sees at the moment of transfer.

Voho’s transfer carries the caller identity, a summary, the detected intent and every action already taken, so the caller does not repeat themselves. When to transfer is a rule you set, not something the model decides on its own; our guidance on that is in the voice agent metrics piece.

Questions to ask your telephony team

  • Is there an SBC or gateway between the carrier and the platform, and who administers it?
  • Can the platform route to an external SIP destination, and can it do so by number, time, queue depth and IVR choice?
  • Does the platform support REFER, or does it need another transfer method?
  • How are DTMF tones carried, and does the trunk use μ-law or A-law?
  • How many calls can the SIP path carry at once? Voho supports up to 15 concurrent calls, so agree the numbers against your peak.
  • Where do queue statistics and call records for agent-handled calls need to appear in reporting?
  • Which environments exist for testing, and can acceptance calls run on a non-production number first?

If the answers raise problems, they are usually about one of three things: an SBC that needs a new route, a transfer method the platform handles differently, or a context path that needs a small integration. None of them requires replacing the platform.

A rollout order that limits risk

  • Test on a non-production number with your team calling in, covering Saudi dialects, English mixed into Arabic sentences and the transfer path.
  • Go live on after hours or overflow for one number, with the failover route tested by switching the agent off.
  • Listen to real calls every week and measure containment per intent, counting only outcomes that exist in your system of record.
  • Widen to more numbers or to front-door routing once the transfer experience and the measured results justify it.

If you have not yet decided how to count success, start with the five metrics in our voice agent metrics article, and see the broader picture of running on the phones you already have in our guide to AI call centres in Saudi Arabia. If you also need the number side sorted, the Saudi phone numbers page covers the routes.

How Voho does it

Voho builds Arabic-first voice agents that connect to the Cisco, Avaya or SIP estate you already run, on your existing numbers and queues, with English handled too. We do not ask for new numbers or a replacement PBX. Audio is available as 8 kHz μ-law, so the agent sits on a normal SIP trunk.

Voho sends forward deployed engineers to sit with your team and get the agent working on real calls: the routing rule, the failover, the transfer and the context path are built against your actual platform rather than a specification. Customer data can be stored in Saudi Arabia, and our security page sets out what we do and do not claim. The pricing page shows what a paid plan includes, since going live on a real phone line needs one, and you can book a demo to walk through your call flow.

Sources

Frequently asked

Do I need to replace my Avaya, Genesys or Cisco platform to add an Arabic AI voice agent?
No. The agent is added as one more SIP destination. Your platform routes selected calls to it over a SIP trunk and takes calls back through a normal transfer, so the existing platform, queues and numbers stay in place.
How does the AI voice agent connect to our phone system?
Over SIP, the signalling protocol that Avaya, Genesys and Cisco contact-centre platforms already use, directly or through a session border controller. Voho’s agent works with 8 kHz μ-law audio, which SIP trunks commonly carry, so a transcoding step is usually not needed.
How does a call transfer from the AI agent to a human agent?
Typically with a SIP REFER (RFC 3515), where the agent asks your platform to connect the caller to a queue or extension. Context such as caller identity, summary, intent and actions taken travels on a separate path, such as SIP headers, a CTI integration or a CRM or ticket write, depending on what your platform supports.
What should I do if the AI voice agent is unavailable?
Build a failover into the routing rule so that calls fall through to your existing human queue or voicemail if the SIP path is down or the agent does not answer. Test it before go-live by switching the agent off.
Which calls should I send to the agent first?
After-hours and overflow calls are the lowest-risk start, because those calls are currently unanswered or abandoned. Move to front-door or intent-based routing once measured containment per intent supports it.

Keep reading

Deployment-ready

Start your AI transformation today.

Sign up and build your first agent in the browser, or book a call if you would rather someone walked you through it. Most people do not need the call.

Start

$5 of credit, free

Granted when you sign up, about 70 minutes of live calls. No card to begin.

Then

Plans from SAR 109 a month

Starter puts your agent on your website, Business on a Saudi phone line. Cancel any month.

When you need it

Enterprise terms

Saudi data residency, an uptime SLA and on-premise deployment, on an agreement.