Forwarding a call to another queue if agents are available (V2)

Do you have a specialized service queue with very few agents or agents that are engaged in long and extensive calls? Is that the reason why your customers sometimes have to wait before another agent is free?

There are multiple options to improve customer experience, for instance giving the customer the option for a callback or to leave a voicemail (for a callback you will need to create an input reader - find out more about this topic in this article).

Another possibility is to enable call-overflow. In the scenario we want to discuss today, we would like to forward a customer to another department. But we want to offer this option only if a representative in the other department is actually available and only after a certain wait time (let's say the customer should wait for at least 5 minutes before this option can be offered).

This is how the process could look:

Overflow_if_agent_in_other_queue_is_enabled.png

Before getting started with this call flow, make sure you are familiar with Input Readers, local Automations and the different module types in general. This article is more advanced and won't explain everything step-by-step.

What you need in the babelforce manager app:

  • Audios
  • 2 Queues
  • 2 Triggers
  • 2 ACDs
  • 1 Input Reader
  • 1 Switch Node module
  • 2 Audio Player
  • 2 Local Automations

Step 1: Audio Prompts

Make sure you uploaded the prompts for your call flow. One prompt should offer the option to switch to the other queue, and you also need waiting music for when customers are in the queue. Alternatively to uploading prompts and use them in an Audio player you can also use a Text to Speech module which reads an individually defined text. Click here for more information on our Text to Speech module.

Step 2: Queues

Create two queues (Queue 1 = the first queue a caller reaches, Queue 2 = the overflow queue, for instance English Support) and add groups of agents that do not overlap too much (you need at least a few more agents in queue 2, otherwise there won't really be an overflow). 

Step 3: Application modules - 2 Audio Player, 1 Input Reader, 2 ACDs

Now, create the modules for the waiting music. Create 2 Audio Player and add the waiting music audio (the after-flow of these apps should be set to loop to themselves). You will need to go back to the Waiting Music module for Queue 1 later. Just to keep that in mind.

Create an Input Reader for the customer which offers the option to be forwarded to Queue 2. If you want, you can rename the variable (e.g. QueueForwardingOption). For more details on input readers, see this article.

Now, create 2 Automatic Call Distribution modules: the first links to Queue 1, the second to Queue 2. The first should link to Waiting Music module 1, the second to the Wait Music 2. The ACD linked to Queue 1 should have the Input Reader as after-flow.

We are not quite done with the modules, yet, however. Before we can proceed, we need two Triggers.

Step 4: Triggers

mceclip0.png

Trigger 1: In the example below, the customer has to wait for at least 5 minutes and an agent must be available in the queue that's called ENG Support queue (Queue 2 in the process map). Both of these conditions have to be satisfied before this Trigger will fire.

 

 

 

 

 

 

mceclip1.png

Trigger 2: The Input Reader you created above automatically stores a variable in the system (you can only create this Trigger if the Input Reader module already exists, see also this article). The example below selects the variable EnglishQueueOption. In this case, if the customer presses 1, the Trigger will fire.

 

 

 

Step 5: Complete Call flow with Application modules

Now create a Switch Node. This little module needs to evaluate the answer from your customer (1 would be a yes - "I want to be forwarded to the other queue"). This could look something like the screenshot below. You add a Trigger to a Routing Rule of a Switch Node. In this Rule, you use the Trigger you created above("forwarding wanted"). If the Trigger applies, the customer is forwarded to your 2nd queue (Automatic Call Distribution module 2). However, if the customer does not choose to be forwarded, the call goes to the After Flow which leads right back to your 1st queue (Automatic Call Distribution module 1).

mceclip2.png

Make sure that the Input Reader module's after-flow is linked to the Switch Node above! Otherwise, the customer's answer will get lost and the call ends.

Now you are almost finished! But one crucial part is missing: how does the call leave the first Automatic Call Distribution module and enter the Input Reader? Quite simple: you go back to the waiting music prompt player used in your first Automatic Call Distribution module for Queue 1. Go to he tab "Automations" and add a local Automation with the Trigger you created above.

What happens here? Every time the waiting audio finishes playing, this local Automation checks first whether the call waited in the queue for more than 300 seconds. Also, it checks whether an agent is available in Queue 2. If both of these questions can be answered with "Yes", the call will leave Queue 1 (your Action is "Leave queue") and go to the next module which is the Input Reader offering the option to switch to the other queue.

mceclip3.png

Finishing everything up

To round everything down, make sure that all modules are correctly conneced to each other. Automatic Call Distribution 1 (Queue 1/Wait Music 1) > After Flow: Input Reader > After Flow: Switch Node > After Flow: Automatic Call distribution 1.

Also make sure that the right waiting music Audio player and queues are assigned to the matching Automatic Call Distribution module.

The screenshot below summarizes the modules.

mceclip0.png

Test your flow with different scenarios (for instance: make no agent in first queue available but have one waiting in queue 2). All done! Happy testing.

 

Have more questions? Submit a request