Skip to main content
When the AI hands a session off, OpenCX opens a Genesys Cloud conversation and your flow routes it to a queue. This page covers where that conversation goes and what the customer is told. All of these settings are on the Handoff tab.

How handoff works

OpenCX opens one Genesys message conversation per session, starting with the customer’s latest message. Your inbound message flow routes it to a queue. New customer messages and agent replies then pass through OpenCX, with files where the channel carries them. Your flow can read this participant data, always as text: The full summary, opencx_transcript, opencx_sentiment and opencx_handoff_reason (why the AI handed off) follow on the customer participant once the conversation opens. All of it is plain text.

Use your own flow

OpenCX imports and publishes an OpenCX Inbound Messages flow for you. To route with your own flow, choose Use my own flow beside Routing on the Setup tab, any time. A minimal flow: Connection check expects the OpenCX flow. With your own flow, use Test session on the Diagnostics tab for the round trip.

When no agents are available

When no agents are on the queue decides what happens if nobody is on the target queue at handoff. If OpenCX can’t tell, or there’s no target queue, it hands off.

Expected wait

With Tell the customer the expected wait on, the customer gets one more line right after the handoff: when an agent should be with them, as Genesys estimates it for their conversation in the target queue. It reads in the session’s language, rounded: “less than a minute” or about so many minutes. With no estimate, an estimate over two hours, no target queue (your flow picks the queue), an email session, or a native email or messaging handoff, nothing more is said and the handoff is as before. The handoff never waits for the estimate. The estimate is kept on the session as genesys_estimated_wait_seconds, for workflows and reports.

Business hours

By default OpenCX uses your office hours to decide whether a handoff can happen now. To use the hours you already keep in Genesys instead, pick a schedule group under Business hours. OpenCX then reads that group the way Genesys does:
  • Times are read in the schedule group’s time zone, so daylight saving changes and schedules that run past midnight work as they do in Genesys.
  • Emergency groups belong to call flows in Genesys, not to the messaging flow OpenCX hands off through. So any emergency group switched on counts as closed.
  • Outside these hours a handoff does exactly what it does outside your OpenCX office hours: the outside office hours settings decide.
  • Once you pick a schedule group, it replaces your default OpenCX office hours everywhere they are used: handoffs, the within office hours value workflows get, voice transfers, and automatic team assignment for teams without their own office hours.
  • Teams with their own office hours, SLA clocks and auto-replies are unchanged.
  • OpenCX reads the group again every five minutes, so a change in Genesys, including an emergency, applies within five minutes.
  • Picking Use OpenCX office hours goes back to your office hours.
If Genesys can’t be read, or doesn’t answer within two seconds, OpenCX uses your office hours and Health on the Setup tab shows Business hours with the reason. While OpenCX is reading the group, other checks use your office hours instead of waiting. See troubleshooting.

What the Genesys agent sees

The handoff note, notes and context in the agent desktop.

Sessions and sync

What changes each way once the conversation is open.

Agents, queues and teams

Link teams to queues so handoffs land in the right place.

Fix handoffs and routing

Nothing in the queue, failed handoffs, warnings.