An agent is only worth building once calls actually reach it. Voho does not sell numbers: you bring any number you already have, in one of two ways.

From Twilio

Connect your Twilio account and import the numbers it owns.

Any carrier, over SIP

GO, Mobily, stc, Zain, Maqsam, any other carrier, or your own PBX. Your carrier and PBX stay exactly as they are.

​
Bring your own trunk

Voho takes calls over SIP from the telephony you already run. Cisco, Avaya, a hosted PBX, or a trunk direct from your carrier: the agent sits behind it as a destination, so you keep your numbers, your call routing, and your existing contracts. The calls arrive through a SIP address in your own Twilio account; Phone numbers walks through the setup. There is no requirement to replace or migrate anything. A common first rollout points a single test number or a low-volume queue at the agent and leaves everything else untouched. Audio is carried as 8 kHz mulaw, which is what SIP trunks carry natively. Requesting it directly avoids a transcoding tier and the quality loss that comes with it. See Audio formats.
Keep SIP termination and the agent close to each other on the network. Round trips between them land directly in the pause the caller hears. See Latency.

​
Inbound and outbound

The same agent configuration works in both directions. What changes is who starts the call.
The agent answers, greets the caller in your configured dialect, and handles the request: logging a ticket, checking an order, booking a slot, or transferring to a person. This is where most lines start.
The agent places the call: campaigns, callbacks, appointment reminders, qualification, and confirmations. Outbound runs from a list you supply or a trigger from your own systems. See Integrations.
Nothing stops one deployment doing both. Keep the instructions separate per direction, an outbound reminder call opens completely differently from an inbound service call. See Writing instructions.
Outbound calling carries obligations that inbound does not: consent, calling hours, identification of the caller, and do-not-call handling all vary by jurisdiction. Settle these with your legal team before the first campaign, not after.

​
Keypad input

Callers reach for the keypad when speech is not working: a noisy line, a long reference number, or simply habit from years of IVR menus. Agents accept DTMF tones as a fallback so those callers are not stuck. Use it for what it is good at: digits, menu selections, and confirmations. Do not rebuild an eight-level IVR tree behind an agent that could have asked the question.

​
Transfer to a person

Warm transfer hands the call to a human over the same trunk, with the context from the conversation carried across so the caller does not start again. When and how that fires is a design decision worth its own page. See Handoff to humans.

​
Concurrency

Capacity is sized against your peak concurrent calls, not your monthly volume. The number that matters is the busiest hour of your busiest day, since that is what the deployment has to survive. Bring that figure to scoping along with average call length and the inbound/outbound split.

​
What Voho does not do

Voho is not your carrier and does not sell numbers. Call carriage, number rental, and per-minute telephony charges come from your carrier and from Twilio, billed to you directly. See Phone numbers.

Phone numbers

Bringing your numbers, from Twilio or any carrier over SIP.

Integrations

Trigger outbound calls and push results into your systems.