Channels & engagement

Web messaging & Messenger

Persistent, asynchronous web and in-app messaging on Genesys Cloud CX, designed around your customer journeys and delivered by certified specialists.

Every channel, one conversation Six channel tiles are stacked on the left: voice, messaging, social, SMS, email and co-browse, each with a simple icon. Lines from every tile converge on a single point and a two-way arrow carries them into one large royal blue conversation bubble on the right, showing a customer and their message thread. A dashed arrow leaves the conversation and returns to the voice channel, representing proactive outbound engagement. ONE CONVERSATION Voice Messaging Social SMS Email Co-browse

In summary

Genesys Cloud web messaging lets customers start a conversation on your website or app and pick it up again whenever suits them. QVCCS designs and deploys Messenger configurations, authenticated messaging, bots-first journeys, rich messages and file attachments, and integrates the native iOS and Android Mobile Messenger SDK into your apps. Certified specialists from our own bench shape the routing, the bot hand-off and the agent experience, migrate you from retired web chat, then test, launch and support it within your chosen support model. The result is a persistent, asynchronous channel that recognises signed-in customers and gives agents the full history.

Who works on this

  • Solution Architect
  • Senior Business Consultant / Business Analyst
  • Senior Developer
  • Software Developer
  • Systems Integration Tester
  • User Acceptance Test Lead
  • Conversations that persistMessaging is asynchronous and persistent across sessions, so customers return to the same thread instead of starting again.
  • Know who you're talking toAuthenticated web messaging links signed-in customers to their identity, enabling secure, personalised service from the first message.
  • Bots first, people when neededBots answer common questions and collect details, then hand over to an agent with the full transcript and context.
  • Web and mobile appsOne Messenger experience on your website, with the native Mobile Messenger SDK for iOS and Android bringing it into your apps.
DiagramHow a Genesys Cloud web messaging solution fits together
  1. Customer touchpoints
    • Website Messenger
    • iOS app SDK
    • Android app SDK
  2. Messenger setup
    • Look and feel
    • Authentication
    • Knowledge portal
  3. Flows and bots
    • Message flow
    • Bot self-service
    • Data lookups
  4. Routing and agents
    • ACD queues
    • Agent workspace
    • Transcript history

QVCCS designs and builds every layer, from the widget your customers see to the agent desktop.

01

What Genesys Cloud web messaging offers your customers

Genesys Cloud web messaging replaces the old session-based web chat model with something closer to the messaging apps customers use every day, and it is now the only route forward: Genesys ended support for ACD Web Chat v2 and its chat widgets on 11 June 2025. A conversation does not end when the browser tab closes. Customers can send a question, leave, and come back later to find the reply waiting, with the history intact. For the contact centre, agents can handle several conversations concurrently, peaks are absorbed more gracefully, and customers no longer abandon because they could not wait at their desk. QVCCS helps you decide which journeys should move first.

Messaging also raises expectations. Customers who can message at any time expect sensible responses at any time, which makes bots, opening-hours messaging and clear expectations of reply times part of the design rather than optional extras. They also expect to be recognised if they are signed in, to share photos or documents, and to get rich responses such as buttons and quick replies rather than walls of text. Our consultants work with your digital, brand and service teams to define the experience, tone and service levels, and to make sure what customers see in the widget matches what your contact centre can deliver.

02

How Messenger and web messaging work

Customers interact through Messenger, the Genesys launcher and message window on your website. Its appearance and behaviour are set in a Messenger configuration, which is published through a Messenger deployment and added to your site with a snippet; the Messenger JavaScript SDK and public APIs support deeper customisation. The same configuration can enable the knowledge portal, giving customers self-service articles alongside the option to message, and the same deployment provides digital user tracking and co-browse. For apps, the Mobile Messenger SDK embeds a ready-made Messenger in native iOS and Android apps, with push notifications through Apple and Firebase services, while a transport SDK suits teams building their own interface. Each deployment points to an Architect inbound message flow, where routing, bots and data lookups are defined.

Messaging is asynchronous and persistent: messages thread into one conversation until a configurable threading timeline, 72 hours by default, has passed since the last disconnect. Authenticated web messaging lets your website pass a verified identity when a signed-in customer starts a conversation, enabling personalised journeys, continuity across devices and secure handling of account queries; step-up authentication can be requested mid-conversation. Conversations carry image and file attachments, governed by supported content profiles, and rich content such as quick replies, cards and carousels. Feature support differs between web and mobile, so we check the Genesys comparison matrix for every journey. Conversations route to ACD queues like any other interaction, and agents see the transcript, customer details and anything a bot collected.

Messaging works when the conversation belongs to the customer, not the session – it should be there whenever they come back.

QVCCS point of view

03

Getting the design right: identity, bots and capacity

Authentication is usually the most important design decision. Anonymous messaging is quick to launch, but authenticated messaging unlocks secure self-service and continuity across devices. QVCCS works with your identity and web teams to design the authentication flow, decide which pages and app screens offer which mode, and define what happens when a guest later signs in. We document how identity is passed, validated and used in routing, and we agree data handling with your security team, including attachment rules and what personal information may appear in transcripts.

Bots-first design needs restraint. A bot that tries to do everything frustrates customers; one that answers the top questions well and hands over cleanly earns trust. We design bot scope around real contact reasons, write concise responses, and define the hand-off so the agent receives the transcript and every captured detail. Capacity design matters too: messaging changes how agents work, so we help you set concurrency, utilisation and response-time targets, and design out-of-hours behaviour that tells customers clearly when to expect a reply rather than leaving them waiting in silence.

Brand and accessibility belong in the build, not in a final review. Our Software Developers configure Messenger to match your visual identity, check contrast and keyboard behaviour, and plan how the launcher behaves on different pages and devices. For organisations still on legacy web chat, migration is no longer optional, so we plan it page by page: retiring chat widgets, moving any proactive chat offers to web messaging offers, keeping reporting continuous and training agents before each switch. Customers are never offered two competing widgets, and every migrated page is regression tested against the original journey before the old code is removed.

04

How the QVCCS squad designs and deploys messaging

Web and in-app messaging spans your website, your apps, identity, bots and the contact centre, so QVCCS musters a team from its own bench and takes collective responsibility for the result. A Solution Architect owns the HLD and the authentication pattern, specified in an Interface Control Document for the handshake with your identity provider. A Senior Business Consultant / Business Analyst runs discovery on journeys, contact reasons, staffing and accessibility. A Senior Developer builds the inbound message flows, bots and data actions, and a Software Developer works alongside your web and app teams on the Messenger deployment and the iOS and Android SDK integration. A Systems Integration Tester proves guest and authenticated starts, returning customers and expired tokens on real devices.

Messaging changes the agent's day more than most channels. Conversations pause and resume, a customer may reply hours later, and one agent may hold several conversations at once. We design how returning conversations are routed – back to the same agent where that helps, or to the queue where speed matters more – how long an idle conversation stays with an agent, and what supervisors see when demand builds. Agents rehearse these patterns in UAT before launch, because a channel that looks simple in a demonstration can feel very different with three conversations open at once. Launch is phased by page or app screen, so staffing and routing are tuned on real traffic before the channel is offered everywhere.

05

Running, measuring and growing messaging

Messaging improves with attention. Genesys releases Messenger and SDK changes frequently, including minimum operating system updates for mobile, so every release goes through our release readiness review and an impact assessment for your apps, and your app teams know in advance when an SDK update is needed. We review conversation data with you to refine bot content, routing and concurrency, and to spot journeys that could move to messaging. Support follows your Genesys Cloud CX support model, alongside your provider or under SLA with us, with monitoring that can detect deployment, flow or integration failures. As your estate grows, the flows can be extended to other messaging channels and to virtual agents and agent assist.

What you get from QVCCS

  • Messaging channel strategy, BRD and prioritised journey roadmap
  • Messenger configuration and deployment LLD matched to your brand
  • Authenticated messaging ICD agreed with identity and security teams
  • Inbound message flows with bot self-service and clean agent hand-off
  • iOS and Android Mobile Messenger SDK integration with your app teams
  • Web chat migration plan covering widgets, offers and reporting
  • SIT pack, UAT scripts, handover pack and support aligned to your model

Genesys documentation references

Checked against current official documentation, October 2026. Genesys releases weekly, so we re-validate every design against the live release notes.

  1. Web messaging overviewhelp.genesys.cloud
  2. Deprecation: Removal of ACD Web Chat (version 2)help.genesys.cloud
  3. Mobile Messenger overviewhelp.genesys.cloud
  4. Mobile Messenger feature comparison matrixhelp.genesys.cloud
  5. Authenticated web messaging overviewhelp.genesys.cloud
  6. Messaging threading timelinehelp.genesys.cloud
  7. Knowledge portal overviewhelp.genesys.cloud

Methods & templates

Web messaging & Messenger: quality gates, stage by stage

Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For Web messaging & Messenger, the work concentrates in Discover, Define, Design, Build, Prove and Transition, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.

  1. 01DiscoverDiscovery sign-off
  2. 02DefineRequirements baseline
  3. 03DesignDesign authority review
  4. 04BuildBuild complete
  5. 05ProveGo / no-go readiness
  6. 06TransitionOperational acceptance
  7. 07Run & evolveService reviews
  • 1 · Discover

    Current-state journey mapping

    Maps where customers seek help on your site and apps today, including any legacy web chat, to prioritise journeys for messaging.

  • 2 · Define

    Business Requirements Document (BRD)

    Agrees guest versus authenticated use, bot scope, reply-time expectations, attachment rules and out-of-hours behaviour with business owners.

  • 3 · Design

    Interface Control Document (ICD)

    Specifies the authenticated messaging handshake with your identity provider and every data lookup the message flow makes.

  • 4 · Build

    Configuration-as-code with CX as Code and Archy

    Keeps Messenger, flows and routing in version control so changes are peer reviewed and promoted consistently between orgs.

  • 5 · Prove

    SIT test pack

    Proves guest and authenticated starts, returning customers, attachments, rich content, bot hand-off and routing on real browsers and devices.

  • 6 · Transition

    Cut-over plan and runbook

    Moves pages and app releases from legacy chat to Messenger in planned steps with rollback, training and hypercare.

See the full QVCCS delivery method

How we deliver

Web messaging & Messenger: your engagement at a glance

  1. 01DiscoverWorkshops on journeys, contact reasons, identity, brand, accessibility and staffing to shape the messaging experience.
  2. 02DesignHLD, LLD and ICDs for Messenger, deployments, message flows, bots, routing and authentication, approved by design authority.
  3. 03BuildCertified developers configure Messenger, build flows and bots, and support SDK integration with your app teams.
  4. 04Test & launchSIT traced to the RTM, negative tests and UAT with agents, then a phased launch on selected pages or apps.
  5. 05Support & growSupport aligned to your provider model, with regular reviews that refine bots and routing and add channels over time.

The specialists on this work, from our own bench

  • Solution Architect
  • Senior Business Consultant / Business Analyst
  • Senior Developer
  • Software Developer
  • Systems Integration Tester
  • User Acceptance Test Lead

Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →

Questions

Web messaging & Messenger: common questions

What is the difference between web chat and web messaging in Genesys Cloud?

Web chat was tied to a single session, so the conversation ended when the customer left. Web messaging is asynchronous and persistent, so customers return to the same conversation later. Genesys ended support for ACD Web Chat v2 and its chat widgets on 11 June 2025, so remaining chat users need to migrate.

How do you set up web messaging in Genesys Cloud?

You create a Messenger configuration, publish it through a deployment linked to an Architect inbound message flow, and add the deployment snippet to your website. Because the snippet sits in your site's code, your web team and the contact centre agree together which pages carry it and how it is released.

Can Genesys Cloud messaging recognise logged-in customers?

Yes. Authenticated web messaging is supported, allowing your site to pass a verified identity when a signed-in customer starts a conversation. QVCCS designs the authentication flow with your identity team and uses that identity to personalise routing, self-service and the agent's view of the customer.

Can we add Genesys Cloud messaging to our mobile app?

Yes. The Mobile Messenger SDK embeds a ready-made messaging experience in native iOS and Android apps, with push notifications for offline users, and a transport SDK is available for fully custom interfaces. Our developers work with your app teams on integration, authentication and testing on real devices, and check feature parity with your website for each journey. We built our own native iPhone app, QVCCS Verified Mobile, on the transport SDK to prove the approach; our Innovation article describes it.

Last reviewed

Talk to a specialist about this

We work by introduction. Clients, partners and people introduced to us can reach the right specialist for this topic directly.

Who to contact