Genesys SMS Routing (CE29) for GenesysCloud

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Cloud Use Cases for version Public of Genesys Use Cases.
Read this topic for other versions:
Route SMS interactions to the best resource

What's the challenge?

Your customer wants to contact you in the same way they would friends and family — instantly, conveniently, and personally, with freedom to keep moving. If they encounter constraints, excessive hold times, inconsistent responses or multiple calls, that can damage customer satisfaction and put a strain on your agents.

What's the solution?

Connect a customer to the right resource anywhere in your business by routing customer text messages to your best-fit agents. Genesys SMS Routing uses skill-based routing so messaging your company for support is faster and more efficient than calling and enables conversations from anywhere.

Story and Business Context

In today’s digital world, customers want a simple, convenient method of communication through their preferred channel at a time that meets their schedule. More often, customers choose asynchronous channels, such as SMS, for the convenience it provides. Using SMS, customers can avoid calling and waiting on hold for an available agent. SMS also allows customers to engage "on the go" without a dedicated mobile app. Also, because customers engage by SMS at faster rates than any other messaging channel, the organization can resolve issues more quickly.

Use Case Benefits

Use Case Benefits Explanation
Improved First Contact Resolution Routing interactions to an expert through skills-based routing.
Increased Revenue Routing revenue generating opportunities to best resources through skills-based routing.
Reduced Handle Time Routing of SMS messages to the right skilled agents through skills-based routing. Defer work to a later time when traffic volumes are not as significant.
Reduced Interaction Transfers Reduce interaction transfers through skills-based routing.

Summary

A customer sends an SMS message to a company. The Genesys system receives the SMS message and routes it to the appropriate messaging flow for processing. The messaging flow allows customer to potentially perform a data dip that enriches the available data about the SMS conversation. Based on decisions made in the flow, the system eventually transfers that data to a queue. The system then queues the SMS message to the best available agent who has the skill set that corresponds to the skills requested in the flow. When an agent becomes available, the system routes the conversation to the agent by ACD, just like any other media type. The agent answers the message, reviews the message contents, and replies from within the Genesys Cloud interface. The agent can keep the message open and use SMS like a chat channel, or close the SMS message after replying. If the agent keeps the conversation open, the system immediately displays each customer response to the agent, using SMS messages as a chat channel. If the agent closes the conversation but the customer replies within 72 hours, the conversation reopens (after 72 hours, the system creates a new conversation) and routes to the last agent that handled the SMS. If that agent is unavailable, the system routes the message by ACD to the next available agent. After the conversation ends, it may pass to a Quality Evaluator, who scores the conversation. As part of the SMS messaging channels, supervisors can view SMS traffic in all the analytics dynamic views.


Use Case Definition

Business Flow

The following flow describes the use case from the perspective of the main actors, i.e. user and contact center agent.

Business Flow Description

  1. A customer sends an SMS to a company long code or toll-free number.
  2. Genesys Cloud receives the SMS message, including the customer's phone number as metadata.
  3. Genesys triggers an Architect inbound message flow for the incoming SMS message.
  4. The Architect flow attempts to recognize the customer by performing a search in External Contacts or external data source (optional).
  5. The inbound message flow performs routing decisions based on the data returned from External Contacts (or External Data source as an option) and also based on message content analysis and keywords
  6. When an agent within the queue is available, the SMS message routes to the agent. A screen pop displays related SMS information. Relevant conversation information appears in the agent script. The agent receives full context of the SMS conversation.
  7. The agent reads the SMS message and determines if a reply is necessary.
    1. If reply is not necessary, the agent disconnects the SMS and assigns a wrap-up code that indicates a response is not necessary.
    2. If a reply is necessary, the agent replies in the chat window, potentially using a standard response template.
    3. If they expect the customer to respond quickly, the agent can leave the conversation open. If not, they can close the conversation.
  8. When the conversation closes, the agent sets a disposition code to mark the business outcome for reporting purposes after the interaction disconnects.



For more details

For additional details, contact your Genesys Sales Representative by filing out the form or for immediate assistance call us: 1-888-Genesys.