Common Call Flow Errors!
One of the most common errors in call center call flow planning is allowing a customer caller to queue for an Agent when no agents are logged in! The second biggest error, is leaving folks in the call back queue, at 5PM when all the agents log out and go home! So how do you do make sure this situation does not happen?
As it relates to the first issue, we always check to make sure that Agents are logged in BEFORE we queue a caller! This is a very simple step to do and it saves a lot of aggravation for callers who will never forget how long you left them rotting away in an empty queue!
Now as it relates to ‘call back’ without losing your place in queue, we have the same issue. Let’s assume that you offer callers this option. It is now 15 minutes before closing, what happens if all the agents log out before the call back is next in queue?
Call Back without losing your place?
In AWS Connect, Call Backs will follow the On-hours schedule. So if someone left a request for call back at closing time, that option will not trigger until the next day when the queue is open per On-hours. Lets see if we can improve this, but NOT offering that option late in the day!
We can setup a new schedule that only offers the call back between certain hours, so that if it is near closing, we do not offer the caller this option. This can be easily scripted in AWS Connect Contact Flows by adding a “check on-hours” step that eliminates this option when callers enter the queue and hour before closing time. This assures that Agents can log out at the appointed time and not leave anybody in queue!
AWS Connect is written around “contact flows” of different types. A “contact flow” handles inbound calls and routes them to Agents in queue. A “customer queue” contact flow deals with how to treat a caller while they are awaiting for the “next available representative”. You will learn this the hard way the first time you try to add a block to a contact flow and find that, though the block was there earlier, it is not there now! Why, the contact flow you are working on, does not support this type of block.
Free Call Back Script just for Asking
In this example we use a “Main Greeting” that is triggered by a call to the DNIS number associated with this path. We start the contact flow off by setting up all the variables like what voice to use, are we logging, what queue hold to use, which queue we are using etc. The flow goes on to check operating hours – routing ON- hours to the Queue and Off-hours to the Voice Message center.
If it is “On-hours” we send the call to the Queue flow. If an Agent is available, we connect them to the caller. If all agents are engaged with other callers, we queue the call. We play our “poor mans” Estimated wait time and then queue them with a “care message” followed by Music. 60 seconds later, we offer the option to continue to hold for an agent, or press 1 to receive a call back without losing your place in queue’.
Before we offer this option, we check another schedule that determines if we should offer the call back option. If the caller hits the center during the call back hours, the call proceeds as described above. If it is an hour before closing time, we do not offer the option.
So hit us up with a request and we will send you three “Quick Start” scripts that enable you to get this working as quickly as you can import the scripts into your AWS Connect call center instance.
Better yet – Give us a call and we will set this up for you!
