Handbook
Genesys Cloud digital channels: web messaging, SMS, WhatsApp and email
A detailed handbook for the people who design, build and run Genesys Cloud digital channels. It covers the three delivery models, licensing, Messenger configurations and deployments, the messaging timers, authenticated and mobile messaging, open messaging, SMS, WhatsApp, email, flows, utilization, co-browse, the end of web chat, limits, analytics and data protection. Checked against Genesys sources on 16 November 2026.
In short
- Web messaging, platform messaging, open messaging and email are different delivery models with different owners.
- Digital queues have no default in-queue flow and inactivity handling is off by default, so set both before go-live.
- WhatsApp needs approved templates after 24 hours, and SMS needs consent, registration and tested opt-out handling.
- An MX record sends all mail for that domain to Genesys, so use a subdomain or redirect, and set up DKIM.
- One email and four messages per agent are defaults, not limits, and preferred agent routing turns off last-agent routing.
01
Four channels, three delivery models
This handbook is for the people who design, build and run digital channels in Genesys Cloud: solution architects, web and mobile teams, messaging and DNS owners, flow authors, workforce planners and contact centre managers. Every statement about Genesys Cloud comes from Genesys's documentation, listed in the sources and checked on 16 November 2026. Where something is our own practice, it is labelled QVCCS practice.
1.1 Not four settings of one thing
Web messaging, SMS, WhatsApp and email are often listed as though they were four switches on the same feature. Genesys Cloud delivers them through different mechanisms, with different configuration screens, routing entry points, limits and failure modes. Getting this wrong costs project time, because a team that has built web messaging assumes WhatsApp is a tick box.
| Model | Channels | How an interaction arrives | Where routing is set |
|---|---|---|---|
| Messenger | Web messaging and mobile messaging | A snippet on your site or an SDK in your app opens a Messenger session | In the Messenger deployment |
| Platform messaging | SMS, WhatsApp, Facebook Messenger, X, Instagram and Apple Messages for Business | A number or third-party account delivers to a provisioned address | Message Routing, mapped to an inbound message flow |
| Open messaging | Any channel you build middleware for | Your middleware calls the Genesys API | An inbound message flow, plus your webhook |
| ACD email | Genesys mail, SMTP, IMAP or Microsoft Graph delivers to a routed address | Email settings, mapped to an inbound email flow or a queue |
1.2 The sentence that proves it
Genesys's message routing article says it covers SMS, open messaging and third-party channels but does not apply to web messaging, whose routing is defined as part of the Messenger deployment. Email has its own administration area and its own flow type. And agent utilization counts capacity separately by media type, which is why a team can be well staffed for one channel and short on another that looks identical on the agent's screen (part 12).
1.3 What digital shares with voice, and what it does not
Genesys says messages work like other ACD interactions: they have alerting timeouts and service level targets, appear in analytics and can use scripts. So routing strategy, queue design, wrap-up codes, quality forms and dashboards built for voice extend to digital. The differences are structural.
- Messages are asynchronous. Genesys's example is a customer who sends two messages, gets a reply, and sends two more hours later; the messaging threading timeline, 72 hours by default, decides how long that stays one conversation.
- Concurrency is normal. By default an agent can handle up to four messages at once, and only one email.
- Agents complete wrap-up on each portion of a conversation they handle, which can be several messages, so what an agent wraps up and what a customer experiences as one conversation differ.
- The channel is not the customer's identity. A Messenger session means nothing outside the browser unless you authenticate or resolve identity, which is why conversations and customers are different numbers in every digital dashboard (part 14).
02
Licensing and prerequisites
Digital channels show more clearly than anything else why licensing is a design input. Several of the things that decide what can be delivered also sit outside Genesys entirely.
2.1 What the plan comparison shows
| Capability | CX 1 | CX 2 | CX 3 | CX 4 |
|---|---|---|---|---|
| Web messaging, email, SMS and in-app messaging | Add-on | Included | Included | Included |
| Omnichannel routing | Add-on | Included | Included | Included |
| Third-party messaging (Facebook, X, Instagram, WhatsApp, Apple Messages for Business) | Add-on | Experience units | Experience units | Experience units |
| Inbound WhatsApp Business Calling | Add-on | Included | Included | Included |
| Co-browse | Add-on | Included | Included | Included |
| Digital user tracking and predictive engagement | Add-on | Included | Included | Included |
| Outbound SMS, WhatsApp and email campaigns | Add-on | Included | Included | Included |
- Third-party messaging is the one row in the digital block marked as requiring experience units rather than plainly included. A CX 2 client adding WhatsApp has added a channel and a metered dependency, so put the question to Genesys or the reseller; our AI Experience tokens guide explains the metering.
- Individual release notes carry narrower subscription lists, including Digital variants such as CX 1 Digital Add-on II, CX 2 Digital and CX 3 Digital. Estates licensed for a digital-only programme sometimes later want voice, and the reverse.
- Quality management, speech and text analytics and recording all apply to digital interactions, each with its own entitlement.
2.2 The client owns the external accounts
Genesys's messaging use case says customers adhere to each social platform's terms and conditions and configure their own accounts before integration; the social use case adds that customers set up and verify their own Meta Business Manager account and keep ownership of the number used for WhatsApp. For every third-party channel, the client must own and configure the external account before Genesys configuration can start, and that is the commonest cause of a slipped digital timeline.
03
Web messaging: configurations, deployments and domains
Web messaging has a two-object model, and the separation is the whole point. A configuration is a design; a deployment publishes a version of it to your site.
3.1 Configurations and versions
Genesys describes Messenger configurations as letting administrators create several versions to set branding and customer experience, and Messenger deployments as publishing configuration versions to a website in one operation. Getting started is three steps: create a configuration, create a deployment that assigns a version of it and generates the snippet, and optionally refine behaviour with the Messenger JavaScript SDK. Genesys gives the examples itself: a different configuration per domain, one for all domains, or one for situations such as holidays.
The configuration wizard runs through channel setup, appearance, behaviour and review. Configurations can be versioned, cloned to a draft, previewed and duplicated, and a deployment's assigned version can be changed in one operation. Since February 2024, administrators can turn web messaging off in a configuration and deploy Messenger only for its apps, such as co-browse for voice or the Knowledge App.
3.2 Behaviour settings that matter
- Authentication is switched on in the behaviour step, and it changes who can start a session and what flows can see (part 5). Decide it before the branding workshop, because it gives the web team an integration to build.
- Since February 2024, the launcher can stay visible through page reloads and navigation when it was triggered by business logic, which matters for predictive engagement offers on multi-page journeys.
- Whether customers can send files is set in the configuration, and which file types are accepted is set through the supported content profile on the deployment: two separate decisions.
- Messenger runs inside the client's page, so their CSS, cookie banner, consent platform and content security policy can all interfere with it.
3.3 Restricting domains
When deploying, Genesys offers Allow all domains, which it says is for testing and development, or a list of allowed domains, which it says prevents unauthorised use of your snippet from unknown domains. A production deployment left on Allow all domains lets any site embed the snippet and open sessions against the client's queues.
The snippet can be added to page templates by hand or through Google Tag Manager, and the same deployment serves mobile apps through its domain and ID in the Transport SDK.
3.4 Sessions stop at the deployment boundary
Genesys states that with several deployments, each web session is contained within its deployment, and contact, journey and conversation data do not span deployments. It presents this as a way to separate business areas, and to separate environments that require authentication from those that do not; for one session across deployments, combine them into one.
A client with a marketing site, a signed-in customer area and a partner portal will naturally create three deployments, and then find the same person appears as three unrelated contacts with no shared history. That is a data protection decision made on a Messenger screen, so it needs the data protection officer as well as the web team.
04
Sessions, threading and inactivity
Messaging has several independent clocks, set in different places, and conflating them produces the familiar complaint that conversations keep getting lost. Each is documented; nothing documents them together.
4.1 The clocks
| Timer | Range and default | Where it is set | What it controls |
|---|---|---|---|
| Messaging threading timeline | 0 to 72 hours in one-minute steps; default 72 hours (4,320 minutes) | Per messaging channel | How long a disconnected conversation stays open so a new message threads to it |
| Guest session duration | 15 minutes to 18 months; default 3 days | Messenger configuration | How long an inactive web messaging session stays available to the customer |
| Inactivity handling | Disabled by default on all queues | Queue | Whether a silent conversation is disconnected or rerouted to a flow |
| In-queue flow duration | 72 hours maximum | Architect | After 72 hours, an in-queue message or email flow disconnects |
| Parking | Up to seven days by default, adjustable from one to 28 | Organisation | How long an agent can park a message conversation |
4.2 Threading timeline
Once a conversation disconnects, the threading timeline decides how long later messages join it. It is set per channel: third-party messaging, SMS, web messaging and open messaging. A value of zero means every reply, and every agentless outbound message from a disconnected conversation, starts a new conversation.
Genesys lists what shortening it does: conversations separate more often, routing to the last agent ends sooner, prior context stops showing to the agent, and frequent messages from one customer are less likely to exceed conversation size limits. That last reason is telling: the operational case for a shorter window is the size of the conversation, not tidiness.
4.3 Guest session is a different clock
Genesys states that changing the threading timeline does not affect guest session duration, and its FAQ explains why: the threading timeline belongs to the internal conversation model. With threading at zero, the internal conversation ends when the agent disconnects; a new message in the same guest session gets a new conversation ID, a new flow execution and a new transcript, while the customer's experience is unaffected.
So the customer sees one chat and Genesys records two conversations. Genesys also says conversation history is retained for 18 months for identified and curated contact records and for 15 days for other contacts, separately from both timers. Set each deliberately and tell the reporting team what mismatch to expect.
4.4 Inactivity handling is off until you turn it on
Genesys states that by default inactivity handling is disabled on all queues, and inactive conversations stay assigned to the original agent until someone disconnects them, counting against that agent's utilization. Once enabled, it applies to messages from both sides, resets whenever either side sends, and either disconnects or routes to another message flow. The agent sees a clock that turns red, with a notification a minute before the end. It covers Facebook, X, Instagram, WhatsApp, inbound SMS, web messaging, open messaging and Apple Messages for Business.
05
Authenticated and mobile messaging
Guest sessions are anonymous. Authentication turns a session into a known customer, and mobile messaging is the same Messenger object reached by an app rather than a browser.
5.1 Authenticated web messaging
Genesys lets administrators require customers to authenticate with your website before starting or resuming a web messaging session, and optionally personalise the experience with authenticated users' attributes in Architect. The integration is OpenID Connect: create the OpenID Connect Messenger configuration integration with your provider's details, turn on authentication in the Messenger configuration, deploy it, and set identity resolution parameters for the deployment.
Flows can then read authenticated attributes, including Message.IsAuthenticated, which Genesys says is true if authentication was requested for the message when it entered the queue. A flow and a queue can treat a verified customer differently from an anonymous one, and verification steps can come out of the agent's script because the platform has already done them. Genesys also documents step-up authentication during a conversation, and since February 2026 Messenger can accept an existing token so users already signed in to your site or app are not asked to sign in again. Our innovation article on authenticating customers in web messaging covers the set-up in more depth.
5.2 Two routes to mobile
Genesys describes Mobile Messenger as a predefined Messenger window you embed in an app, with configurable appearance and behaviour, and the headless Transport SDK as the way to build a custom mobile messaging client. Both use the same Messenger configuration and deployment as the web.
Headless means the SDK supplies the messaging transport and the client's developers supply everything the customer sees: designs, build, app store releases and a place on the mobile team's backlog. That is a software project, and it is regularly estimated as configuration.
- On the Transport SDK, inbound attachments are limited to 10 MB and outbound to 25 MB, so a customer cannot send in what you can send out, and malicious file types such as .exe are blocked.
- Custom attributes must total less than 2 KB per message; above that the inbound message fails to send, and the app is told through an error. Passing a whole customer record as context is the obvious mistake.
- Since 27 January 2025, configurable session persistence has been removed, and Messenger's local storage sits in the Genesys domain that serves Messenger; Genesys says this does not affect Mobile Messenger.
06
Open messaging: the channel you build
Open messaging is how a channel Genesys does not support becomes an ACD interaction. It is a development project that looks like a configuration.
6.1 What Genesys provides, and what you build
Genesys describes open messaging as a lightweight integration consisting of a public API with webhooks. Messages arrive when a customer sends one, or go out as agentless messages through the API; outbound messages go to the webhook you configure, and your middleware delivers them to the external service. Genesys's social use case is explicit that customers build any middleware needed between open messaging and the external application.
The Genesys side is short: create an Open Messaging platform integration, name it, and enter the outbound notification webhook URL and a signature secret token used to generate the X-Hub-Signature-256 header. Genesys states that only webhook URLs on port 443 work.
6.2 Limits and side effects
- An open message can be at most 128 KB, counting all fields, in either direction; larger messages are rejected.
- Outbound web messaging and open messaging content is limited to 4,000 characters, and an outbound open messaging recipient address to 200 characters.
- Agentless outbound open messages are text only.
- Agents see open messages with the standard SMS icon and the queue or integration name, so several proprietary channels all look like SMS unless naming is designed.
- In the agent UI, recordings, Architect, analytics and performance views, open messages share one open subtype. Per-channel reporting needs separate integrations and naming discipline.
07
SMS: numbers, compliance, opt-outs and your own carrier
SMS is the channel where the platform work is small and the procurement and regulatory work is large.
7.1 Number types and lead times
Genesys supports long codes, which are standard DID or toll-free numbers typically used between two parties, and short codes of five or six digits, used for large audiences. Long codes can be bought and managed within Genesys Cloud; short codes need an external procedure, and Genesys says obtaining one can take several weeks. For outbound campaigns, an alphanumeric sender ID of three to 11 characters, including letters and no spaces or special characters, is available only in specific countries.
Genesys currently marks its long code inventory management page as temporarily rolled back, so check the state of number self-service before promising it. Outbound numbers are assigned to queues so agents can send on a queue's behalf, a capability since December 2018, and inbound numbers map to flows in Message Routing.
7.2 Consent and regulation
Genesys's SMS best practice is blunt: consent and opt-in are mandatory, consent cannot be obtained deceitfully, and the customer must know what they are signing up for. It points to the CTIA's messaging principles, warns that failing to align can lead to carrier filtering that takes time to resolve, and ranks sender types by trust: short codes and toll-free numbers as trusted, ten-digit long codes as lower trust. Its long code regulations page adds daytime-only sending, HELP and STOP support, respecting do-not-contact registries, and consulting qualified legal counsel.
For the UK, Genesys announced that all organisations must register their business and use case before using UK long codes. From 27 May 2024, new UK long code purchases needed an approved KYC registration, and by 30 September 2024 existing UK long codes without one were to be released and potentially unavailable to reacquire. Genesys keeps separate pages for UK and Singapore long codes, so the position must be checked per country.
7.3 Opt-out keywords and phrases
| Category | Keywords | Effect |
|---|---|---|
| Opt-out | STOP, STOPALL, UNSUBSCRIBE, REVOKE, OPTOUT, CANCEL, END, QUIT | The customer no longer receives messages from that outbound number |
| Re-opt-in | START, YES, UNSTOP | Messages from that number resume |
| Help | HELP, INFO | The customer receives information about the SMS programme |
- Genesys routes HELP and INFO for short codes, but not for long codes or toll-free numbers, so on the number types most UK clients use, HELP needs handling in a flow.
- Phrase-based detection evaluates inbound messages against predefined opt-out phrases and suppresses the number. Genesys warns it does not catch every request, may occasionally misclassify a message, and that organisations remain responsible for managing suppression status.
- A suppression list can be retrieved, and Genesys keeps ownership of keyword compliance even when you use your own carrier.
7.4 Bring your own SMS carrier
Since September 2025, administrators can integrate existing SMPP accounts and numbers from their preferred carrier, broker or aggregator, and assign them to outbound queues, inbound flows or agentless notifications. Genesys frames it as mirroring the flexibility of BYOC for voice, for extending SMS to more markets, reducing messaging costs or controlling routing. It is installed from AppFoundry, priced under Genesys's fair use policy, and indirect customers set it up through their partner.
- Not supported: VPNs (TLS 1.2 or 1.3 is required instead), MMS and alphanumeric sender IDs.
- Bandwidth cannot currently be used as a BYO SMS provider, because a platform control at Bandwidth prevents provisioning public IP addresses across multiple accounts.
- Genesys's IP addresses must be on the vendor's allowlist, and Genesys expects a delivery report for each segment of a concatenated message.
- You remain responsible for any use case registration with your provider.
08
WhatsApp: the 24-hour window and account ownership
WhatsApp behaves differently from every other channel in the estate, and one rule explains most of it. The rest comes from the Meta accounts behind it.
8.1 The 24-hour rule
Genesys explains that WhatsApp business customers can reply to inbound messages within 24 hours without a template; after 24 hours, or to send a proactive message, they must use pre-approved template messages. When the customer responds again, the 24-hour timer resets. This is Meta's rule, not a Genesys setting, and Genesys's 2020 release note points to Meta's charges for templates sent outside the customer care window.
So the natural service design, resolving a query today and messaging tomorrow when the part arrives, needs an approved template and may incur a charge. No other channel in this handbook has an equivalent constraint.
8.2 Templates
- Standard templates support text and a single-media image header, are created and approved in Meta Business Manager, then mapped to a Genesys canned response for agents, bots, the agentless API and campaigns.
- Carousel templates are created in Genesys Cloud and submitted to Meta for approval; they carry up to 10 cards with images or video and interactive buttons.
- Template components can include a header, a text footer and buttons for quick replies, phone calls or websites with static or dynamic URLs. Header images are JPEG, PNG or WebP up to 5 MB.
- An agent must fill every field, or substitution must fill it from conversation attributes; if a field is empty, Genesys shows an error and the message does not send.
- Templates can be used on other messaging channels, where Genesys sends them as plain text.
- Agents cannot switch an interaction to WhatsApp from another channel; WhatsApp is entered from the customer's side.
8.3 Onboarding and ownership
Genesys's Embedded Signup connects Meta Business Manager and WhatsApp Business Accounts to Genesys Cloud, verifies and registers phone numbers, and leaves accounts created this way owned by the business and shared with Genesys. Phone numbers, profiles and templates are managed in Meta Business Manager, where insights and approximate pass-through charges are also shown, so per-conversation cost reporting is a Meta exercise. Genesys's instruction is direct: do not create new WhatsApp business accounts or add numbers in Meta Business Manager; follow the Embedded Signup flow.
The customer is responsible for setting up and verifying its Meta Business Manager account, and for owning the number used for WhatsApp for as long as the account is active. Genesys also documents migrating WhatsApp from another platform.
8.4 WhatsApp voice
Since February 2026, WhatsApp business numbers can accept inbound voice calls in Genesys Cloud, with standard transcription, standard ACD routing and blind transfers. A WhatsApp number can now carry both messaging and voice.
09
Email: connecting, DNS and deliverability
Email is the most architecturally consequential channel in this handbook, and the one least likely to be led by the contact centre team. The first decision is which mail system carries the traffic.
9.1 Genesys mail or your own
Genesys says agents can send and receive ACD email through your own domain or the Genesys Cloud domain, whose addresses take the form yourAccountName.myGenesysCloud.com. Its provisioning list covers using your own domain, registering your domain and redirecting inbound mail to it, sending with the Genesys domain, a custom SMTP integration for outbound, a custom IMAP integration for inbound, a custom Microsoft Graph integration for both, and DMARC monitoring for custom domains.
The real fork is Genesys-native mail, which uses Amazon SES, against your own mail system. Native is fastest and needs no mail-server project. Your own system, through Graph or SMTP with IMAP, keeps mail in your tenant for retention, legal hold, journaling and existing data loss prevention, at the cost of integration work, credentials and another failure domain.
- Genesys states that a domain registered in another organisation can be reused only with Microsoft Graph, or with SMTP outbound and IMAP inbound together, and not with native SES. That matters for separate development, test and production organisations.
- A domain must be unique within an organisation, and an email address or route used in one organisation cannot be reused in another.
- Only one integration can be attached to an email domain or address, so Graph and SMTP with IMAP cannot be paired on one address for redundancy.
- IMAP integrations poll up to 10 folders per route.
9.2 The MX record decision
Genesys states that after verifying the domain you add an MX record, and that all email for a domain or subdomain with that MX record routes only to Genesys Cloud; it recommends a subdomain such as support.yourcompany.com. Point the MX at the corporate domain and company-wide mail stops reaching people's inboxes.
To keep copies in your own system, Genesys documents redirect rules from your mail server to an address on the registered domain, and a register-and-redirect pattern for organisations whose existing addresses do not use a subdomain. Outbound needs less: Genesys says that to reply and send on your behalf you only need TXT records, not MX records. Domain verification can take up to 72 hours, and DKIM and a custom MAIL FROM domain are optional advanced settings. When switching over an existing domain, add every address and routing setting before adding the MX record.
9.3 Deliverability
Sending from Genesys is sending as the client's brand, which brings the contact centre into the messaging team's discipline. Genesys presents DKIM as optional, to help stop outbound mail from being marked as spam, and lists DMARC monitoring for custom domains, a signal that it expects customers to watch authentication results rather than assume them.
- The reply-to address must be an ACD-routed address. If it is an unmonitored mailbox, every customer reply disappears, invisible to routing, service levels and reporting.
- Where the client already publishes SPF, adding a sending path carelessly can break authentication for the whole company's mail.
- Volume spikes damage reputation: a large campaign from a domain that normally sends a few hundred service emails a day can get it filtered, harming service mail too.
10
Email: threading, routing and limits
Email continuity works quite differently from messaging, and the limits that shape an email estate are spread across several Genesys pages that do not always agree.
10.1 How email threading works
Genesys threads a customer's reply with the earlier message so the agent sees the whole history; a new email with a different subject starts a new conversation. Its threading settings article says threading is based on subject line, ignoring Re and Fwd, that a trailing space can cause a mismatch, and that replies within 30 days thread by default, with the period reducible or threading disabled. Its email overview adds that threading uses the In-Reply-To and References headers, so unrelated messages with the same subject and sender from certain mail clients are no longer threaded together.
Two rules need briefing. The timer starts when the agent disconnects the email, and Genesys states that if the agent does not disconnect, incoming emails thread even when threading is disabled. And Enable Subject Based Threading starts a new conversation ID when the subject changes.
- Threading also decides survey timing: with Send Survey set to As per the Threading Timeline in a web survey policy, the first invitation goes when the threading timeline expires, so a 30-day window sends the survey a month after the case closed.
- Reconnecting a closed email follows the same 30-day, or configured, lifetime.
10.2 Routing and copies
Genesys explains that an ACD email routes to a mailbox associated with a queue and then to its members, and that an administrator must configure agents to receive email. Both halves are needed, and the second is the usual reason email is queued but nobody can see it. Replies route to the last agent who handled the email if that agent is on queue and not fully utilised, unless preferred agent routing is in use (part 12).
Administrators can configure up to five BCC addresses for outbound replies, which Genesys presents as a way to keep copies for compliance or backup, a capability since June 2019. Where there is no Graph or IMAP integration, BCC to a journaling archive is the cheapest way to meet a retention requirement.
10.3 Email limits
| Limit | Rate limits article | Developer Center limits page |
|---|---|---|
| Email domains per organisation | 5 custom or Genesys domains; 15 campaign and agentless domains | 15 inbound domains, configurable |
| Addresses or routes per domain | 1,000 | 1,000, configurable |
| Agentless email | 300 per minute | 600 per minute, configurable |
| Campaign and agentless combined | 3,000 per minute | 3,000 per minute, configurable |
| Email campaigns | 1,200 per minute across all running campaigns | Not listed |
| Outbound message size | 40 MB, SMTP, SES and IMAP | 150 MB Graph; 250 MB custom SMTP |
| Recipients | 50 across To, Cc and Bcc combined | Not listed |
| Auto-responses from an Architect flow | 1 per conversation | Not listed |
| Attachments per email | Not listed | 50 |
| Connected emails per agent | Not listed | 100, not configurable |
| Parked email | Presented to the agent after 7 days | 7 days, configurable |
- The pages disagree on domains: Genesys's ACD email overview says two, its manage-routing article says five and to contact Customer Care for more, and the limits page shows 15 and configurable. Check your organisation's value before a multi-brand design depends on it.
- Genesys's email overview gives 40 MB as the encoded message limit, about 29 MB of content, and says increases can be requested with a business justification, which probably explains the higher figures on the limits page. Design to 40 MB unless your organisation has a confirmed higher limit.
- Genesys says auto-replies are limited to one per conversation to avoid auto-replies answering each other, so a second courtesy message needs another mechanism.
11
Flows: inbound and in-queue
Both digital families use Architect, but not in the same way, and a team that has only built call flows will make predictable mistakes.
11.1 Inbound message and email flows
Genesys's Message Routing page lists active inbound message flows and the numbers or addresses tied to them; when someone messages a number, the message enters its flow. It is the estate map for platform messaging, and web messaging does not appear on it. Creating a message flow is ordinary Architect work, including a division and an optional error event transfer queue.
Email flows are selected in the email settings, and differ in a way that changes design. Genesys states that, unlike call flows, inbound email flows do not have failure or success paths, that errors are handled by configuring an action's path, and that email flows have no language settings, in-queue handling or audio controls. They do have actions such as Detect Intent, Get Email Headers and Send Auto Reply.
11.2 Digital queues have no default in-queue flow
Genesys states that, unlike calls, Architect does not include a built-in default in-queue flow for email and message interactions. A digital customer waiting in queue receives nothing unless someone builds and assigns one. Genesys suggests auto-responses every 30 seconds with queue position, and transferring to another in-queue flow after a set time.
- In-queue email and message flows run for at most 72 hours, then disconnect.
- Architect limits the in-queue flows opened for one interaction to 30, a problem Genesys says can occur when a transfer targets the current queue: a flow that transfers back into its own queue silently hits the ceiling.
- If the first message is outbound, the in-queue flow does not launch until an inbound reply arrives.
12
Utilization, continuity and the agent experience
This part matters most for a client's cost model. Utilization decides how many digital agents are needed, routing settings decide whether a returning customer reaches the same person, and the agent desktop decides how the work feels.
12.1 Utilization defaults
Genesys defines utilization as the maximum number of concurrent interactions the ACD can assign to an agent. By default that is one call, one callback, one email, up to four chats, up to four messages and up to four workitems, and Genesys's FAQ gives 25 as the maximum capacity for each interaction type. One email is a conservative default, not a technical limit, and it is the single biggest input to an email staffing model.
Interruptions are set per media type: on each row, you choose which incoming types can interrupt. Genesys advises not allowing interruptions to voice, notes that by default interruptions to email are allowed, says the order of types does not set priority, and that when one interaction interrupts another, hold time is recorded for analytics. Non-ACD calls are excluded from ACD utilization by default, and preview calls count as callbacks.
12.2 Weighted capacity
For messaging, a maximum weight capacity can be set: each active message starts with a weight of 1, and new interactions are assigned only while the agent's total weight is below the capacity. Genesys says this field is a prerequisite for dynamic utilization. Weighting answers the objection that four complex WhatsApp threads are not the same work as four password resets.
12.3 Last agent or preferred agent
Genesys tries to route callbacks, email replies and message replies to the last agent who handled them, if that agent is on queue and not fully utilised. But it also states that for email, messaging and inbound callbacks, when preferred agent routing is used, Genesys no longer attempts last-agent routing; scheduled callbacks are unaffected. Turning on preferred agent routing for better matching therefore switches off continuity on those channels, and nothing warns you. The continuity window itself is the threading timeline (part 4).
12.4 The agent desktop
- Agents can park message and email interactions and resume them from Parked Conversations. Messages can be parked for up to seven days by default, adjustable from one to 28, with up to 25 parked at once, and Genesys documents when parked interactions resume automatically and how that affects after-call work.
- Channel switching lets an agent start a conversation on another channel from the interaction card, grouping all channels for the contact. It works only for interactions linked to an external contact with the right details, uses only the first value where a contact has several, needs a queue that allows outbound, and cannot switch to WhatsApp.
- Canned responses carry WhatsApp templates and serve as the governed response library, and scripts work with message and email interactions.
- Supervisors can monitor in-progress web messaging, third-party and API messaging and SMS, and with permission take over a messaging conversation. Email is not in that list.
- Digital work needs its own permissions, such as conversation:message:park, conversation:message:takeover and conversation:email:park, separate from voice rights.
13
Co-browse, the end of web chat, and messaging limits
This part covers three things that affect existing estates: co-browse, the move from web chat to web messaging, and the published messaging limits, most of which are hard.
13.1 Co-browse belongs to Messenger
Genesys's co-browse use case lists the assumptions for co-browse with web messaging and voice: CX 2 licensing or the Digital add-on, a website prepared for co-browse, and masking added to private data on the site to control what the agent can see. Legacy co-browse for chat and voice was due to be deprecated on 27 January 2025, and Genesys directs customers to co-browse for Messenger. Co-browse for voice is delivered through Messenger, so a voice-only client needs a Messenger deployment, even one with web messaging turned off.
Genesys's migration FAQ warns that the two versions are not cross-compatible: as soon as agents are assigned the Conversation, CobrowseVoice, Add permission, generated meeting IDs work only with the Messenger version. Since October 2023, agents can use a toolbar and ask the customer to navigate to a page the agent chooses.
13.2 Web chat is being retired
Genesys states it will no longer support ACD Web Chat v2 and its chat widget versions, following v1, that predictive engagement is ending support for these legacy versions too, and that all customers are encouraged to move to web messaging and Messenger. Support for v1 ended on 27 January 2025; v2 and widget versions 1.1 and 2.0 are deprecated, to be removed at a later date.
The replacement is architectural. With web chat, the site carried a chat widget and a separate predictive engagement tracking snippet; with web messaging, the Messenger snippet replaces both. Genesys keeps a migration series, including the analytics impact of the move and rebuilding web chat offers as web messaging offers.
13.3 Messaging limits
| Limit | Value | Configurable |
|---|---|---|
| Outbound SMS content | 765 characters | No |
| Outbound web messaging and open messaging content | 4,000 characters | No |
| Other outbound messaging content | 2,000 characters | No |
| Outbound message media | 25,000,000 bytes | No |
| WhatsApp and Apple outbound media | 104,857,600 bytes | No |
| SMS outbound media | 5,242,880 bytes | No |
| X outbound media | 3,145,728 bytes | No |
| Outbound messages per minute | 1,200 | Yes |
| WhatsApp agentless and campaign messages per minute | 900 | Yes |
| SMS agentless and campaign segments per minute, organisation | 1,200 | Yes |
| SMS segments per minute per US long code | 70 | No |
| SMS segments per minute per toll-free number | 180 | No |
| SMS segments per minute per international long code or alphanumeric sender | 700 | No |
| SMS segments per minute per short code | 1,200 | Yes |
| Provisioned SMS numbers | 1,000 | Yes |
- Genesys's limits page distinguishes counted limits, usually ending in max, from rate limits ending in rate.per an interval: one is capacity planning, the other throughput. Customers can ask Customer Care to make a case for raising a limit once other options are exhausted.
- 765 characters is about five standard SMS segments. Concatenated messages are billed per segment and can arrive out of order on some handsets.
- Genesys's own example: 17 US long codes sending 70 segments a minute each fit within the organisation's 1,200. Campaign speed is usually set by the per-number rate, and adding numbers only helps up to the organisation limit.
- Trial and sandbox organisations may have lower limits, such as 100 outbound messages and one SMS number, until they become billable.
14
Analytics, data protection, design and what goes wrong
The last part covers how digital is measured, the data protection decisions it raises, the order we design in, and the problems we see most often.
14.1 Measuring digital
Genesys provides dedicated digital views: Email and Message Agent Performance Summary and Detail, and Email and Message Queue Performance Summary and Detail. Real-time columns always show current status, even when other columns are filtered to history, and filtered users can be shown as a group. Genesys warns that for asynchronous interactions such as email and messaging, speech and text analytics metrics like topics and sentiment take up to 72 hours to update in aggregate views.
Then there is counting. A customer experience and a conversation differ in every model: guest sessions and deployment boundaries in web messaging, several messages threaded into one conversation with wrap-up per portion in platform messaging, a month of correspondence in one email thread, and every open messaging channel in one subtype. Conversations handled is not customers served, and the only platform remedy is identity: authentication, external contacts and identity resolution.
14.2 Data protection
Every digital channel produces searchable text about a named customer, which changes the risk profile even where it is no riskier than voice. Recording, monitoring, transcription of WhatsApp voice and quality evaluation all apply to digital interactions. A phone number is personal data, and an opt-out list is a processing record.
- A retention decision per channel, including email copies kept by BCC or in the client's own mail system.
- A co-browse masking standard naming the pages and fields.
- An SMS and WhatsApp content standard covering consent, opt-out wording and the frequency customers agreed to.
- An entry in the DPIA for any analytics or AI processing of digital content, since speech and text analytics, sentiment and AI scoring all process customer messages.
14.3 The order we design in
- Four questions first: which channels for which journeys, the licence position including experience units, where email must be retained, and which markets and number types.
- Identity and routing foundations: divisions, external contacts and identity resolution, utilization per media type with the workforce team, wrap-up codes that suit asynchronous work, and authentication where the client has a login.
- External artefacts in parallel: Messenger configuration and versioning, one DNS change request, Meta verification and WhatsApp numbers, SMS numbers and registration, templates, and the co-browse masking standard.
- Flows and the queue experience: inbound patterns, an in-queue flow on every digital queue, threading and inactivity per channel, auto-responses and the continuity decision per queue.
- Agent enablement, then measurement: canned responses, templates, channel switching, parking rules, digital evaluation forms, and digital views with the analytics delay disclosed.
14.4 What goes wrong
| Symptom | Likely cause | Fix |
|---|---|---|
| Customers in a digital queue hear nothing | No in-queue flow; there is no default for digital | Build and assign one per queue (part 11) |
| Messenger appears on an unapproved site | Deployment left on Allow all domains | Restrict domains at go-live (part 3) |
| Same customer appears as several contacts | Separate deployments or anonymous sessions | Combine deployments; authenticate (parts 3 and 5) |
| Customer says one chat, dashboard says four | Threading timeline and guest session differ | Set both deliberately and explain (part 4) |
| Agents stay loaded with silent chats | Inactivity handling off by default | Enable it per queue (part 4) |
| Company email stops arriving | MX record on the corporate domain | Use a subdomain or redirect (part 9) |
| Customer replies vanish | Reply-to is not an ACD-routed address | Test replies per environment (part 9) |
| Outbound email lands in spam | No DKIM, or SPF not updated | DKIM, SPF and DMARC monitoring (part 9) |
| Survey arrives a month late | Survey tied to a 30-day threading timeline | Shorten threading or change timing (part 10) |
| Emails thread when threading is off | Agent never disconnected the email | Make disconnecting an expectation (part 10) |
| Second auto-reply never sends | One auto-response per conversation | Use another mechanism (part 10) |
| WhatsApp follow-up blocked | 24-hour window expired | Template inventory and briefing (part 8) |
| WhatsApp template will not send | A substitution field is empty | Design and test attributes (part 8) |
| HELP texts go unanswered | Not routed for long codes or toll-free numbers | Handle HELP in a flow (part 7) |
| Campaign slower than planned | Per-number SMS rate limits | Compute segments and numbers early (part 13) |
| Returning customers reach new agents | Preferred agent routing disables last-agent routing | Decide per queue (part 12) |
| Topics missing from this week's report | 72-hour analytics delay on asynchronous channels | Report later and say so (part 14) |
Questions
Common questions
Is web messaging routing configured in Message Routing in Genesys Cloud?
No. Genesys's message routing article covers SMS, open messaging and third-party channels and says it does not apply to web messaging, whose routing is defined in the Messenger deployment. Email has its own settings and flow type. That is why we treat web messaging, platform messaging, open messaging and email as different delivery models with different owners.
What is the difference between the threading timeline and guest session duration?
The messaging threading timeline, 0 to 72 hours with a default of 72, decides how long a disconnected conversation stays open internally. Guest session duration, 15 minutes to 18 months with a default of three days, decides how long the customer's web messaging session stays available. They are independent, so a customer can see one chat while Genesys records several conversations.
Can I send a WhatsApp message to a customer after 24 hours?
Only with a pre-approved template. Genesys explains that businesses can reply within 24 hours of an inbound message without a template, but after that, or to start a conversation, they must use templates approved through Meta. The 24-hour timer resets when the customer replies. Templates can incur Meta charges outside the customer care window.
Should I point my company domain's MX record at Genesys Cloud?
Usually not. Genesys states that all email for a domain or subdomain with the MX record routes only to Genesys Cloud, and recommends a subdomain such as support.yourcompany.com. To keep copies in your own system, use redirect rules or register-and-redirect. Outbound sending needs only TXT records, so test inbound routing separately.
How many emails can a Genesys Cloud agent handle at once?
By default one email, alongside up to four messages, four chats and four workitems, one call and one callback. Genesys's FAQ gives 25 as the maximum capacity per interaction type, so one email is a default, not a limit. Raise it gradually with quality monitoring, and review which media can interrupt email, since email is interruptible by default.
Does Genesys Cloud answer HELP texts automatically?
Only on short codes. Genesys routes HELP and INFO for short codes but not for long codes or toll-free numbers, while it handles opt-out words such as STOP on the outbound number. On long codes, handle HELP in a flow, test it on the real number type, and remember Genesys says organisations remain responsible for managing suppression status.
Sources
- Automatic handling of inactive messaging interactions – Genesys Cloud Resource Centerhelp.genesys.cloud
- Bring your own SMS Provider (SMPP) support coming to Genesys Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
- Deprecation: Configurable session persistence methods in Messenger – Genesys Cloud Resource Centerhelp.genesys.cloud
- Identity stitching and journey support coming to authenticated web messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- UK Longcode Registration Requirement for SMS – Genesys Cloud Resource Centerhelp.genesys.cloud
- ACD email overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- About ACD emails – Genesys Cloud Resource Centerhelp.genesys.cloud
- About agent interactions – Genesys Cloud Resource Centerhelp.genesys.cloud
- About Architect – Genesys Cloud Resource Centerhelp.genesys.cloud
- About customer surveys – Genesys Cloud Resource Centerhelp.genesys.cloud
- About email – Genesys Cloud Resource Centerhelp.genesys.cloud
- Message routing overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- About messages in the Genesys Cloud embedded clients – Genesys Cloud Resource Centerhelp.genesys.cloud
- About messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- About views and dashboards – Genesys Cloud Resource Centerhelp.genesys.cloud
- About SMS messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- About third-party messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- About web chats – Genesys Cloud Resource Centerhelp.genesys.cloud
- About web messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- Messaging overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Add a WhatsApp template message – Genesys Cloud Resource Centerhelp.genesys.cloud
- Add an inbound message flow that calls a digital bot flow – Genesys Cloud Resource Centerhelp.genesys.cloud
- Add an inbound message flow – Genesys Cloud Resource Centerhelp.genesys.cloud
- Add the MX record to the organization's domain server – Genesys Cloud Resource Centerhelp.genesys.cloud
- Agentless WhatsApp notifications – Genesys Cloud Resource Centerhelp.genesys.cloud
- Authenticated web messaging attributes – Genesys Cloud Resource Centerhelp.genesys.cloud
- Authenticated web messaging quick start guide – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure utilization at the agent level – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure an open messaging integration – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure and deploy Genesys Messenger – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure BYO SMS for SMPP – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure Messenger – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure email threading settings – Genesys Cloud Resource Centerhelp.genesys.cloud
- Create an SMS campaign – Genesys Cloud Resource Centerhelp.genesys.cloud
- Create an SMS campaign with MMS – Genesys Cloud Resource Centerhelp.genesys.cloud
- Deploy Messenger – Genesys Cloud Resource Centerhelp.genesys.cloud
- Disconnect or reroute inactive messaging conversations – Genesys Cloud Resource Centerhelp.genesys.cloud
- Email Agent Performance Detail view – Genesys Cloud Resource Centerhelp.genesys.cloud
- Email Agent Performance Summary view – Genesys Cloud Resource Centerhelp.genesys.cloud
- Email rate limits – Genesys Cloud Resource Centerhelp.genesys.cloud
- Get started with authenticated web messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- Get started with open messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- Get started with web messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- Guest session duration for web messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- Inbound email flows overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Manage your WhatsApp business account – Genesys Cloud Resource Centerhelp.genesys.cloud
- Manage ACD email routing – Genesys Cloud Resource Centerhelp.genesys.cloud
- Message Agent Performance Detail view – Genesys Cloud Resource Centerhelp.genesys.cloud
- Message Agent Performance Summary view – Genesys Cloud Resource Centerhelp.genesys.cloud
- Messaging threading timeline – Genesys Cloud Resource Centerhelp.genesys.cloud
- Migrate from web chat offers to web messaging offers – Genesys Cloud Resource Centerhelp.genesys.cloud
- Migrate from web chat to web messaging for digital user tracking and Predictive Engagement – Genesys Cloud Resource Centerhelp.genesys.cloud
- Monitor in-progress digital interactions – Genesys Cloud Resource Centerhelp.genesys.cloud
- Open messaging overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Park and resume a message interaction – Genesys Cloud Resource Centerhelp.genesys.cloud
- In-queue flows overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Register your domain and redirect inbound messages – Genesys Cloud Resource Centerhelp.genesys.cloud
- Regulations for long codes in outbound SMS campaigns – Genesys Cloud Resource Centerhelp.genesys.cloud
- SMS best practices for a compliant program – Genesys Cloud Resource Centerhelp.genesys.cloud
- SMS opt-out detection – Genesys Cloud Resource Centerhelp.genesys.cloud
- SMS messaging overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Switch channels for an interaction – Genesys Cloud Resource Centerhelp.genesys.cloud
- Use a WhatsApp template message – Genesys Cloud Resource Centerhelp.genesys.cloud
- Use the organization's email domain name – Genesys Cloud Resource Centerhelp.genesys.cloud
- Agent utilization – Genesys Cloud Resource Centerhelp.genesys.cloud
- Web messaging overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- WhatsApp Embedded Signup Flow overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- How do I migrate from legacy co-browse to the new co-browse for Messenger? – Genesys Cloud Resource Centerhelp.genesys.cloud
- Is the Web Messaging Guest session duration related to Threading Timeline? – Genesys Cloud Resource Centerhelp.genesys.cloud
- When configuring utilization, what is the maximum capacity for each interaction type? – Genesys Cloud Resource Centerhelp.genesys.cloud
- August 02, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- December 12, 2018 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- February 14, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- February 16, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- February 2, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- February 7, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- January 27, 2025 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- June 19, 2019 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- June 24, 2020 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- October 18, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- September 29, 2025 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- September 8, 2021 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Co-Browse – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Messaging – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys SMS and Email Notifications – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys SMS Routing – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Social Listening – Genesys Cloud Resource Centerhelp.genesys.cloud
- Limits – Genesys Cloud Developer Centerdeveloper.genesys.cloud
- Trial and sandbox limits – Genesys Cloud Developer Centerdeveloper.genesys.cloud
- Open messaging – Genesys Cloud Developer Centerdeveloper.genesys.cloud
- Generic file attachment (Messenger Transport Mobile SDK) – Genesys Cloud Developer Centerdeveloper.genesys.cloud
- Sending and receiving messages (Messenger Transport Mobile SDK) – Genesys Cloud Developer Centerdeveloper.genesys.cloud
- Genesys Cloud Platform API v2 definition (permission requirements per operation) – Genesysapi.mypurecloud.com
- Genesys Cloud CX summarised plan comparison – Genesyslibrary.genesys.com
Keep reading
More guides
Genesys Cloud recording, retention, redaction and subject access
A detailed handbook to Genesys Cloud recording: capture, policies, the retention ceiling, archive, redaction, secure pause, PCI, legal hold and subject access.
Read the guideGenesys Cloud routing explained: bullseye, conditional, preferred and predictive
How Genesys Cloud ACD routes interactions: evaluation and scoring methods, skills, bullseye, conditional group, preferred agent, predictive and utilisation.
Read the guideGenesys Cloud data actions: the integration handbook
A detailed handbook to Genesys Cloud data actions: integrations, contracts, Velocity and escaping, translation, credentials, limits, caching and failure.
Read the guide