Skip to main content
Customers can reach you on OpenCX channels, on Genesys Messenger, or both. This page says how each one works with Genesys Cloud and how your agents’ replies reach the customer. Choose where customers chat on the Channels tab: these can run together, and each session stays on the one it started on.

Agent replies

Agent replies on sessions that start in OpenCX: Quick-reply options become buttons on the widget, WhatsApp, Messenger and Instagram when there are at most three, each 20 characters or fewer. Otherwise, and on SMS and email, they show as a list under the message. The customer’s tap reaches the agent once, as the customer’s choice on that quick reply, or as the option’s text if Genesys refuses the choice.

Typing indicators

Turn on Typing indicators on the Channels tab, after you go live. With it on, typing shows both ways on sessions handed off to Genesys from OpenCX channels:
  • A Genesys agent types: the customer sees it. The widget shows the typing dots under the agent’s last message for a few seconds, until the reply arrives. WhatsApp shows its own typing indicator, which also marks the customer’s latest message as read.
  • The customer types in the widget: the Genesys agent who holds the conversation sees it. Nothing is sent while the AI or a queue has the session.
Typing never adds a message, opens a session, or counts toward unread, SLAs or reports. SMS, email, Messenger and Instagram show no typing. OpenCX turns typing on for its own messaging connection in Genesys with a setting named OpenCX typing indicators. If you put your own messaging setting on that connection, OpenCX leaves it in place and typing follows it, and Health says so. Turning the switch off turns OpenCX’s setting off, and disconnecting removes it. It needs the messaging setting permissions.

Flow messages

A message your flow sends on these sessions, such as a queue update or a survey question, reaches the customer the same way. It appears as a workflow message under the flow’s name, not as an agent’s reply: it doesn’t reopen a closed session, doesn’t count as a first reply in SLAs or reports, doesn’t run your agent reply or agent inactivity workflows, and doesn’t send the conversation.agent_response webhook. On API sessions, read it from the session history.

Channel pages

Native messaging

The AI answers messaging your Genesys flows route.

Native email

The AI answers or suggests replies on Genesys email.

Phone calls & live assist

Transcripts, suggestions and the AI on Genesys calls.

WhatsApp

WhatsApp conversations that run through Genesys.