Genesys Email Routing (CE16) for PureConnect

From Genesys Documentation
Revision as of 19:29, June 5, 2019 by Bgrenon (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This is a draft page; the published version of this page can be found at UseCases/Public/PureConnect/CE16.
Route email interactions to the best skilled resource

What's the challenge?

When customers take the time to send an email, they expect a quick, personalized response. But as the volume of email interactions increases, you struggle to provide timely and helpful responses. Trust in email as a reliable communication channel is declining among your customers and employees.

What's the solution?

Automatically distribute emails to the best-fit agent based on content analysis and keywords. Genesys Email Routing streamlines your response process using email automation functionality that enables you to monitor, measure, and optimize your email flow to create a better customer experience.

[[Category:]]

Story and Business Context

Email is still one of the most reliable and desired ways for customers to interact with companies for support. It is an essential avenue for companies to serve and engage with customers while providing a consistent and positive customer experience. Genesys can improve handle time, first contact resolution, agent utilization, and customer satisfaction by automatically distributing emails to the best available agent based on content analysis and keywords, and automating acknowledgements and responses.


Use Case Benefits

Use Case Benefits Explanation
Improved Customer Experience Addressing customers requests in a timely manner through skills based routing improves Net Promoter Score
Improved Employee Utilization Blending email with voice and chat allows agents to make better use of downtime between calls and chats to improve employee occupancy.
Improved First Contact Resolution Directing interactions to an expert through skills based routing improves First Contact Resolution
Reduced Handle Time Reduce handle time by routing emails to agents with the right skills

Summary

A customer sends an email to a company email address. The email is captured by the Genesys system and a content analysis is performed. It is then queued to the best available agent with the corresponding skill set. Priority tuning functionality can improve the service level adherence to customer's emails. The reporting functionality of this use case provides management visibility into the email interaction channel to drive further improvements.


Use Case Definition

Business Flow

The following diagrams show the business flow of the use case:

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

  1. A customer sends an email to one of the public addresses (e.g., orders@abc.org) monitored by the Genesys email solution.
  2. Genesys periodically checks corporate inboxes for new emails. Genesys analyzes the email to capture From, To, Subject, and body content as metadata.
  3. Conversation tracking option: Genesys verifies whether the corresponding user already exists as a contact within the Tracker system (by email address). Tracker is an additional, licensable product. The email and any agent responses are attached to the contact.
  4. The system checks whether the email is new or a reply.
    1. In case of a new email, the system classifies the email based on keyword analysis (see the Keyword Categorization section).
    2. In case of a reply email from the customer, the system attempts to route it to the previous workgroup (see details in the Distribution Logic section). After a timeout, the system routes the email to the originally specified workgroup.
    3. In case of an automatically generated reply email, the email will not be distributed to an agent and the flow will stop.
  5. The system sends out a receipt acknowledgement email to the customer with a predefined template for the To address.
  6. Once an agent with the requested skill is available, the email is routed to the agent's desktop with a screen pop from the email editor displaying the content.
  7. Once the agent reads the email, he or she decides whether a reply is needed.
    1. If no reply is needed, the agent marks the email as done.
    2. If a reply is needed, the agent creates an outbound reply email, potentially using a standard response template.
  8. The agent sets a disposition code to mark the business outcome for reporting purposes.



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.