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

# Every Genesys Cloud conversation as an OpenCX session

> Show every Genesys Cloud email, message, call and callback as an OpenCX session: what comes in, when the AI answers, how it closes, and how to import history.

With **Show every Genesys conversation** on, the email, messaging, calls and callbacks your Genesys Cloud queues receive appear in OpenCX as sessions, while your agents keep working in Genesys. Turn it on to watch Genesys from the OpenCX inbox, report on it, and let the AI answer customers waiting in a queue.

Turn on **Show every Genesys conversation** on the **Channels** tab, after you go live. It's off by default. Every email, messaging conversation (WhatsApp, web messaging, SMS, Instagram, Messenger and other messengers), call and callback in your Genesys queues then appears as a session, usually within seconds.

> [!WARNING]
>
> The AI starts answering waiting customers as soon as you turn this on, so the switch asks you to confirm first. Check autopilot for each channel, and your workflows, before you do: they run on these sessions as on any other session, and a workflow message reaches waiting customers. A team that distributes sessions automatically would assign these too, so set teams linked to Genesys queues to manual assignment.

## How these sessions work

These sessions work like sessions on your other channels, and your agents keep working in Genesys:

* Customer, agent, flow and bot messages and files appear on the session as they're written, in the order they were written in Genesys. Messages the AI sent never appear twice. After you [redact a session](https://docs.open.cx/api-reference/redaction/redact-session.md), messages written before the erasure don't come back to it; new ones still appear.
* The queue sets the team, the agent who accepts it becomes the assignee (when the agent is linked), the wrap-up code sets the sub-status, and the session closes when the conversation ends in Genesys, with its last messages (or a note saying to open the conversation in Genesys if Genesys didn't share them).
* **The AI answers while the customer waits in a queue**, when autopilot is on for the channel: on email, web messaging and Open Messaging, in the customer's own conversation. Email needs the sender address set under [Native email](https://docs.open.cx/integrations/genesys/native-email.md), or replies sent from your support address. WhatsApp, SMS and other messengers can't take a reply in an ongoing conversation, so those sessions start with your agents. With autopilot off, a session starts with your agents, as on any channel. With assist mode on, the AI writes drafts for the agent.
* **An agent who accepts the conversation in Genesys owns it.** The AI stops, and a reply it was still writing isn't sent.
* **When the AI hands off**, the conversation stays in its queue for your agents: nothing is transferred and no workitem is created.
* **When the AI resolves the session**, OpenCX ends the conversation in Genesys, so no agent picks it up. If the customer writes again, a new conversation and a new session start.
* The AI's resolutions are billed, and its handoffs and resolutions count in your reports, as on any channel.
* **Assign to AI** works while no agent holds the conversation in Genesys. It's refused once one does.
* Workflow messages go out like the AI's while no agent holds the conversation, and are held back with a note once one does.
* **Closing the session in OpenCX** ends the conversation in Genesys when no agent holds it. With an agent on it, the conversation stays open for them, and the session gets an internal note saying so. If Genesys is unavailable at that moment, OpenCX ends the conversation once Genesys is back.
* **Assigning one of these sessions to a teammate** means they work it from OpenCX, so nothing changes in Genesys. Changing the team moves the conversation to the team's queue when the role holds the **Transfer** permission, and the session gets an internal note either way.
* Conversations waiting for the AI (native email or messaging) keep working as before.

## Replying from OpenCX

* **Your teammates can work these sessions from OpenCX.** While no agent holds the conversation in Genesys, a reply from the inbox goes into the customer's own conversation the way the AI's does, on email, web messaging and Open Messaging. Files go as links. It counts as the teammate's reply, as on any channel: the session becomes theirs, the AI stops answering, and it counts in reply times and reports. It's never added to the session a second time.
* **Once an agent accepts the conversation in Genesys**, the composer says to reply in Genesys, and a reply from the inbox is refused. A reply sent just as the agent accepted it isn't sent, and the session gets an internal note.
* **WhatsApp** takes only approved templates in an ongoing conversation, so the composer offers **Send template** instead of **Send**. Pick one of your WhatsApp templates in Genesys, fill in its values and check the preview, as with [your own WhatsApp templates](https://docs.open.cx/whatsapp/whatsapp-rules.md). Genesys sends it into the customer's conversation, the session shows it like any template, and the session becomes yours. It's refused while an agent holds the conversation in Genesys. Header and button values can't be filled in from OpenCX, so send templates that need them from Genesys.
* **SMS and other messengers** can't take a reply in an ongoing conversation, so the composer says to reply in Genesys.

## Leave queues out

To leave queues out, such as sales or partner support, switch them off in the **Queues** list on the **Directory** tab. Their conversations never appear. A conversation that moves into a left-out queue after it appeared is followed until it ends.

Conversations that are open when you turn this on appear within about two minutes. Conversations that ended earlier come in with [Import past conversations](#import-past-conversations).

## Calls and callbacks

Calls and callbacks in the same queues appear as phone sessions, whether or not live assist is on and whether or not Genesys transcribes the queue:

* A call appears when an agent answers it, with the caller's number on the contact, the queue's team, the agent as assignee (when linked) and its timeline. A call or callback the minute check finds first appears at once, even while it waits.
* When the call ends, the session closes, and Genesys's recording, its transcript (with a speech analytics licence) and the agent's wrap-up code and notes come in over the next minutes to hours, as for [calls with live assist](https://docs.open.cx/integrations/genesys/voice.md). A call that ended before OpenCX saw it, including one the caller abandoned in the queue, comes in closed at its own times, and its recording, transcript and wrap-up follow the same way. Like past conversations, it isn't counted in AI handoff and resolution reports.
* Closing a call's session in OpenCX never hangs up the call. It stays live in Genesys until the caller or the agent ends it.
* These are your agents' sessions. The AI never answers or joins them, they're never billed as AI resolutions, and they count in your reports like any call your team takes.
* With live assist on a transcribed queue, the transcript also appears live and agents get suggestions, as before.

Calls in left-out queues never appear. **Import past conversations** still covers messaging and email only.

If live updates from Genesys pause, for example while Genesys is unreachable, OpenCX checks your queues every minute and brings in what it missed, once. **Health** on the **Setup** tab shows **Live updates** and **Every conversation** when either needs attention. See [Troubleshooting](https://docs.open.cx/integrations/genesys/troubleshooting-replies.md#a-genesys-conversation-is-missing-from-the-inbox).

## Import past conversations

To bring past messaging and email into the inbox, open the **Import from Genesys** section of the **Connection** tab and press **Import** beside **Past conversations**. It covers the last 90 days and creates closed sessions on their real channels.

* Messages a flow, bot or auto-reply sent come in as workflow messages, never as an agent's reply.
* Nothing is sent to customers, no AI or workflow runs, and nothing is billed. Sessions keep the times their messages were written, so they don't jump to the top of the inbox or change your reply-time reports, and they never count as AI handoffs.
* Participant data on emails, calls and messaging still open comes in as session attributes of the same names, and an email, SMS or WhatsApp conversation joins the contact linked to its external contact.
* Importing again skips what's already there. A large history imports in parts and carries on by itself about once a minute, waiting whenever Genesys is busy so live conversations come first. A conversation that fails for a passing reason is tried again at the end. **Resume** only matters after an import stopped on an error, such as a missing permission.
* Each imported session also shows its timeline of queues, agents and wrap-up.

Ended messaging conversations come from the transcripts Genesys keeps with its recordings, so the import needs `recording:recording:view` on the role OpenCX uses. Without it, emails still import, messaging is skipped, and the import ends asking for the permission: add it, then press **Resume** to bring the messaging in. Conversations with nothing to bring over, such as an email with no sender address or a conversation Genesys kept no transcript of, are skipped, not failed.

To import one conversation in a workflow, set **Genesys Conversation ID** on the **Create Ticket** action. A live messaging conversation stays open and keeps syncing. An email or a call still open is refused until it ends. An ended call comes in as a closed phone session, and its recording, transcript and wrap-up follow.

## Related

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

> [card] [Fix replies, messages and calls](https://docs.open.cx/integrations/genesys/troubleshooting-replies.md)
>
> A conversation doesn't appear, a reply is refused.


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