Skip to main content
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. A session with only a workitem 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, opencx_transcript included, is part of every handoff and is written either way. 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 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.

Assist panel

The AI’s draft beside the interaction, with a live preview.

Sessions and sync

Every change that reaches Genesys, key by key.