AI conversations inside your RingCentral workflows

Route selected RingCX calls to Simple, while RingCentral continues to control the surrounding workflow, queues, and routing rules.

Talk to our team

From RingCX to AI and back

RingCX routes the call

Simple handles the conversation

Your workflow chooses what happens next

What you can do with RingCentral

01 / INBOUND

Choose where AI joins the flow

Add Simple as a SIP-based IVA in Workflow Studio and route selected calls to it.

02 / ROUTING

Return every call to the right path

When the AI session ends, return the caller to the RingCX workflow for the next queue, routing rule, or escalation step.

03 / CONTEXT

Use AI outcomes in your workflow

Pass selected session context to Simple and return structured metadata, such as the caller’s intent, for the workflow’s next decision.

Hand off without losing the thread

Return to the right queue

Use metadata returned by Simple to direct the caller through the appropriate RingCX routing path.

Give the workflow useful context

Return structured details such as intent or outcome so RingCX can determine what happens next.

Built around RingCX Workflow Studio

RingCX connects to Simple through its SIP-based IVA interface. Your workflow controls when the AI joins, what session context it receives, and which path the call follows afterward.

RingCX supports UDP, TCP, and TLS transport, with TLS recommended. When TLS is used, RingCX attempts to negotiate encrypted media. Deployments can also use IP allowlisting and exchange JSON metadata through SIP messages.