The questions teams ask before they build, with the page that answers each one properly.

Language and dialects

Voices ship in Najdi, Hijazi, Gulf, Egyptian, and Modern Standard Arabic, plus English. Saudi Arabic is the focus rather than an afterthought.See Voices for the full catalogue by dialect, style, and age.
Agents follow code-switching mid-sentence rather than forcing the caller to pick a language. It is normal speech in the region and is treated as such.
If you know your callers, match the dialect. If you do not, Modern Standard Arabic is the safe default. See Voices.

Calls and numbers

Both, from the same configuration: inbound answering, and outbound campaigns, callbacks, reminders, qualification, and confirmations. See Telephony.
No. Voho connects over SIP to the trunk or PBX you already run: Cisco, Avaya, hosted, or direct from a carrier. Your numbers and routing stay as they are. See Telephony.
Provisioning is arranged across Saudi Arabia and the Gulf. What is available depends on the number type, the direction, and carrier inventory, and verification is a carrier process. See Phone numbers.
Yes: keypad input works as a fallback for digits, menu choices, and confirmations. See Keypad input.
Yes, with the context from the conversation carried across so the caller does not repeat themselves. Every production line should have this path. See Handoff to humans.

Scale

Capacity is sized against your peak concurrency (the busiest hour of your busiest day) rather than sold as a fixed ceiling. Bring that number, your average call length, and the inbound/outbound split to scoping. See Concurrency.
There is no published cap. What a deployment supports is decided by concurrent call capacity, not by how many agent configurations exist. See Agencies and resellers.

Building and integrating

Yes: REST and streaming endpoints, WebSocket, and voice management. See the API reference.
Yes, through the REST API and webhooks, no dedicated connector needed. See Integrations.
That is what actions are for: logging tickets, checking orders, updating records, mid-conversation. See Actions.
Every call leaves a transcript and a bilingual summary, in the console and through the API. See Transcripts and summaries.

Deployment and data

Managed cloud, an in-country hosted deployment, your own private cloud, or fully on-premise including air-gapped. See Deployment options.
Yes: on-premise runs the whole call path inside your boundary, on hardware you control. See On-premise overview.
It depends on the configuration, and it is worth settling in writing before you build. See Data residency and Security and data handling.

Commercial

Yes: separate workspaces per client, usage broken out per account, your own pricing, and your brand on what the client sees. See Agencies and resellers.
Two shapes: pay-as-you-go per minute with no seats or commitment, and an enterprise agreement for high-volume or regulated operations. Telephony and numbers are quoted separately and passed through at cost.

Ask for pricing against your volume

Bring expected monthly minutes, average call length, and the deployment model.
Something missing here that a customer asked you? It belongs on the page that owns the topic, with a line added to this list pointing at it.