Enhanced web messaging is Genesys Cloud web messaging with a customisable design and the other contact options around it in one widget. The chat still routes to a Genesys Messenger deployment, so bot flows, quick replies and carousels work as they do today. This post lists what the widget adds and what a business user controls without a developer.
Routing. The widget sends the conversation to the Genesys Messenger deployment chosen in the TrueEngage panel. Every native web messaging feature remains: quick replies, carousels, bot flows, agent handover, history. The agent works the conversation in Genesys Cloud; reporting and recording are native.
Design: header, colours including gradients, logo, avatars, fonts, corner radius and position on the page. Texts in every state. Which channels show, and a single-channel view when one option is enough. Transcript on or off. Per channel, a schedule group that hides the option outside hours and an expected-wait-time threshold that hides it under load.
Peak handling. With a wait-time threshold on web messaging and WhatsApp or Messenger enabled, the widget shifts visitors from the live channel to the asynchronous one when the queue is long. The visitor still gets an answer; the contact centre spreads the load.
One script before the closing body tag, or a Google Tag Manager custom HTML tag. One script serves every widget in the account; which widget shows on which page is decided by targeting rules in the panel: URL rules including regular expressions, country, device, UTM parameters and referrer, with a priority order when several match.
Yes, when the Genesys Cloud setting "Humanize your conversation" is on for the Messenger deployment.
Yes. The Genesys knowledge base can be exposed as a tab in the widget alongside the contact options.
WhatsApp and Messenger are website channels. Mobile and kiosk touchpoints carry voice, video and messaging.