Channels & engagement
WhatsApp, Apple Messages & social messaging
Meet customers on WhatsApp, Apple Messages and social platforms, with every channel connected, routed and supported by certified Genesys Cloud specialists.
Genesys Cloud WhatsApp and social messaging let you serve customers in the apps they already use, with every conversation routed and reported like any other interaction. QVCCS connects WhatsApp, Apple Messages for Business, Facebook Messenger, Instagram and X direct messages to Genesys Cloud CX, brings public posts in through Social Listening, and uses open messaging to add custom channels through an API. Certified specialists from our own bench plan onboarding, designs flows, bots and routing, builds the integrations, tests every channel on real devices and supports them within your chosen support model, so agents work one queue wherever conversations start.
- Solution Architect
- Senior Business Consultant / Business Analyst
- Senior Developer
- Software Developer
- Systems Integration Tester
- WhatsApp done properlyWhatsApp Embedded Signup inside Genesys Cloud, opt-in and template rules designed in, and routing that brings each conversation to the right agent.
- Every major social inboxFacebook Messenger, Instagram Direct Messages and X Direct Messaging brought into Genesys Cloud alongside your other channels.
- One queue, one desktopThird-party messages are routed like any other interaction, so agents handle them in the same workspace with the same tools.
- Open messaging for the restOur developers connect custom or additional channels through the open messaging API, from regional apps to in-house platforms.
- WhatsAppBusiness messaging
- Apple MessagesMessages on Apple devices
- Facebook MessengerPage conversations
- Instagram DMsDirect messages
- X Direct MessagesFormerly Twitter
- Social ListeningPublic posts to agents
- Open messagingCustom channels via API
QVCCS connects each channel, then designs one routing and agent experience across them all.
01
Why Genesys Cloud WhatsApp and social messaging matter
Genesys Cloud WhatsApp and social messaging channels let customers contact you from the apps already on their phones, without downloading anything or finding a phone number. For many customers, particularly in markets where WhatsApp is the default way to communicate, a business that cannot be messaged there feels hard to reach. Social direct messages carry a similar expectation: a customer who messages your brand on Instagram or Facebook wants an answer there, not an instruction to call. QVCCS helps you decide which channels matter for your customer base, in which regions, and for which journeys, so you invest where demand really exists.
Adding channels is easy to get wrong. If each one is handled in a separate tool by a separate team, customers get inconsistent answers, managers lose sight of volumes, and agents switch screens constantly. The value comes from treating every channel as part of one contact centre: shared routing, shared standards and shared reporting. Our consultants define a channel strategy that covers service hours, response expectations, tone of voice, escalation and compliance for each platform, so customers receive the same quality of service whether they start on WhatsApp, Apple Messages or a social inbox.
02
How third-party messaging works on Genesys Cloud CX
Genesys Cloud third-party messaging natively supports WhatsApp, Facebook Messenger, Instagram Direct Messaging, X Direct Messaging and Social Listening, and Apple Messages for Business is configured through its own ACD integration. Each channel is linked to a messaging app or business account created with the platform owner, and an organisation can configure more than one integration per platform, which suits multi-brand estates. WhatsApp onboarding runs through the Embedded Signup Flow inside Genesys Cloud, using a Meta business portfolio owned by the brand itself. Incoming messages are directed to Architect inbound message flows, where bots, data lookups and routing apply, then reach ACD queues and agents with the same skills, priorities, wrap-up codes and reporting as every other interaction.
Open messaging covers the rest. It is a lightweight API with webhooks: your middleware posts inbound messages to Genesys Cloud and receives agent replies on an outbound webhook secured with a token, so a regional app, a proprietary portal or an in-house system joins the same contact centre. Genesys Social Listening goes beyond private messages, using data ingestion rules to bring public posts from Facebook, Instagram, X and Google Business Profile to agents for a response; it requires the Genesys Cloud AI Experience licence. Each platform also sets its own rules. WhatsApp, for example, requires customer opt-in before a business opens a conversation outside the 24-hour window, using approved template messages. QVCCS designs flows and outbound use to respect those rules from the outset.
WhatsApp charging changed on 1 October 2026. Meta now charges per delivered message for service messages, the replies a business sends within the 24-hour customer service window, and for utility messages sent inside that window, both of which had been free; businesses without a payment method set up stop having service messages delivered. Genesys passes Meta's charges through with no markup, alongside its own WhatsApp component, measured in Genesys Cloud Experience Units at 400 inbound or outbound messages per token. For high-volume WhatsApp service, that makes message design and bot containment a cost question as well as an experience one, and we model both before go-live.
Customers choose the app; your contact centre should simply be there, with one standard of service whichever channel they start in.
03
Design choices across WhatsApp, Apple and social
Onboarding is the first hurdle. Business verification, display names, numbers, brand assets and approvals all sit with the platform owner and can take time; Apple Messages for Business also needs an Apple business account and agreed entry points that decide how customers start a conversation. QVCCS records these dependencies in the RAID log, prepares the information each platform needs, and sequences them so that build is never waiting on paperwork. We decide whether to reuse existing WhatsApp numbers or social pages, how many accounts or brands to connect, and how each maps to queues and divisions in Genesys Cloud, so ownership and access are clear from the start.
Each channel then needs the right conversation design. Customers expect speed and brevity in messaging apps, so bots should be focused and hand-offs clean. Some content types and interactive elements behave differently from one platform to another, so we design for what each channel supports rather than assuming the same message renders everywhere. We also plan identity: how a WhatsApp number or social handle is matched to a customer record, when a customer is asked to verify, and what an agent may discuss before identity is confirmed. These rules are agreed with your security and compliance teams.
Operational design is just as important. Social channels can bring sudden spikes after a campaign, an outage or a viral post. We design routing, priorities and overflow so messaging demand does not starve voice or email, and we define service levels that reflect how quickly customers expect replies on each platform. Reporting is set up so leaders see volumes, response times and outcomes by channel and by brand, and so the case for adding or retiring a channel is based on evidence.
04
How the QVCCS squad connects and launches each channel
Third-party messaging crosses marketing, digital, service, security and integration, so QVCCS musters a team from its own bench and owns the outcome end to end. A Senior Business Consultant / Business Analyst leads channel discovery and onboarding planning with your digital, marketing and service teams, because platform approvals often set the timeline. A Solution Architect owns the design for integrations, flows, identity and data handling. A Senior Developer builds the channel integrations, flows and bots, and a Software Developer builds and hosts any open messaging middleware, specified webhook by webhook in an Interface Control Document. A Systems Integration Tester proves every channel on real devices, including expired messaging windows, rejected templates and webhook failures.
Social channels also raise questions most voice projects never meet. Who in your organisation owns the WhatsApp business account, the Facebook page or the X handle, and what happens to the integration if that person leaves or a marketing agency changes? Which public posts picked up by Social Listening should become routed work, and which belong to the social media team? How are conversations from several brands kept apart in queues, divisions and reports? We work through these questions with your digital and service leads before build, record the answers in the design decision log, and launch channels one at a time so each is stable before the next arrives.
05
Keeping messaging channels healthy as platforms change
Messaging platforms evolve constantly, with changes to policies, features, pricing and approval processes; Genesys itself retired its original X channel in April 2024 and later delivered a new native X integration. Every Genesys and platform change goes through our release readiness review for its impact on your channels, and support follows your Genesys Cloud CX support model, alongside your provider or under SLA with us. We maintain any open messaging connectors we build, keep the handover pack current, and review channel performance with you – volumes, response times and outcomes by platform and brand – so routing, bots and staffing keep pace with how your customers choose to message, and channels that no longer earn their place can be retired.
What you get from QVCCS
- Channel strategy and BRD by region, brand and customer journey
- Onboarding plan for WhatsApp, Apple and social platform approvals
- HLD and LLD for integrations, message flows, bots and routing
- Social Listening rules and response routing where public posts matter
- Open messaging ICD and connector designed, built and documented
- SIT pack, device-level testing and phased cut-over with hypercare
- Release readiness reviews and support matched to your provider model
Genesys documentation references
- Third-party messaging overviewhelp.genesys.cloud
- WhatsApp Embedded Signup Flow overviewhelp.genesys.cloud
- Configure ACD for Apple Messages for Business integrationshelp.genesys.cloud
- Configure ACD messaging for X (Twitter) Direct Messaginghelp.genesys.cloud
- Get started with open messaginghelp.genesys.cloud
- Social listening topicshelp.genesys.cloud
- Deprecation: Native X (formerly Twitter) third-party messaging channelhelp.genesys.cloud
- Genesys Cloud pricing hub: WhatsApp pricing after 1 October 2026help.genesys.cloud
Methods & templates
WhatsApp, Apple Messages & social messaging: the templates behind each stage
Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For WhatsApp, Apple Messages & social messaging, the work concentrates in Discover, Define, Design, Prove, Transition and Run & evolve, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.
- 01DiscoverDiscovery sign-off
- 02DefineRequirements baseline
- 03DesignDesign authority review
- 04BuildBuild complete
- 05ProveGo / no-go readiness
- 06TransitionOperational acceptance
- 07Run & evolveService reviews
Stakeholder mapping and discovery workshops
Identifies which platforms, regions and brands matter, who owns each account, and what onboarding each platform owner will require.
Requirements Traceability Matrix (RTM)
Traces per-channel service hours, identity rules, opt-in obligations and reporting needs to design elements and SIT test cases.
Interface Control Document (ICD)
Defines open messaging webhooks, payloads, token validation, retries and error handling for any custom channel middleware we build.
SIT test pack and negative testing
Tests every channel on real devices, including rich content, attachments, expired messaging windows, rejected templates and webhook failures.
Operational handover pack
Hands over as-built integrations, connector runbooks and platform contacts so channels can be supported and changed safely.
Release impact assessments
Reviews Genesys and platform changes to policies, features and APIs before they affect your live messaging channels.
How we deliver
WhatsApp, Apple Messages & social messaging: one accountable team, start to finish
- 01Plan channelsAgree which platforms, regions and journeys to support, and start onboarding and approvals with each platform early.
- 02DesignIntegrations, message flows, bots, identity, routing and reporting designed once and applied consistently across channels.
- 03Connect & buildCertified developers configure each channel, build flows and bots, and create open messaging connectors where required.
- 04TestReal-device testing of every channel, content type, hand-off and failure path, followed by agent acceptance testing.
- 05Launch & supportPhased go-live with hypercare, then support aligned to your model and reviews as platforms and demand evolve.
- Solution Architect
- Senior Business Consultant / Business Analyst
- Senior Developer
- Software Developer
- Systems Integration Tester
Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →
In practice
Where we have delivered this, and related work
A UK estate agency: valuation requests on WhatsApp, captured by a bot
How QVCCS moved a UK estate agency's valuation requests into WhatsApp and web messaging on Genesys Cloud CX: a bot, a secure lead integration, IVR deflection.
- Users
- Valuations team and senior managers
- Licence
- Existing Genesys Cloud CX organisation
A luxury hotel group: WhatsApp, web messaging bots and Microsoft Dynamics 365
How QVCCS acted as expert to the experts for a luxury hotel group, guiding Genesys Cloud CX digital bot flows, WhatsApp templates and Dynamics 365 data actions.
- Agents
- 200
- Licence
- Genesys Cloud CX 3
A UK healthcare services provider: live on Genesys Cloud first, then delivery self-service
How QVCCS took a UK healthcare services provider live on Genesys Cloud CX while its APIs were late, then added self-service that checks and books deliveries.
- Users
- About 55, including an outsourced partner's agents
- Licence
- Genesys Cloud CX 3
Questions
WhatsApp, Apple Messages & social messaging: common questions
How do you connect WhatsApp to Genesys Cloud?
Use the WhatsApp Embedded Signup Flow in Genesys Cloud, which creates the integration from a Meta business portfolio owned by your brand, then route messages through an Architect inbound message flow. Messages sent outside WhatsApp's customer service window need approved templates, so opt-in and template design come before build.
Which messaging apps does Genesys Cloud support?
Genesys Cloud natively supports WhatsApp, Facebook Messenger, Instagram Direct Messaging, X Direct Messaging and Social Listening for public posts, plus Apple Messages for Business through its own integration. Open messaging lets organisations connect custom or additional channels via an API, and QVCCS builds those connectors where a platform is not supported natively.
What is Genesys Cloud open messaging?
Open messaging is a lightweight API with webhooks for connecting custom or additional messaging channels to Genesys Cloud. Your middleware sends customer messages in and receives agent replies on a secured webhook, so the conversation is routed like any other.
Are social messages routed like calls and web messages?
Yes. Third-party messages pass through inbound message flows and ACD routing, using the same queues, skills, priorities and wrap-up codes as other interactions. QVCCS designs the routing and overflow so agents work one consistent queue and leaders see every channel in the same reports.
Last reviewed