Difference between revisions of "UseCases/Current/GenesysCloud/OP02"
(Blanked the page) |
|||
Line 1: | Line 1: | ||
+ | {{SMART UseCase | ||
+ | |ID=OP01 | ||
+ | |Title=Genesys Business Communications | ||
+ | |Offering=PureCloud | ||
+ | |SMART_Benefits={{SMART Benefits | ||
+ | |UCBenefitID=Reduced Administration Costs | ||
+ | |UCBenefit=A single, all-in-one platform approach enables you to better control communications while reducing costs. The PureCloud solution centralizes omnichannel processing, system configuration, administration, and reporting, while also consolidating multiple vendors to one. Wizard-driven DIY administration eases time and effort to set up and manage. | ||
+ | }}{{SMART Benefits | ||
+ | |UCBenefitID=Reduced Deployment Costs | ||
+ | |UCBenefit=The cloud platform provides fast deployment and provisioning through the ability to auto-sync users from your HR record system, and cost-saving WebRTC softphones vs. expensive hardphones. Continuous deployment enables fixes and features to be rapidly and automatically delivered—without a heavy upgrade process or downtime. A scalable cloud architecture enables simple, straightforward, and cost-effective pricing. Instantly deploy new users as needed, when needed – wherever they’re located. The reliable, integrated application suite eliminates unstable voice processing cards and all the points of potential failure that come with multi-system configurations. | ||
+ | }}{{SMART Benefits | ||
+ | |UCBenefitID=Reduced IT Operational Costs | ||
+ | |UCBenefit=The platform provides cost-effective omnichannel customer service calls, email, chats, text, and social media to handle all types of communications quickly and consistently. The streamlined real-time monitoring and end-to-end reporting capabilities make it easy to ensure service quality across channels. Applications for outbound campaigns and workforce management complete the solution. The platform supports open interoperability and eliminates vendor lock-in to proprietary hardware. Customers can take advantage of the platform to openly integrate with third-party cloud or premises PBX – or just use the built-in features. The platform also integrates easily to databases, web services, messaging platforms, business apps, CRM and ERP packages, and SIP devices, including gateways, telephones, and headsets. Desk phones are no longer necessary. Users are able to break free of location and hardware restraints and reduce business communications costs with a simple softphone. Users can make and take calls with just a browser and the Internet. | ||
+ | }} | ||
+ | |UCOverview=Companies want to reduce complexity, simplify administration, improve efficiency, and reduce total cost of ownership. They need a single platform that empowers both contact center and business users. The combination of customer experience management and business communications gives customers a unified all-in-one solution. | ||
+ | Companies no longer want to deal with multiple cobbled-together communications solutions. These solutions require more resources to deploy and maintain, increase cost of ownership, and leave the business constantly context-switching without a good way to collaborate across teams and business units. Customers and employees are too important to just maintain the status quo. | ||
+ | |||
+ | With a unified platform, enterprises smartly connect departments, workgroups, contact centers, branch offices, and remote and mobile workers. The unified platform combines a contact center solution with traditional business telephony functionality, speech-enabled auto-attendant, and real-time collaboration features. For example, video conference, screen share, dynamic team chat, presence management, corporate directory, and document management. | ||
+ | |||
+ | In keeping with multi-modality requirements, companies must equip their employees, especially sales force and field organizations, with mobility-based applications that give them the same functionality as their in-office counterparts. This functionality includes a company-wide directory with real-time presence and geolocation indicators, call controls and voicemail, find-me/follow-me, video and voice conferencing, ad hoc call recording, and unified messaging. Employees must also have access to contacts and communications from anywhere, on any device—including native mobile applications. Selecting a unified platform that supports traditional and digital communication capabilities can bridge the gap between the contact center and the rest of the business, and become a competitive advantage. | ||
+ | |UCSummary=This use case offers basic PBX functionality, together with rich collaboration features. Features include: | ||
+ | * IP PBX call processing | ||
+ | * Auto-attendant | ||
+ | * Desktop phone features | ||
+ | * WebRTC softphone | ||
+ | * Real-time presence management | ||
+ | * On-demand call recording | ||
+ | * Voice and video conferencing | ||
+ | * Screen- and file-share | ||
+ | * Corporate and workgroup directories | ||
+ | * Instant messaging | ||
+ | * Voicemail and unified messaging | ||
+ | * Document management | ||
+ | * Multilingual support | ||
+ | This complete functionality is built into the PureCloud Communicate license, available as low as $19.99 per user per month (with annual prepay). PureCloud Communicate complements the contact center sales: lead with contact center and evaluate back office opportunity for business users. | ||
+ | |PainPoints=* The customer's current enterprise PBX is no longer under warranty. | ||
+ | * There is uncertainty whether current infrastructure is being maintained by the manufacturer. | ||
+ | * The customer is spending too much money maintaining outdated equipment. | ||
+ | * The customer has to outsource support for an enterprise PBX. | ||
+ | * The customer owns multiple siloed PBX platforms. | ||
+ | * Existing PBX is managed and maintained as a solution separately from PureCloud. | ||
+ | * Existing PBX does not easily scale. | ||
+ | * The customer manages separate, siloed applications and vendors for employee collaboration (eg, directory, chat, video, document management). | ||
+ | |DesiredState=* Add enterprise users onto the PureCloud infrastructure that the customer currently uses for contact center. | ||
+ | * Allows single source of administration and support. | ||
+ | * Software revisions are released consistently to provide continuous innovation to PureCloud business communications features. | ||
+ | * Support and maintenance for both PBX and contact center is consolidated into one platform. | ||
+ | * PureCloud Communicate greatly reduces overall solution complexity which makes it easier to use and manage. | ||
+ | * Supports growth through simple licensing to deliver exactly what the customer needs when needed. | ||
+ | |BusinessImageFlow={{SMART BusinessImageFlow | ||
+ | |BusinessFlow=Inbound PBX Call or Call to a Business User | ||
+ | |BusinessImage=https://www.lucidchart.com/documents/edit/bbafce35-04a3-45a3-b53f-cd34a52e4704/0 | ||
+ | |BusinessFlowDescription=Call options provided | ||
+ | # <span class="inline-comment-marker" data-ref="b73c6ed7-4758-4058-ae3a-3d3508072d55">The call routes to a business user via Direct Inward Dial (DID) ''See flow at bottom for Company Directory example.''</span> | ||
+ | # The business user uses the client to pick up the call. | ||
+ | ## If the business user has find-me/follow-me configured, the call routes to the configured forward number. | ||
+ | ## If the business user does not pick up either at the desktop client or at the find-me/follow-me number, the call goes to voicemail. | ||
+ | # Unified communications provides notification of pending voicemail. | ||
+ | ACD user connects to Business user via chat | ||
+ | # The ACD user searches Directory to find a SME (based on name, department, title or skills). | ||
+ | # The ACD user reaches out to the back office SME via chat tool. | ||
+ | ACD user connects to Business user via video | ||
+ | # The ACD user searches Directory to find a SME (based on name,department, title or skills). | ||
+ | # The ACD user initiates an internal video and receive product training via screen share tool. | ||
+ | ACD user connects to Business user via mobile application | ||
+ | # The ACD user can still reach Business users in the field via mobile device. | ||
+ | The Company Directory feature allows customers to call an IVR and say the name of the PureCloud user they want to reach. | ||
+ | # Customer contacts a PureCloud user that does not have a DID (or they do not know the DID). | ||
+ | # Customer calls the main IVR # and says the name of the PureCloud user they want to reach. | ||
+ | # The system automatically connects the caller to the PureCloud user. | ||
+ | # Notes:"https://help.mypurecloud.com/articles/enable-company-directory-support-menus/" | ||
+ | }}{{SMART BusinessImageFlow | ||
+ | |BusinessImage=https://www.lucidchart.com/documents/edit/641536f4-a37b-4508-a839-03f2766cb40a/0 | ||
+ | |BusinessFlowDescription=ACD user connects to PBX user | ||
+ | |||
+ | |||
+ | 1. The ACD agent reaches out to a subject matter expert in the enterprise. | ||
+ | |||
+ | 2. The ACD user sees the status of the subject matter expert in the client. | ||
+ | |||
+ | 3. The ACD user performs a warm-transfer to the subject matter expert. | ||
+ | }} | ||
+ | |BusinessLogic=N/A | ||
+ | |DistributionLogic=An ACD agent connects to a PBX user (e.g., Subject Matter Expert/SME). The PBX user/SME can be a remote agent working from a satellite location or from home. In either case the ACD agent would see the status of the SME and be able to warm transfer the customer call. | ||
+ | # The ACD agent needs to reach out to a SME in the enterprise. | ||
+ | # The ACD agent can see the status of the SME in the client. | ||
+ | # The ACD agent can perform a warm-transfer to the SME. | ||
+ | ACD user connects to business user via chat | ||
+ | # The ACD agent reaches out to a SME in the enterprise. | ||
+ | # The ACD agent sees the status of the SME in the client. | ||
+ | # ACD user reaches out to the back office SME via chat. | ||
+ | ACD user connects to business user via video | ||
+ | # The ACD agent reaches out to a SME in the enterprise. | ||
+ | # The ACD agent sees the status of the SME in the client. | ||
+ | # ACD user reaches out to back office SME via video. | ||
+ | ACD user connects to business user via mobile application | ||
+ | # The ACD agent reaches out to a SME in the enterprise. | ||
+ | # The ACD agent sees the status of the SME in the client. | ||
+ | # ACD user can still reach business users in the field via mobile device. | ||
+ | The Company Directory feature allows customers to call an IVR and say the name of the PureCloud user they want to reach. | ||
+ | # Customer contacts a PureCloud user that does not have a DID (or they do not know the DID). | ||
+ | # Customer calls the main IVR # and says the name of the PureCloud user they want to reach. | ||
+ | # The system automatically connects the caller to the PureCloud user. | ||
+ | # Notes: https://help.mypurecloud.com/articles/enable-company-directory-support-menus/. | ||
+ | |CustomerInterfaceRequirements=N/A | ||
+ | |AgentDeskRequirements=See the PureCloud Installation and Configuration Guide: [https://help.mypurecloud.com/articles/purecloud-apps/ https://help.mypurecloud.com/articles/purecloud-apps/.] | ||
+ | |||
+ | '''Web app''' | ||
+ | |||
+ | Access your PureCloud account from almost any computer with the web app. Use a web browser, such as Chrome or Firefox, to log on to PureCloud without downloading an app. | ||
+ | |||
+ | '''Mobile apps''' | ||
+ | |||
+ | Use the mobile app to stay connected to your org directory and chats, even when you are away from your office. We offer apps for iPhone and Android phones. | ||
+ | |||
+ | '''Desktop app''' | ||
+ | |||
+ | Keep PureCloud separate from your browser and other work with the desktop app. The desktop app allows you to open PureCloud automatically at startup and run it in the background. Download the desktop app for Windows or Mac. | ||
+ | |RealTimeReporting=Due to the continuous evolution, the features available in PureCloud change rapidly. Please see the PureCloud Resource Center for latest features at http://help.mypurecloud.com. The following are examples of PureCloud historical and real-time views that provide relevant insights: | ||
+ | |||
+ | Business User Reporting | ||
+ | * Interactions. The Interactions view provides detailed information on both historical and real-time interactions. | ||
+ | |||
+ | * Call Detail Reporting (if leveraging voice from Genesys Telecom). This report tracks your organization’s consumption of PureCloud Voice services, including information about call origin and destination, and the type of call. | ||
+ | |||
+ | Contact Center Reporting | ||
+ | * Agent | ||
+ | |||
+ | * Agent views provide metrics on agent status, agent performance, agent interactions, and other metrics to understand agent activity. Filters include skills, languages, wrap-up codes, and more. | ||
+ | |||
+ | * Queue | ||
+ | |||
+ | * A number of views provide insight into both real-time and historical queue activity. | ||
+ | |||
+ | * The Queue Activity view shows real-time metrics, including all calls that are currently waiting on and interacting with agents. | ||
+ | |||
+ | * Reports | ||
+ | |||
+ | * PureCloud has a full library of canned reports available in PDF and XLSX formats. | ||
+ | |||
+ | * Supervisors can filter these reports by dates, users, queues, and more. | ||
+ | |||
+ | * Supervisors can download reports from the PureCloud user interface. | ||
+ | |||
+ | * Supervisors can schedule reports to run and download in batch. | ||
+ | |||
+ | * Other views include, but are not limited to: | ||
+ | |||
+ | * WFM | ||
+ | |||
+ | * Quality | ||
+ | |||
+ | * Outbound | ||
+ | |||
+ | * Scheduled Callbacks | ||
+ | |||
+ | * Campaigns | ||
+ | |HistoricalReporting=N/A | ||
+ | |SMART_HybridAssumptions={{SMART HybridAssumptions | ||
+ | |Hybrid_Assumption=ver 1.0.0 | ||
+ | }} | ||
+ | |GeneralAssumptions=* The customer is an existing PureCloud customer. | ||
+ | * Voice option has been setup and configured under [https://repository.docs.genesys.com/UseCases/Draft/PureCloud/OP04 Draft Genesys Voice Services (OP04) for PureCloud] | ||
+ | |CustomerAssumptions=N/A | ||
+ | |Optional=OP04 | ||
+ | |SMART_PremiseAssumptions={{SMART PremiseAssumptions | ||
+ | |Premise_Assumption=There are no premises-specific assumptions. | ||
+ | }} | ||
+ | |SMART_CloudAssumptions={{SMART CloudAssumptions | ||
+ | |Cloud_Assumption=The customer is an existing PureCloud customer. | ||
+ | }} | ||
+ | }} |
Revision as of 10:49, January 8, 2019
What's the challenge?
CRM information and the contact center traditionally been silo'ed, but they don't have to be. The contact center can leverage integrations to the CRM to provide a superior customer experience and more efficient handling of calls through improved routing decisions and the surfacing of critical context to the agent as the call is delivered to them.
What's the solution?
Using information stored in the CRM regarding your customer and their prior interactions with your business can be used to great effect by the Contact Center. Data enabling your IVR allows for the customer experience to be more personalized, addressing the caller by name and confirming critical information prior to reaching an agent. Lastly, the information gathered from the CRM can be surfaced directly to the agent.
Contents
Use Case Overview
Story and Business Context
CRMs and the contact center often coexist, serving as complimentary pieces to the customer experience puzzle. The contact center can use information stored in the CRM about your customer and their prior interactions with your business to provide a more personalized, meaningful, and effective customer experience. Data enables your IVR to make the customer experience more personalized, addressing the caller by name and confirming critical information before they ever reach an agent. This data can also be used to make advanced routing decisions, steering the customer to the appropriate queue to handle their inquiry. Once a queue is chosen, the system selects the appropriate skills an agent in that queue should have to properly handle this inquiry. The system provides the ACD engine all the facets it should consider when making a routing determination. Lastly, the information gathered from the CRM can be surfaced directly to the agent when they receive the call. The agent will have all the necessary context to quickly and efficiently handle the call.
Use Case Benefits*
The following benefits are based on benchmark information captured from Genesys customers and may vary based on industry, lines of business or Genesys product line:
Use Case Benefits | Explanation |
---|---|
Improved Customer Experience | Personalize IVR experience and improve routing efficiency creating an improved overall customer experience. |
Improved First Contact Resolution | Improved FCR by enabling more intelligent routing. |
Reduced Handle Time | Reduced handle times by providing critical interaction context directly to the agent desktop |
Summary
Genesys Cloud CX supports out of the box integrations for Salesforce, MS Dynamics CRM 365, and Zendesk. Genesys Cloud CX also supports a “generic” integration that connects to a wide range of REST and GRAPH APIs. For more information, see: https://help.mypurecloud.com/articles/requirements-for-the-data-actions-integration (web services tab).
Use Case Definition
Business Flow
Business Flow Description
Business Flow Description
- Call enters the IVR.
- Based on the customer's phone number, the data action searches for records in the CRM.
- 2a Caller is identified. CRM record types can include contacts, accounts, cases, custom objects, etc.
- 2b Caller is not identified. If the caller is not identified based on phone number, the customer can be prompted for other identifying information to locate the contact.
- Caller is addressed by name.
- Key information from the CRM record is used to make routing decisions and select the appropriate queue.
- Examples: Subscription level, priority account, products purchased, and NPS.
- Examples: Subscription level, priority account, products purchased, and NPS.
- Information from CRM record is used to set up to five skills required to handle the interaction.
- Examples: Language, product knowledge, and account retention specialty.
- Reference to the CRM record is attached to the interaction using a Set Participant Data action.
- The ACD system routes to the available agent with the designated skills in the selected queue.
- Agent is presented with the call in a client embedded inside their CRM.
- Alerting call includes information the agent needs to begin the conversation.
- Examples: Queue call in on, skills on the interaction, subscription level.
- Alerting call includes information the agent needs to begin the conversation.
- The agent answers call using client embedded inside the CRM.
- The embedded client performs screenpop to the CRM record used in the IVR.
Business and Distribution Logic
Business Logic
Distribution Logic
- Install the data action integration relevant to your CRM:
- Configure and test your data actions:
- Add the data action to your call flow:
- Install the CRM integration from AppFoundry:
User Interface & Reporting
Agent UI
There are two methods to deliver a screen pop, either use an agent script or agent UI embedded into the CRM.
Reporting
Real-time Reporting
There is no applicable content.
Historical Reporting
There is no applicable content.
Customer-facing Considerations
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 |
Customer Responsibilities
- Customer has a CRM.
- Assumes CRM has web service endpoints to access records.
- Assumes they are not using sensitive data to make routing decisions.
Document Version
- Version V 1.0.2 last updated January 8, 2019