> ## 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 replies, messages and calls troubleshooting

> Fix Genesys Cloud agent replies that do not reach the customer, refused inbox replies and templates, missing conversations, notes and call recordings.

Use this page when a reply, a message, a note or a call doesn't arrive where you expect it, on either side. Each entry gives the likely cause and the fix. For other problems, start at [Troubleshooting](https://docs.open.cx/integrations/genesys/troubleshooting.md).

### **Agent replies don't reach the customer**

Likely cause (WhatsApp's 24-hour window is the usual reason. The messaging connection may also have been changed in Genesys.): the channel refused the reply, or accepted it and failed it later (a number not on WhatsApp, a sending limit), or the messaging connection changed.

**Fix:** read the reason in `opencx_notes` or the session's internal note. The reply is marked failed in Genesys either way. For WhatsApp, send a template from OpenCX. Otherwise check **Health** and click **Repair**.

### **A late agent reply on WhatsApp didn't reach the customer**

Likely cause (WhatsApp only takes a template once 24 hours have passed since the customer's last message.): the customer's 24-hour window had closed. With **Re-open WhatsApp chats** set, the reply waits until the customer answers your template. It's dropped if they don't answer within 72 hours, if a newer reply replaced it, or if the session was erased. If WhatsApp refuses the send, it's tried again with the customer's next message, up to three times, and then the agent is told it wasn't sent.

**Fix:** read the line in `opencx_notes` or the session's internal note. If no template went out, check that **Re-open WhatsApp chats** has an approved template that needs no values, or send a template from OpenCX yourself. See [WhatsApp](https://docs.open.cx/integrations/genesys/whatsapp.md#settings).

### **The AI doesn't answer a WhatsApp conversation from Genesys**

Likely cause (Genesys only lets OpenCX send approved templates into an ongoing WhatsApp conversation.): the conversation reached a queue on your Genesys WhatsApp number. The session's internal note says so.

**Fix:** to let the AI answer, add it to your WhatsApp inbound flow with [native messaging](https://docs.open.cx/integrations/genesys/native-messaging.md), so it replies before the queue. In the queue, your agents answer; turn on assist mode for drafts. See [WhatsApp](https://docs.open.cx/integrations/genesys/whatsapp.md#your-number-in-genesys).

### **A reply from the inbox is refused or not sent**

Likely cause (OpenCX replies in a Genesys conversation the way the AI does, and only while nobody holds it in Genesys.): an agent accepted the conversation in Genesys, the session is on SMS or another messenger that can't take a reply in an ongoing conversation (or Genesys never said which messenger it is), or the session was imported from past conversations. WhatsApp takes only templates: use **Send template**.

**Fix:** reply in Genesys. If the agent hands the conversation back to the queue, replies from the inbox work again within about a minute. An internal note on the session says why a reply wasn't sent. A long reply Genesys refused part-way through gets a note with the part the customer didn't get.

### **A WhatsApp template from the inbox is refused, or none are listed**

Likely cause (Templates come from Genesys's own WhatsApp templates and go out through the conversation's WhatsApp number in Genesys.): an agent holds the conversation in Genesys, the role OpenCX uses can't read templates, the conversation's number isn't a WhatsApp number in Genesys, or Genesys refused the template (for example, it needs header or button values).

**Fix:** the error says which. Reply in Genesys while an agent holds the conversation. For an empty list or a read error, reconnect Genesys with an admin who holds `responses:response:view`, or add it to the role. New templates show up within five minutes. Send templates that need header or button values from Genesys.

### **A note says Genesys could not deliver a message**

Genesys reported that a message didn't reach the customer, and the note gives its reason. On WhatsApp this is usually a reply sent outside the 24-hour window, which needs a template. Send it again from Genesys once the reason is fixed.

### **The Genesys agent doesn't see a teammate's reply or the handoff note**

Likely cause (The copy goes in only after a handoff, on sessions OpenCX handed off to Genesys.): Genesys refused the copy, or **Handoff summary note** is off. A refused copy leaves an internal note on the session, and the customer still got the reply.

**Fix:** check the setting on the **Handoff** tab. If the internal note keeps appearing, check **Health** on the **Setup** tab and the **Request log** on the **Diagnostics** tab for the refusal.

### **A teammate's note doesn't reach the Genesys contact**

Likely cause (Genesys signs every external contact note with an agent.): the teammate isn't linked to a Genesys user, the session's contact isn't linked to an external contact, or **Share OpenCX context with Genesys** is off.

**Fix:** link the teammate on the **Directory** tab and check the setting. Notes written before the fix aren't sent again.

### **Typing doesn't show, or Health shows Typing indicators**

Likely cause (OpenCX turns typing on with its own messaging setting on its messaging connection in Genesys.): your own messaging setting is on OpenCX's messaging connection and has typing off, or the OpenCX role lacks the messaging setting permissions.

**Fix:** if **Health** says typing follows your own messaging setting, turn typing on in that setting in Genesys, or remove it from the connection and turn **Typing indicators** off and on again. If it says Genesys refused, reconnect with an admin who holds the messaging setting [permissions](https://docs.open.cx/integrations/genesys/permissions.md), or add them to the role, then turn the switch off and on. Typing shows only on the widget and WhatsApp, and the customer's typing only while a Genesys agent holds the conversation.

### **The Assist panel says "This conversation is not available to Assist."**

Likely cause (The panel shows only sessions from your connected OpenCX organization, to agents on the conversation.): the conversation didn't come from OpenCX, or the agent isn't on it.

**Fix:** open the panel from a handed-off conversation, as an agent on it.

### **Drafts don't appear in Agent Copilot**

Likely cause (Genesys lets OpenCX answer only a suggestion the copilot asks for.): **Drafts in Agent Copilot** is off, the copilot has no rule with the third-party action for that turn, or Genesys refused it. The Assist panel still shows the draft.

**Fix:** follow the steps in [Drafts in Agent Copilot](https://docs.open.cx/integrations/genesys/assist-panel.md#drafts-in-agent-copilot). If **Health** shows **Agent Copilot drafts**, reconnect with an admin who holds `conversation:suggestion:view` and `conversation:suggestion:edit`, or add them to the role OpenCX uses, and check that your Genesys plan includes Agent Copilot. OpenCX tries again a day after a refusal.

### **A Genesys conversation is missing from the inbox**

Likely cause (Conversations appear within seconds while live updates arrive, and within about a minute when they don't.): **Show every Genesys conversation** is off, the queue is left out on the **Directory** tab, or the conversation is waiting for the AI and appears once the AI takes it.

**Fix:** check both settings. If **Health** shows **Live updates** or **Every conversation** with a warning, OpenCX is catching up by itself:

* **Live updates from Genesys are not arriving**: sessions still appear, about a minute later. If it stays for more than half an hour, check the connection status and reconnect if asked.
* **Some queues are checked every minute instead of live**: you have more queues than one live connection carries, or Genesys refused live updates for some of them. Their sessions appear about a minute later.
* **Some sessions are waiting for their latest messages from Genesys**: Genesys is busy, and those sessions catch up when it allows.
* **Many conversations were found by the minute check instead of live updates**: live updates are missing some conversations. Nothing is lost; contact support if it stays.
* **Genesys conversations are not being checked for what live updates missed** (an error): contact support.

### **A call has no transcript or recording**

Likely cause (Genesys produces both after the call ends: OpenCX keeps looking for the recording for 24 hours and the transcript for 6.): Genesys hasn't finished them yet, the queue isn't recorded or transcribed in Genesys, or the role lacks `recording:recording:view` (recordings) or `speechAndTextAnalytics:data:view` with a speech analytics licence (transcripts).

**Fix:** wait a few hours after the call. If **Health** shows **Call recordings** with a warning, add `recording:recording:view` to the role. For transcripts, add `speechAndTextAnalytics:data:view` and check the speech analytics licence. A call still open has no transcript until it ends, unless live assist transcribes it.

## Related

> [card] [Every Genesys conversation](https://docs.open.cx/integrations/genesys/every-conversation.md)
>
> How conversations come in and when you can reply.

> [card] [Channels](https://docs.open.cx/integrations/genesys/channels.md)
>
> How agent replies reach each channel.


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