SMS & text messaging

Genesys Cloud SMS reaches customers on the one messaging channel every mobile phone already has. No app, no account and no data connection are needed, which makes text messaging the most inclusive digital channel you can offer. Customers can ask a question without waiting on hold, reply to a reminder to reschedule, or confirm a delivery in seconds. For the contact centre, SMS absorbs simple contacts that would otherwise become calls and lets agents manage several conversations at once. QVCCS helps you identify which journeys suit SMS, from service conversations to proactive alerts, and where text should hand over to another channel.

SMS also carries responsibility. Messages arrive on a personal device, often with a notification, so relevance, timing and consent matter. Regulators and carriers in many countries set rules for how businesses send texts, which number types they use and how customers opt out. Getting this right protects your sender reputation and keeps messages being delivered. Our consultants work with your compliance, marketing and service teams to define what you will send, to whom, when and from which number, and document these decisions as requirements before any configuration begins.

Genesys Cloud supports SMS routing as a messaging channel, and SMS can be inbound conversations or outbound messaging campaigns. Long codes are standard DID or toll-free numbers, short codes are five- or six-digit numbers available as random or vanity codes, and alphanumeric sender IDs show a brand name as the sender where a country allows it. Numbers are purchased through Genesys Cloud, with regulatory documentation where a country requires it, or an existing provider account is connected through Bring Your Own SMS for Twilio or any provider with an SMPP interface. Each number is assigned to an Architect inbound message flow that can check hours, recognise keywords, call data actions, offer bot self-service and route to an ACD queue, and MMS adds image sharing.

Outbound use comes in two forms. Agentless SMS notifications are individual messages triggered by an event, such as an appointment reminder or delivery update, sent by your back-end systems through the API or from an Architect flow using a data action, with any reply routed back into Genesys Cloud as a conversation. SMS campaigns send messages to a contact list using campaign template messages, with MMS available, and the same compliance controls as other campaigns. Genesys Cloud treats standard keywords such as STOP and UNSUBSCRIBE as opt-out requests, and has announced broader phrase-based detection. Registration and sender verification rules vary by country and number type – the UK, for example, protects certain alphanumeric sender IDs – so they are planned early in every QVCCS engagement.

Number strategy shapes everything else. Long codes feel local and suit conversational service, short codes suit high-volume campaigns, toll-free numbers can serve both in some regions, and alphanumeric sender IDs build recognition for notifications. Availability, throughput, cost and registration rules differ by country, and a number already printed on letters or websites may need to be ported or kept in use; SMS does not automatically move with voice when numbers are ported. QVCCS assesses your volumes, regions and use cases, recommends the right mix, decides whether to buy numbers or bring your existing provider, and plans provisioning and registration so numbers are ready when the build is.

Consent and opt-out handling must be reliable. We design keyword handling for stop, start and help requests, align it with your consent records, and make sure campaigns and notifications respect opt-outs across every number. Message content is written to be short, clear and identifiable as coming from you, with links and personal data used carefully. We also agree which information may be exchanged by text at all, and when a conversation should move to an authenticated channel or a call, documenting these rules with your information-security team.

Routing design keeps SMS manageable. Texts are short and arrive in bursts, especially after a campaign, so we design queues, priorities and concurrency to absorb replies without overwhelming agents or starving other channels. Out-of-hours behaviour is defined so customers know when to expect an answer. We also plan how a texting customer is matched to a CRM record and how conversations appear in reporting, so leaders can see volumes, response times and outcomes for SMS alongside voice and digital channels.

SMS looks simple but touches carriers, regulators, consent records, campaign owners and back-end systems, so QVCCS musters a team from its own bench and owns the outcome end to end. A Senior Business Consultant / Business Analyst captures use cases, countries, volumes and consent rules. A Solution Architect owns the number strategy and the design for flows, routing, campaigns and notifications. An IT Systems, Telecoms & SIP Engineer is central to SMS, handling number provisioning, registration, porting and any Bring Your Own SMS connection, while a Senior Developer builds the flows, bots, data actions and notification integrations. A Systems Integration Tester proves every number type and country on real handsets, not just in a simulator.

The details that break SMS in production are rarely the obvious ones. A message with an accented character or emoji can switch encoding and split into more parts than expected; a reply to a campaign can arrive hours later on a number nobody now monitors; a customer who texts STOP to one number may expect to be removed from all of them. We write these cases into the requirements and the Interface Control Document for every system that triggers or receives texts, and the SIT pack sends long and special-character messages, unknown keywords, late replies and opt-outs across each number type. Launch then proceeds one number or use case at a time.

Once SMS is live, the work shifts to delivery and relevance. We review delivery, response and campaign results with you, refine templates and routing, and track regulatory, carrier and Genesys release changes through our release readiness review, such as new opt-out detection or sender ID rules. Registration obligations in some countries are renewed or tightened over time, so we keep a register of every number, its registration status and its owner. Support follows your Genesys Cloud CX support model, alongside your provider or under SLA with us, and the handover pack gives your administrators runbooks for templates, lists and day-to-day changes. As needs grow, SMS can be extended with bots and new notification journeys.