AI-generated summary
Genesys Cloud provides comprehensive Messenger configuration capabilities that enable organizations to customize web and mobile messaging experiences across digital channels. Implementation requires appropriate CX licensing (CX 2, CX 3, CX 4, or Digital Add-on variants) and specific role-based permissions including Web Deployments configuration, Knowledge Base viewing rights, Co-browse permissions, and Supported Content management capabilities.
The configuration process involves accessing the Digital and Telephony menu to create a new Messenger configuration through a multi-step workflow. Initial setup requires defining build details with a unique name and description, then selecting digital channels to enable. Appearance customization includes color selection via embedded color picker or manual #HEX notation, positioning options with automatic right-to-left text detection, and alignment settings. Launcher configuration supports icon-only, text-only, or combined display modes with custom icon uploads (26×26 pixels recommended, maximum 100×100 pixels, 512 KB limit in JPG/PNG/SVG formats) and launcher text limited to per supported language.
Positioning adjusts automatically for right-to-left webpages with configurable side and bottom spacing in pixels. Language support enables selection of multiple supported languages with customizable text labels and default language designation. Brand logo configuration accepts JPG, PNG, or GIF formats up to 512 KB with automatic resizing for images exceeding 200×70 pixels. Session persistence controls whether Messenger maintains sessions across website subdomains, while homescreen configuration enables or disables access to Knowledge App and Co-browse features. Launcher visibility options include always visible (default), hidden, or hidden until triggered by business logic.
Messaging behavior customization includes displaying participant names and avatars with optional bot names and custom avatars (minimum 75×75 pixels), enabling conversation clearing for privacy, configuring disconnect notifications, supporting rich text formatting with Markdown syntax, auto-starting conversations upon window expansion, enabling customer attachments with refinable file types, and displaying typing indicators. Authentication configuration restricts sessions to authenticated users through OpenID Connect integration, with automatic PII storage for authenticated contacts. Button triggering occurs programmatically through SDK commands or Predictive Engagement Action Maps.
Knowledge Portal configuration allows selection of header background color, global background color, primary color, and optional header image upload. Administrators can enable customer feedback collection, select published knowledge bases, choose between compact or detailed category appearance, display top viewed articles, and customize scenario-specific labels. Co-browse functionality is available for web messaging with privacy controls including CSS masking for sensitive fields, read-only field restrictions, and pause sharing capabilities; however, Co-browse is not currently supported on Mobile Messenger.
Notification settings permit administrators to choose whether message content appears in offline user notifications, with options for single notifications without content or notifications containing full message details. Guest session duration can be set to predefined values or custom durations ranging from 15 minutes to 18 months, with a default of three days. Digital User Tracking Configuration enables customization of web tracking parameters, search tracking settings, and exclusion of IP addresses, URL Query Parameters, and URL fragments from tracking. Genesys recommends migrating from legacy Predictive Engagement tracking snippets to Messenger-specific settings for improved functionality.
The configuration process includes a Review section displaying summaries of all previous selections with options to edit and update content before publishing. Error or warning messages may appear and require revision before publication. Configuration must be published to create a version that can be assigned to Messenger deployments. Configuration management capabilities include creating new versions, cloning versions to draft status, previewing versions, duplicating configurations, and deleting configurations. The final step involves creating a Messenger deployment and assigning the configured Messenger configuration to it