TrueEngage enhanced web messaging is Genesys Cloud web messaging inside a chat widget the contact centre can design itself, with the other contact options placed around it. Every conversation still routes to a Genesys Messenger deployment, so bot flows, quick replies, carousels, routing, recording and reporting work exactly as they do today. On top of that, the widget adds forms, transcript export, WhatsApp and Messenger, wait-time rules and a one-click move to voice or video.
Genesys Cloud web messaging is the asynchronous chat channel of Genesys Cloud. A Messenger deployment, configured by a Genesys Cloud admin, decides which inbound message flow a conversation enters, and from there architect flows, bots and queues take over. The visitor-facing part is the chat window on the website.
TrueEngage enhanced web messaging is a chat widget for the website that connects to that same Messenger deployment. A Genesys Cloud admin installs TrueEngage from the Genesys AppFoundry, picks the Messenger deployment in the TrueEngage panel, and the widget sends every conversation there. The panel is where a business user sets the design, the texts, the forms and the other channels that sit next to chat in the same widget: WhatsApp, Facebook Messenger, a web call, a video call, a callback request and a contact form.
Everything that happens after the visitor presses send. The conversation enters the Messenger deployment chosen in the panel, so the inbound message flow, bot flows, quick replies, carousels, agent handover and conversation history work as the Genesys Cloud admin has configured them. The agent answers in the Genesys Cloud agent desktop, in the queue the flow selected. Recording, quality management and reporting read the interaction as a standard Genesys Cloud web messaging interaction.
For the Genesys Cloud admin. Nothing in the existing flows has to be rebuilt. The admin chooses which Messenger deployment the widget uses and, optionally, adds a step that waits for a form event when in-interaction forms are wanted. Everything else in the architect configuration stays as it is.
The other channels in the widget also end in standard Genesys Cloud objects: a callback in a queue, a web call in a call flow. The contact centre keeps one place to route, record and report.
Pre-interaction forms collect what the agent needs before the conversation starts: name, phone, email, topic, consents and custom fields, set per channel. The answers are passed into Genesys Cloud as participant data, so an architect flow can route on them, and the agent sees them in the TrueEngage Agent App. In-interaction forms appear while the chat is running, for a step where the conversation needs structured input, such as an order number or a policy reference. A bot flow waiting for the form event picks up the answer and continues.
The visitor can export the transcript and keep the conversation. Emoji, notification sounds and unread badges make a reply noticeable when the visitor has switched to another tab, which matters on an asynchronous channel where replies can arrive minutes later.
WhatsApp and Facebook Messenger appear as options next to web messaging, or in its place. WhatsApp uses the number assigned in Genesys Cloud, and Messenger uses the Genesys Cloud Facebook integration. The first message is tagged so that Genesys Cloud can route it like any other message. For a visitor who would rather continue on the phone in their pocket, the conversation moves to an app they already use.
The same widget can offer a web call from the browser, a video call, an immediate or scheduled callback request, and a contact form for questions that do not need a live answer. Each one is switched on per widget, so a page can show a single channel or all of them.
When typing stops working, the agent offers an upgrade to voice or video from the TrueEngage Agent App. The visitor accepts in the widget, the call starts in the browser with no download, and the chat stays open next to it. The same agent continues with the history on screen, and the customer does not repeat the problem. The upgraded leg is recorded in Genesys Cloud and linked by ID to the chat it came from.
The agent works in the Genesys Cloud agent desktop, with the TrueEngage Agent App as an interaction widget beside the conversation. The Agent App shows the page the visitor is on and the pages they visited, earlier interactions, location and device, and the answers from the pre-interaction form. The upgrade to voice or video, screen sharing and the move from a phone call to video are controlled from the same place, so the agent does not switch tools.
Agent avatars and names show in the widget when the Genesys Cloud setting "Humanize your conversation" is switched on for the Messenger deployment. The avatar configuration guide shows where the setting sits.
The TrueEngage panel is built for the marketing, digital or CX team that owns the website. Once the widget is on the site, these settings change from the panel:
One script serves every widget in the account, so a new widget for a campaign landing page or a separate brand is a change in the panel, with no new code on the website.
TrueEngage reads wait times from Genesys Cloud every 30 seconds. Each channel can carry its own threshold. When the expected wait for live chat passes the threshold, the widget hides the chat option and the visitor chooses from what remains: WhatsApp or Messenger, where a reply can arrive later without the visitor watching a window; a scheduled callback; or a contact form. For callbacks the rule works the same way. Above the threshold, the immediate callback is withdrawn and only scheduled slots, taken from a Genesys schedule group with capacity limits, are offered.
Peak handling in one widget. With a wait-time threshold on web messaging and WhatsApp or Messenger enabled, visitors move from the live channel to an asynchronous one when the queue is long. The visitor still gets an answer, and the contact centre spreads the load across channels and across time.
If every channel is closed or above its threshold, the widget does not appear at all, except for scheduled callback, which stays available so the visitor can still book a time. Owen Robinson's Black Friday customer service post walks through the same mechanics at the busiest week of the retail year.
A US travel group runs several brands and business units on one Genesys Cloud org, each with its own web designers and developers. It moved from a separate chat tool to enhanced Genesys Cloud web messaging. Each business unit has its own TrueEngage account under a parent account, so each brand's web team designs and publishes only its own widgets, while every conversation lands in the same Genesys Cloud environment.
A European insurer had several disconnected contact options across its website. It replaced them with a single contact hub integrated with Genesys Cloud, so a visitor finds chat, messaging apps and other options in one place, and the contact centre handles all of them in one system.
A global appliance brand upgrades messaging conversations to live video within the same interaction. When a customer describes a fault, the agent sees the device, which makes verification faster than an exchange of written descriptions.
A European hotel group with seasonal demand and limited specialist staff uses callback requests, wait-time indicators and alternative digital channels in the widget. The result on file is lower abandonment and more balanced workloads.
A Genesys Cloud admin installs TrueEngage from the Genesys AppFoundry. The install creates the Genesys Cloud objects it needs: a role, groups, an app instance, the interaction widget for the Agent App, OAuth clients and a BYOC Cloud trunk for voice and video. The installation guide lists each step and the permissions the admin needs.
The website team then adds one script before the closing body tag, or a Google Tag Manager custom HTML tag. The same script serves every widget in the account, and the targeting rules in the panel decide which widget appears on which page. The deployment guide covers both methods.
The TrueEngage reporting module, a set of ready-made reports in the panel, shows the website side of the contact options with no analytics set-up on the customer's side. The views that answer the question for web messaging are:
Interactions themselves are still reported natively in Genesys Cloud. For teams that work in Google Analytics 4, a Google Analytics integration add-on sends widget events and the Genesys Cloud outcome of each conversation to GA4, so web messaging sits in the same reports as the rest of the site.
Yes. TrueEngage enhanced web messaging routes every conversation to the Genesys Cloud Messenger deployment chosen in the TrueEngage panel. The inbound message flow, bot flows, quick replies, carousels, queues, recording and reporting are the ones the Genesys Cloud admin already configured. The widget changes what the visitor sees on the website and adds channels and forms around the chat.
Yes. One TrueEngage script serves every widget in an account, and each widget has its own design, texts, channels and targeting rules. Groups with several brands can also use a parent account with a separate TrueEngage account per brand, so each brand's web team works only on its own widgets while all conversations reach the same Genesys Cloud org.
No. The TrueEngage widget already runs in the browser, so the only prompt is the browser's request for camera and microphone permission. The agent offers the upgrade from the TrueEngage Agent App inside Genesys Cloud, the visitor accepts in the widget, and the chat stays open alongside the call with the same agent.
Yes, when both channels are in the widget. Give web messaging an expected-wait-time threshold and enable WhatsApp or Facebook Messenger. When the wait passes the threshold, TrueEngage hides live chat and the visitor continues on the asynchronous channel, which Genesys Cloud routes like any other message. Wait times are refreshed from Genesys Cloud every 30 seconds.