Skip to content
Telecom · Platform

Cloud IVR

A caller wants to complete a task, not navigate a platform. OVOO Cloud IVR lets your service team design that journey: what the caller hears, how they respond and when the flow transfers them to an agent or business system.

SIP/IMS readyPABX & hunt groupsRecording & compliance

Define what the caller should be able to finish

Agree the caller journey before choosing its blocks: the entry number, the self-service task, the route to an agent and the follow-up that completes the interaction.

  • Which tasks callers can complete in self-service
  • Where hunt groups and queues take over
  • How short numbers and internal dialling reach the flow
  • Which journeys belong to the call centre
  • How fixed and mobile SIP/IMS calls enter
  • Which interactions require recording and consent
  • When SMS/MMS, email or fax completes the task
  • Who maintains the flow through the portal or APIs

Build and maintain the callflow

Author the caller journey

Use the visual designer or YAML-as-code to assemble reusable callflow blocks. A/B and staged rollouts let the service team introduce a changed journey in a controlled scope.

Accept speech or keypad input

Connect speech recognition and synthesis to the flow, with bot hand-offs to Dialogflow, Lex or Rasa. DTMF provides another input path when the caller cannot complete the speech interaction.

Continue the task after the call

A flow can send an SMS/MMS or email follow-up, arrange a callback or invoke a webhook. The voice interaction becomes one part of the customer service process.

Apply the recording policy

Select which interactions are recorded and where consent is required. Encryption, redaction, WORM storage and retention policies govern the resulting recordings.

Transfer within the voice network

Integrate with TAS, SBC and IMS for transfer, consultation, conferencing and announcements. The flow determines when the caller stays in self-service and when another destination is needed.

Measure the journey outcome

Track containment, wait time and transfers rather than counting completed calls alone. Traces and alerts help identify the part of a flow that needs attention.

The runtime behind the journey

SIP or HTTP starts a flow. The callflow engine invokes the selected speech, bot and business-system integrations, then exposes recording, analytics and service events.

Stateless workers run behind a queue with a cache tier and replicated databases. These views show the deployment dependencies and the place of Cloud IVR in a wider voice-service environment.

Deployment - Voice Backend nodes, queues, caches and databases
Deployment view - backend nodes, engines, queues/caches and DB replication.
  • Stateless workers with message queues
  • Cache tier for prompts and lookups
  • DB replication and backups
UCaaS / CPaaS stack with Service Broker, Voice API Gateway and SIP Core
UCaaS/CPaaS stack - Service Broker, Voice API Gateway, SIP Core and integrations.
  • Voice API Gateway and Service Broker
  • SIP Core integration (TAS/SBC/IMS)
  • Hooks to CRM/BI via webhooks/APIs

Design for the moments when the journey changes

A working IVR needs a defined route through routine tasks, traffic peaks, failed input and agent hand-offs.

Speech input does not complete

A caller may not finish the recognition path. Define the DTMF alternative and the point where the flow offers another route, so speech is an input choice rather than the only way through the service.

The enquiry needs an agent

Decide which queue or hunt group owns the request and whether the flow transfers or consults. Language routing and the hand-off point belong to the caller journey, alongside the automated steps.

The task continues outside the call

A callback or message follow-up can carry the remaining step. Connect the SMS/MMS, email or webhook action to the business system that completes the work, then decide what the caller hears before leaving voice.

A changed flow reaches live traffic

Review containment, wait time and transfers while the staged rollout is still limited. A shorter journey is useful only if callers can complete the intended task or reach the right destination.

Discuss Cloud IVR