Genesys Lead Engagement (SL05) for GenesysEngage-onpremises

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Engage on-premisess Use Cases for version Public of Genesys Use Cases.
Read this topic for other versions:
Enrich, prioritize and distribute missed conversion opportunities

What's the challenge?

You need your team to get more conversions in less time. But when leads don’t get to the right rep in real time, or have assigned value, priority or customer context, it’s hard for that rep to successfully convert. And missed conversions mean missed revenue opportunities.

What's the solution?

Create a single, global task list that automatically organizes, prioritizes and routes captured leads (with context) to the best qualified rep anywhere in your company. Eliminate “cherry-picking” and misrouting, so reps can process leads faster and more efficiently, for better resource planning and conversion rates.

Story and Business Context

This functional use case has been created to enable Genesys customers to leverage the back office automation capabilities to manage their high value leads coming through their web or e-commerce sites or other external databases or lead sources. By using automated work distribution to capture, classify, prioritize and deliver the leads to appropriately skilled and available resources, companies can improve their lead conversion rates and throughput.

The ability to define business logic drives the proper prioritization and distribution of leads between the available resources and will therefore disable the “cherry picking” of leads and balance out the interactions between the available resources fairly and equally. Leads can be prioritized (and continuously re-prioritized) based on multiple business parameters as lead capture date, expected lead value, customer segment, change to convert, etc.

The history of the lead and the additional context information around the leads can be pushed together as one work-item and allows the sales enabled resources to understand what has happened in the past and assess the current status of the lead. Having more relevant and recent information available around the leads increases the chance for conversion by delivering more insights to the sales resources to figure out the best approach how to handle the leads in different circumstances.

Additional Context

The following diagram shows how iWD can improve Lead Management through the use of dynamic prioritization and delivery:

Lead Handling without Prioritization

The above diagram shows how leads arrive into an enterprise; the leads are treated on a FIFO basis, whereby the available resources address the next lead in the queue. With iWD, prioritization rules are applied to "sort" the leads by value, to ensure that the fixed available resources always deal with the highest value and important leads. Leads are re prioritized overtime to ensure that time parameter is also taken inconsideration in the prioritization of the leads.

Lead Handling with Prioritization

Genesys iWD can provide high value lead management by the following capabilities:

Lead Grading

  • Genesys iWD solution is responsible for the capture, classification, prioritization of leads. The powerful Genesys Rules Engine defines and sorts the leads according to the business imperatives laid down by the business and supported by IT. This lead sorting is reviewed at regular time intervals to stay aligned with these Business imperatives. This means business users will manage the outcomes of the processing logic by changing or implementing business rules, through a simple business friendly GUI.

Lead Distribution

  • In addition to the capture and prioritizing of leads, Genesys Enterprise Workload Management solution is also responsible for delivering the leads to the correct resource at the right time in order to convert the lead to a sale. This solution leverages the Genesys core routing engine to the back or front office, identifying the available resources with the required skill set and targeting the most urgent lead to that resource.

Benefits of iWD Lead Management

  • Visibility into how leads are processed by employees
  • “Managing” items for telesales and marketing rather than relying on people to choose their leads to work on
  • Rigorously applying skills-based routing to match lead types to the right skilled resources
  • Prioritizing and Re-Prioritizing leads based on various business rules
  • Dynamically matching the demand of leads with the supply of skilled resources throughout the day
  • Providing visibility through real-time and historic metrics

Use Case Benefits

Use Case Benefits Explanation
Improved Employee Occupancy Prioritizing and presenting leads to sales reps reduces idle time, increases throughput and improves their utilization.
Improved Employee Satisfaction Automatic prioritization and distribution of leads prevents "cherry picking" and ensures fairer distribution of leads among team members.
Improved Net Promoter Score Automation of lead follow-up ensures faster responses to prospects, improving their experience.
Increased Revenue Value-based prioritization speeds up response times for important leads, increasing conversion rates and revenue.
Reduced Administration Costs Automatic lead distribution reduces time spent by supervisors and administration staff in monitoring, distributing and reporting on leads.
Reduced Handle Time Easy access to lead context speeds up familiarisation and handle time for sales reps.


A lead is shopping on the web site and abandons his shopping cart. These interactions are captured by the Web Site and delivered to the iWD solution as a "hot lead". The lead is captured from the Web Site, and then placed into the universal queue with a priority defined by the size of the shopping cart, the value of the product/ service and/or by any other information known about the lead (mobile customer segment etc.), the distribution of the lead to lead development representatives could be blended with voice calls. The lead is then continuously reprioritized based on business rules, which define the SLA. All voice / non-voice interactions are distributed to the best skilled lead development representative respecting their SLAs.

Use Case Definition

Business Flow

Lead Capture (out of scope for the use case)

Lead Capture (out of scope for the use case) The logic, which triggers the creation of a lead within Genesys, depends on the web site and is out of the scope of this use case. When a lead is detected logic on the company web site or lead capture system will create a new lead within Genesys. A typical scenario is an abandoned shopping cart event as is shown in the following diagram:

Business Flow Description Lead Capture (out of scope for the use case)

  1. A lead browses the web site of the company.
  2. He is identified using a lead management system or himself by using his customer account or by providig further information on the web site.
  3. He places one or multiple items in his shopping card. If he proceeds to check-out, no further action occurs.
  4. If he does not proceed with his buying process or closes the browser, a lead is generated. All relevant data is collected by the web site and the lead is created in Genesys for distribution to a lead development representative.

Business Flow

Business Flow - Distribution

The following diagram shows the business flow of the use case:

Business Flow Description Business Flow - Distribution

  1. A new lead is created in the system with all attached data necessary to process the lead (see chapter “Attributes”).
  2. The web site creates a new task in Genesys via one of the Genesys capture adapters.
  3. The interaction is classified and prioritized according to specific lead rules and the business value of the lead.
    • The rules are applied according to the lead attributes.
    • If the lead comes from a non-authenticated customer (with only contact details available), then the value of the basket (or potential sales item) or product category are used to calculate the priority and/or business value.
    • If the lead is a known customer (authenticated in the web site), then additional customer attributes could be used for the prioritization process.
    • The leads are reprioritized in certain periods of time if the lead is not distributed to a lead development representative before.
  4. The lead is queued with all other interactions in the system. The priority of the lead defines the position of the lead in the universal queue. Once a lead development representative with the right skill becomes available to handle the lead, the lead is distributed to the lead development representative. If it is not assigned within a specified period of time, it is re-prioritized.
  5. If the lead is assigned to a lead development representative, the lead development representative will open the lead in the Workspace Desktop to manage and/or complete the interaction. The lead development representative desktop will display reference data to the lead (see section “Data presentation to a lead development representative”) and the associated contact details.
  6. The lead development representative will handle the lead and attempt to call the lead using the provided contact data.

Business Flow

Business Flow - Lead Handling

Business Flow Description Business Flow - Lead Handling

  1. The lead development representative will make an outbound call to the customerlead to convert the sale. There could be various results from this call attempt
  2. Lead is reached:
    • The lead development representative reaches the lead and attempts to convert the sale.
    • After the call he records the result for reporting purposes (converted, not converted).
    • He finishes his work on the sale via the desktop (“mark done”) and the lead progresing to onboarding as a customer.
  3. Call needs to be rescheduled.
    • The lead development representative reaches the lead, but the lead wants to have the conversation at a different time.
    • The lead development representative reschedules the call to a specific date and time via his lead development representative desktop and finishes his work on the lead.
    • The system will check if the maximum number of reschedule attempts are reached.
      • If not, the lead is prioritized and queued again when the rescheduled date and time is reached.
      • If yes, the lead will automatically be completed with call result = “max rescheduled”
  4. Lead cannot be reached
    • In this scenario, the lead development representative cannot reach the lead.
    • He sets the corresponding result and finishes his work on the lead (“mark done”).
    • The system will check if the maximum number of call attempts are reached:
      • If not, the lead is automatically rescheduled within 2 business hours. When the rescheduled time is reached, the lead is prioritized and queued again.
      • If yes, the lead will automatically be completed with call result = “no answer”.

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.