> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Genesys Cloud handoff settings

> How an OpenCX session reaches a Genesys Cloud queue: routing, smart routing, what happens when nobody is free, the expected wait and business hours.

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.

| Setting | What it does | Default |
| - | - | - |
| **Genesys connection on** | Off stops new handoffs, AI answers on native Genesys channels and updates from Genesys. The connection stays. | On |
| **Handoff routing** | **Let my Genesys flow decide**, **Always use the default queue** or **Prefer an agent**. | Let my Genesys flow decide |
| **Default queue** | Where handoffs go when nothing else picks a queue. Changing it here also makes it the fallback queue of the OpenCX flow, the same as choosing it beside **Routing** on the **Setup** tab. With your own flow, only the queue OpenCX passes in `opencx_queue_id` changes. | None |
| **Preferred agent** | The agent **Prefer an agent** adds to participant data. | None |
| **Smart routing** | Picks the queue with live agents who fit the session's skills and language. Works only with **Let my Genesys flow decide**: it can't be turned on while **Handoff routing** pins a queue or agent, and a queue or agent can't be pinned while it's on. | Off |
| **When no agents are on the queue** | **Hand off anyway**, **Keep with the AI**, **Offer a callback** or **Create a workitem**. See [When no agents are available](#when-no-agents-are-available). | Hand off anyway |
| **Tell the customer the expected wait** | Adds one line after the handoff with Genesys's estimate. See [Expected wait](#expected-wait). | Off |
| **Business hours** | A Genesys schedule group, or **Use OpenCX office hours**. See [Business hours](#business-hours). | OpenCX office hours |
| **Handoff summary note** | A note for the agent in the transcript. See [Handoff note](https://docs.open.cx/integrations/genesys/agent-view.md#handoff-note). | On |

## 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:

| Attribute | Value |
| - | - |
| `opencx_session_id` | OpenCX session ID |
| `opencx_inbox_url` | Link to the session |
| `opencx_queue_id` | The queue linked to the session's team, otherwise your default queue |
| `opencx_language` | The session's language |
| `opencx_summary` | The AI summary, possibly shortened at routing time |
| `opencx_skills`, `opencx_skill_ids` | The session's skills, with **Smart routing** |
| `opencx_preferred_agent_id` | With **Prefer an agent** |

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:

| Block | What it does |
| - | - |
| **Get Participant Data** | Reads `opencx_queue_id` into a variable. |
| **Decision** | Checks that a queue ID came through. |
| **Transfer to ACD** | Sends the conversation to that queue, or to a fallback queue. |

**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.

| Setting | What happens |
| - | - |
| **Hand off anyway** | The session waits in the queue. |
| **Keep with the AI** | The AI keeps answering, and an internal note explains why. |
| **Offer a callback** | As **Keep with the AI**, and the customer is offered a [callback](https://docs.open.cx/integrations/genesys/workflow-actions.md#callbacks) in their language. When they reply with a number, the AI books it through your AI-trigger workflow with **Create Genesys Callback**: the option stays unavailable until one is active. The offer comes once per session: a later handoff goes to the queue, and so does the session when Genesys refuses the callback. Native email and messaging sessions are kept with the AI without the offer. |
| **Create a workitem** | The session gets a [workitem](https://docs.open.cx/integrations/genesys/workitems.md) instead of a conversation. Native email and messaging sessions are already conversations, so they get the workitem and still move to the queue. Needs a **Worktype** under **Workitems** on the **Handoff** tab: the option stays unavailable until one is set. |

## 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](https://docs.open.cx/handoff/settings.md#outside-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:

| In Genesys | In OpenCX |
| - | - |
| Inside one of the group's open schedules | Within office hours |
| Inside a closed or holiday schedule, even within an open one | Outside office hours |
| Outside every open schedule | Outside office hours |
| An emergency group switched on | Outside office hours |

* 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](https://docs.open.cx/handoff/settings.md#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](https://docs.open.cx/integrations/genesys/troubleshooting-handoffs.md#health-shows-a-business-hours-warning).

## Related

> [card] [What the Genesys agent sees](https://docs.open.cx/integrations/genesys/agent-view.md)
>
> The handoff note, notes and context in the agent desktop.

> [card] [Sessions and sync](https://docs.open.cx/integrations/genesys/conversations.md)
>
> What changes each way once the conversation is open.

> [card] [Agents, queues and teams](https://docs.open.cx/integrations/genesys/directory.md)
>
> Link teams to queues so handoffs land in the right place.

> [card] [Fix handoffs and routing](https://docs.open.cx/integrations/genesys/troubleshooting-handoffs.md)
>
> Nothing in the queue, failed handoffs, warnings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.