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

# What the Genesys Cloud agent sees from OpenCX

> Where a Genesys Cloud agent finds the OpenCX summary, notes, handoff note, teammate replies and wrap-up suggestions, and the context OpenCX writes for flows.

Participant data doesn't show in the Genesys Cloud agent desktop by itself. This page says where the agent finds what OpenCX knows about a session, and which `opencx_` keys your flows and reports can read. Read it when you prepare agents for the first handoffs.

| Where | What |
| - | - |
| **Conversation Details** in the interaction | **OpenCX notes**, **OpenCX summary** and **OpenCX session** (a link to the session), updated with `opencx_notes`, `opencx_summary` and the session link. Agents need the **Agent UI › Conversation Details › View** permission in Genesys Cloud. |
| The [Assist panel](https://docs.open.cx/integrations/genesys/assist-panel.md) | The summary, the contact and the session's internal notes. |
| The transcript | The [handoff note](#handoff-note): why the AI handed off, the summary and a link, on sessions handed off from OpenCX channels. |
| The external contact's notes | A teammate's internal notes, with **Share OpenCX context with Genesys** on. See [Contacts and companies](https://docs.open.cx/integrations/genesys/contacts.md#contacts-and-companies). |

A session with only a [workitem](https://docs.open.cx/integrations/genesys/workitems.md#what-the-workitem-holds) and no conversation shows less: see the workitem page.

## Handoff note

With **Handoff summary note** on (the default, on the **Handoff** tab), the agent also finds a note in the conversation's transcript: who handed off and why, the summary, the session's language and sentiment, and a link to the session in OpenCX. It's for the agent only: the customer never gets it. If Genesys refuses it, the handoff still goes through, and the session gets an internal note saying so (at most one a day). Native email and native messaging hand off inside Genesys, so they have no note, only the participant data.

## Teammate replies

When a teammate replies from the OpenCX inbox after the handoff, the customer gets it on their own channel at once, as usual. A copy also goes into the Genesys conversation's transcript under the teammate's name, such as `Maya Haddad (OpenCX): …`, so the Genesys agent sees what the customer was told, even while they hold the conversation. The customer gets the reply once, never again from Genesys. Long replies go in parts, split between paragraphs, and lists and links stay readable. If Genesys refuses the copy, the reply still reached the customer, and the session gets an internal note saying so (at most one a day). The Genesys agent's own replies are never copied back.

## Wrap-up code suggestions

**Wrap-up code suggestions** on the **Handoff** tab is **Off**, **Suggest** or **Pre-fill when sure** (off by default). With **Suggest**, the AI writes up to three codes from the conversation's queue to `opencx_wrapup_suggestions`. **Pre-fill when sure** also pre-selects the top code when the AI is at least 80% sure and the queue makes wrap-up mandatory. A code the agent chose is never replaced, and the agent always has the final say.

## OpenCX context for agents, flows and reports

With **Share OpenCX context with Genesys** on (the default, on the **Handoff** tab), OpenCX writes what it knows about the session onto the customer participant of the Genesys conversation. Architect flows read it with **Get Participant Data**, and it travels with the conversation into Genesys analytics. Every key starts with `opencx_`, apart from the **Conversation Details** copies above, each event is one update, and keys your flows or agents set are never changed. Turning it off stops everything in this section. The participant data in [How handoff works](https://docs.open.cx/integrations/genesys/handoff.md#how-handoff-works), `opencx_transcript` included, is part of every handoff and is written either way.

| When | Participant data |
| - | - |
| The AI hands off | `opencx_summary` (the whole summary, as plain text), `opencx_intent` (the session's contact reason), `opencx_language`, `opencx_sentiment` (`angry`, `neutral` or `happy`), `opencx_handoff_reason` (why the AI handed off, comma-separated, such as `user_requested_human_assistance`), `opencx_session_url` (the session in OpenCX). A value OpenCX doesn't have is left out. |
| OpenCX closes the session | `opencx_outcome`: `resolved_by_ai`, `unresolved_by_ai`, `handed_off` (nobody held it) or `closed_by_agent` (a person held it, the session was never the AI's, such as a call, or a teammate, a workflow or the API closed the AI's session). `opencx_ai_replies`: how many replies the AI sent the customer. Written just before OpenCX ends the conversation. |
| OpenCX first sees the conversation (every conversation, native email and native messaging) | `opencx_open_sessions`: the customer's other open sessions, as `<channel>:<session ID>`, comma-separated, newest first, up to 10. `opencx_contacts_7d`: how many other sessions the customer started in the last 7 days. `opencx_last_agent_id`: the Genesys user ID of the agent who last handled one of the customer's sessions, for preferred-agent routing. Nothing is written for a first-time customer. |
| A mirrored email waits in a queue | `opencx_intent`, `opencx_language` and `opencx_priority`, when the session has them. See [Email routing](#email-routing). |

A conversation that ends in Genesys first doesn't get `opencx_outcome`, because Genesys takes no participant data once a conversation has ended.

### Email routing

For an email shown under [every Genesys conversation](https://docs.open.cx/integrations/genesys/every-conversation.md) that waits in a queue with no agent yet, OpenCX also asks Genesys to route it by what the session holds, set by your workflows, a teammate or the AI:

* **Priority**: the session's priority (none 0, low 10, medium 20, high 30, urgent 40), only when it's higher than the email's own.
* **Language**: the Genesys routing language matching the session's language, when your Genesys has one. Otherwise the language is only in participant data.
* **Skills**: session skills linked to Genesys skills, added to the skills the email already asks for.

Only changes are sent, and no extra AI step runs for it. It needs `routing:conversation:edit`, which the OpenCX role has. If Genesys refuses, **Health** shows **Email routing** with a warning, OpenCX stops asking for a day, and the participant data still lands.

## Related

> [card] [Assist panel](https://docs.open.cx/integrations/genesys/assist-panel.md)
>
> The AI's draft beside the interaction, with a live preview.

> [card] [Sessions and sync](https://docs.open.cx/integrations/genesys/conversations.md)
>
> Every change that reaches Genesys, key by key.


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