Report Abandoned calls in Routing Strategy

Last month, I attended workshop from Genesys and BT  and found an interesting trend. One of the customer shared that they were able to customer satisfaction and revenue by tracking and linking customer journey through multiple channels. For example, if customer selected products online for purchase and initiates call, they were able to link this and able to provide service. Simple and effective strategy.

Linking transactions across multiple channels is very big & interesting topic and will restrict to only voice channels in this post.

From my experience, I observed that many companies focus on active and answered calls by agent only. For example, C-SAT (Customer Satisfaction) survey are sent to customers which were answered by agent. What happens to customer disconnecting the call while waiting in queue? Most likely, these people are either looking for new service and simply switch to other provider. Others are left with no other option than wait 🙁 Imagine the potential loss of new customers and revenue..

In this post, I will explain how to record abandoned calls for reporting from the strategy (Francesc – Thanks for sharing this idea).

  • Database – Create Stored Procedure and Table
  • Configure DAP in CME
  • Create routing strategy for Abandoned Calls
  • Modify existing strategy to record abandoned calls

Database – Create Stored Procedure and Table


In my environment, I made decision to record ANI, DNIS, Conn ID and Timestamp and in most cases, it is sufficient for analysis or to schedule call backs.

Script to create table ‘CallDetails’

Script to create stored procedure ‘SP_UpdateCallDetails’

 Configure DAP in CME


Using Genesys Administrator or Configuration Manager, create new DAP ‘CustomDAP’ to point to reporting database

Create routing strategy for Abandoned Calls


  • Open IRD and create new routing strategy ‘RecordAbandonedCalls’ as below

Routing Strategy to store abandoned calls

Routing Strategy

  • In function block, store Conn ID, ANI and DNIS values into variables varConnID, varANI and varDNIS
  • In database block, select ‘Custom DAP’  which was created in first step, select stored procedure and follow the wizard
  • In stored procedure screen, enter name as ‘sp_updatecalldetails’ and add arguments as below
    • Key = @varConnID and value = varConnID
    • Key = @varANI and value = varANI
    • Key = @varDNIS and value = varDNIS
  • Click next and select ‘Do not use output values’

Modify existing strategy to record abandoned calls


In main strategy, add new function block after Entry and Target block as below

OnCallAbandoned

OnCallAbandoned

Make test call and abandon it while waiting in queue. Now, you can see records in the database .You can use these records to create calling list for outbound campaign or schedule callback 🙂

(Visited 7 times, 1 visits today)

Tagged: ,

Leave a Reply

Your email address will not be published. Required fields are marked *