Genesys Social Media Routing (CE19) for Genesys Engage cloud

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Engage cloud Use Cases for version Current of Genesys Use Cases.
Read this topic for other versions:
Engage with your customers through social channels
    GenesysEngage-onpremises

Use Case Overview

Story and Business Context

In today's business landscape, customers want to connect with businesses in ways that are natural and intuitive. Social media channels are popular for customers to use to communicate and interact with companies due to their vast availability, influence, and convenience. Customers use social media to share information about products and services, and they frequently follow and review companies with whom they do business. Companies benefit from having an active, responsive, and positive social presence.


Genesys' powerful routing engine is intelligent enough to provide an automated response outside hours of operation or during an emergency or unforeseen closure. During normal hours, Genesys will distribute the social media interaction to the next available agent with the appropriate skill.

Use Case Benefits*

Use Case Benefits Explanation
Improved Brand Perception Responding to social posts publicly acts as a key factor in managing the organization’s reputation at scale.
Improved Employee Occupancy Better scheduling of agents to match demand (WFM solution required)
Improved First Contact Resolution Improved First Contact Resolution by routing interactions to an expert through skill-based routing
Improved Net Promoter Score Improved NPS by addressing customers' requests in a timely manner through skill-based routing. Ability to switch between Public and Private channels seamlessly.
Increased Revenue Route revenue-generating opportunities to best resources through skill-based routing
Reduced Handle Time Reduction of handle time by routing interactions to the correctly skilled agents through skill-based routing
*You can sort all use cases according to their stated benefits here: Sort by benefits

Summary

Provide consistent customer service across Twitter and Facebook communication channels by delivering interactions to the best available agent with social media public posts and private messaging. Agents are able to advise customers based on customer information and social media context. Standard responses enable your agents to provide consistent response to customers engaging via Facebook or Twitter.


Use Case Definition

Business Flow

Facebook/Twitter Interactions (Public and Private)

The following flows describe the use case from the perspective of the main actors, i.e. social media user and contact center agent. The first flow shows how a public interaction is handled is handled:

Business Flow Description

  1. The user searches in Facebook or Twitter for the company's account. User will post or tweet to the attention of the company, by posing a customer care issue.
  2. Genesys verifies if a corresponding contact already exists in Genesys contact history. The customer will be identified in the contact history by his Facebook / Twitter handle (if available).
    • If yes, then it will attach the interaction to an existing session.
    • If a contact does not exist (social handles are not associated to a registered user), Genesys creates a contact in the universal contact database based on the customer data. Any following messages and agent replies are stored under this customer.
  3. Genesys will check if the agent is available to take the interaction.
    • If the agent is available, then Genesys will create a new interaction for the agent to accept and continue/start the conversation
    • If no agent is available, the interaction is placed in the queue until an agent is made available. A new interaction is created for the next agent.
  4. When the agent is available, an open media pop-up for Public Interaction / a chat window pop up for Private Interaction will appear in Workspace Web for the agent to accept or reject the request. If this interaction is sent to a subscribed agent:
    • The agent will see a pop up to “Show/Deny” the message. If the agent denies it / timeout occurs, it will be placed in his communication panel queue to pull once the agent is available.
  5. Once the agent accepts the new interaction, the customer contact will be added into his subscription list to enable last agent routing for any future interactions.
  6. The interaction is sent to the agent for an appropriate response. Once the agent accepts, this session begins and will be alive until the agent has completed the conversation and decides to close the interaction. When the interaction is finished the agent can set a disposition code to register the outcome for reporting purposes.

Business and Distribution Logic

Business Logic

Engagement Scenarios

The following 4 scenarios describe typical social customer care engagement which have been used successfully.

Scenario 1: Twitter - @mention

This scenario depicts an engagement when the customer is tweeting to the company's handle. The customer uses their account to post a Tweet.Genesys Social Engagement captures this message according to predefined business logic. Customer profile details are received with the message through the Twitter API. The profile details are attached to the interaction. The Twitter message will be stored in the Genesys contact history.


The original incoming Twitter interaction is delivered to the agent desktop. The desktop identifies that this message was directed to the business and if the author is a follower of the business' Twitter account. The agent reads the incoming Twitter message and sends a public response/reply to the tweet. Alternatively, the agent can mark this interaction as “Done”, assign a disposition code and not take any further action.


The workflow creates an interaction an outgoing Twitter interaction and associates it with the same customer contact. Genesys Social Engagement sends the reply back to the customer.


Scenario 2: Twitter - Direct Message to Company

In this scenario, a customer is sending a private (or direct) message to a company's Twitter handle. Please note that this is only possible when one of the following conditions is satisfied:

  • The flag “Receive Direct Messages from anyone” is activated in Twitter (not recommended as this might result in a high volume of messages)
  • The customer is a follower of the company's Twitter account
  • A previous conversation was already established in the past to receive help

The user must be a follower of the company so that the company can send a direct message back. Therefore, non-followers are sent a follow request, e.g. “Please follow @Genesys for us to assist you”. This allows the company to assist customers over Twitter privately.

The tweet is stored in Genesys contact history as an outgoingTtwitter message and associated with the same contact Genesys Social Engagement sends the Twitter message to the customer. The customer sees the tweet and responds by following the @Genesys Twitter account.


The company then has a different choice of actions to perform, also according to what other channels are available for the agent and customer. If no other channel is available, the agent can reply to the direct message with the intended information and the interaction is closed.


Scenario 3: Facebook - post on Company's timeline (wall) or comment to post (Reply)

The customer uses his account to post a message on the company's timeline (wall) or posts a reply to a post from the company's timeline.

DigImplSocial10.pngGenesys Social Engagement queries this page's wall and finds the new post with comments. The query is run on a configurable timer (15 seconds by default). Genesys Social Engagement captures the message and creates an interaction. The interaction consists of an original post plus comments which are posted within the query's timeframe by the end user. Additional attributes describing the post author's and commentators' profiles are also part of the interaction structure.Each post/reply/comment comes in as an interaction. Every interaction from a customer will store the customer information in contact history.


The strategy stores the post including comments in Genesys contact history and associates it with the contact(s). NOTE: while the interaction representing the initial post and comments is in the queue, further comments could be added. The query could pick up these additional comments and create another interaction.


The Incoming Facebook interaction will be delivered to an agent. If the agent has subscribed to receive interactions from a particular customer, it will be routed to that agent.


The agent processes the incoming Facebook message and sends a response if required. Also he/she may mark this interaction as “Done” and not take any further actions. Genesys stores the message text of the outgoing Facebook interaction in Genesys Contact History for the same contact. Please NOTE: The outbound Facebook message will be a child of the original message. (Reply)


Scenario 4: Facebook - Private Messaging

Facebook Messenger can only be initiated by the end user. The user needs to invite the company to a chat session via the “Message” button on the main Facebook page.

DigImplSocial13.png

Genesys receives the Message request and distributes to an agent. The customer's public Facebook info is passed with the interaction request.


Screen Shot 2019-03-18 at 4.04.20 PM.png




The agent is alerted of an incoming message, indicating the interaction is with the Facebook customer. The agent accepts the interaction and begins a conversation with the customer. Genesys Social Engagement sends the reply back to the customer.



Rules of Engagement

Genesys Social Engagement can be configured to monitor either a specific account (=all interactions that are related to the account) or keywords (such as hashtags or specific words that are relevant to the social customer care task). Please be careful when specifying keywords as common words or hashtags may result in a large number of interactions that can impact the overall performance of the architecture. In addition to this, Twitter and Facebook have policies that might prevent or block the account from receiving all those interactions, or they might throttle message processing, if they receive too many processing requests, resulting in lost messages or delays in sending or receiving messages.



DigImplSocial17.png


Distribution Logic

Included as part of the Business logic.


Use Case Requirements

Customer Interface Requirements

Common browsers or mobile apps for social media sites.

Agent Desktop Requirements

The following lists the minimum requirements for the Social Engagement interfaces:

  • The agent desktop will be enabled to handle Social Media Interactions (Facebook & Twitter) supporting Genesys standard functionality.
  • Access to Universal Contact History.
  • Configuration of not-ready reason codes (e.g. Admin Work, Pause, Lunch, Meeting, Pause, RONA and Training).
  • Configuration of disposition codes (e.g. Cross Sell, Need Follow-Up, Not Right Skill, Processed, Terminated, Transferred, Up Sell).
  • Access to standard response library.

Reporting

Real-time Reporting

Pulse offers personalized dashboards based on specific functional, geographical, or organizational needs. Pulse dashboards present information using graphical widgets that can be viewed as graphs or tables, showing information about specific key performance indicators, such as service level, chat interaction handled, and average handle time. With Pulse you can:

  • Monitor the current state and activity of contact centre objects to help make decisions about staffing, scheduling, and call routing strategies.
  • Create widgets from predefined and user-defined templates for a fast and easy text or graphical presentation of selected or user-defined object statistics.
  • Use predefined templates to
  • Monitor operational Social activity through the Social Queue Activity template.
  • Monitor Agent resource activity through the Social Agent Activity template.
  • Monitor Tenant Service Level through the Social Service Level template.

DigImplSocial18.png

Historical Reporting

Interactive Insights or GCXI out-of-the-box reports:

  • Assess the day-to-day operations of the contact centre resources for the routing and handling of interactions.
  • Measure the effectiveness of the engagement rules and efficiency of the use case with the Customer Perspective Report and the Interaction Volume Customer Segment Report.
  • Dimension the out-of-the-box aggregate-based Interactive Insights reports with routing parameters including the engagement rules and the disposition codes.
  • With disposition codes, calculate the conversion success rate.
  • Evaluate resource performance with a variety of reports for Agents and Detail facts.

There are 40+ reports available.

Assumptions

General Assumptions

Customer Assumptions

  • Genesys Social Engagement is configured to handle interactions from the company’s Facebook page and Twitter account.
  • Provisions and configures standard responses in eServices Manager.

Interdependencies

All required, alternate, and optional use cases are listed here, as well as any exceptions.

All of the following required: At least one of the following required: Optional Exceptions
None None None None

Premise Assumptions

See Engage/CE19 Genesys Social Media Routing (CE19) for Genesys Engagefor Premise Assumptions.

Cloud Assumptions

  • Genesys CX Insights is the historical reporting application.
  • Pulse is the real-time reporting application.
  • Workspace Web Edition 9 is the agent desktop.

Related Documentation

Document Version

  • v 1.0.0