Today’s consumers are extremely demanding and nowhere is their patience shorter than when dealing with your call center. If you leave callers on hold, your agents will hear the complaints (which extends handle times) and your social media timeline will show angry tweets. (Have you looked up your company on OnHoldWith.com? You might be in for an unpleasant surprise.) So having hold times of more than a few minutes is just asking for trouble.
What can a call center manager do? Sure, more agents will reduce wait time, but agents are expensive! Luckily, in this case, there is another answer: Replace hold time with a call-back. If you’re considering a call-back solution for your call center, here are some things you should check off your list before proceeding.
Reviewing the Reasons:
First, a quick refresher on why call-backs will improve your call center:
1) Improving Customer Satisfaction
Surveys regarding customer service complaints consistently show that “waiting on hold” is at the top of the list. Obviously, eliminating something the causes dissatisfaction, will lead to increased satisfaction. However you measure client happiness – NPS, repeat visits, repeat purchases – you are certain to see improvement.
2) Reducing Abandon Rates
When hold times are long, many callers will simply abandon, i.e. hang-up. Abandonment leads to higher repeat calling (which can strain the call center system) and, of course, dissatisfied customers. Offering a call-back reduces abandonment because, even if the total wait time is the same, a customer who has opted for a call-back is very unlikely to abandon. (Our own numbers show a 98% reconnection rate.)
3) Lower Cost
A less obvious advantage of call-backs is the ability to lower contact center costs. When a caller is waiting on hold, there is a phone line being kept open, with per-minute telco costs accumulating. If that call is turned into a call-back, the line doesn’t have to be active until the agent is available.
4) Smoothing Out Spikes
If your call center has “spikey” call volume, you’re faced with an extra challenge: If you staff to the peak volume, you will have excess agent capacity at other times. Call-backs also help “smooth-out” spikes in call volume by deferring calls (in a customer-friendly manner) till a time when there is excess agent capacity.
For more details on these reasons see:
- 3 Secrets to Successful Call-Backs
- The Do’s and Don’ts for Implementing Call-Backs in the Contact Center
- 7 Signs Your Call Center Needs a Call-Back Solution
Things I Wish I Knew Before Adding Call-Backs
1) Spend Effort Getting the Timing Right
Part of any call-back system is playing the offer message. This is usually something like, “Instead of waiting on hold, you can get a call-back from the next available agent by pressing 1 now.” The “Time-Till-Offer” or “TTO” is the amount of time a caller spends in virtual queue before hearing a call-back offer. Many companies don’t realize how critical the timing of this message is.
Although this sounds complicated, it’s actually good news. Changing TTO is an easy “lever” to adjust and has a big impact on the performance of your call-back deployment. I definitely advise you to put effort into getting this timing right!
For more on this topic download our eBook, “The ROI of Call-Backs for Your Call Center”.
2) Don’t Make Callers Wait Twice
After the queuing is complete, a call-back system has to somehow connect an agent with a caller. Familiarize yourself with the two main ways of doing this: “agent-wait” or “customer-wait”.
In the customer-wait scenario, the call-back system tries to estimate when the next agent is going to be ready, and calls the customer a few minutes ahead of that time. This maximizes agent efficiency, but it results in a negative experience for the customer. From their perspective, they requested a call-back only to be placed on hold again. If the system incorrectly determines agent availability, then hold time can be long, negating the advantage of having call-backs in the first place!
The alternative is the agent-wait scenario. Here, the agent is already on the line when the customer answers the call. This is a better experience for the customer, but the agent has to wait while the customer’s phone rings. Luckily, the idle time is typically 10 seconds or less.
Sometimes “agent-wait” and “customer-wait” are called “agent-first” and “customer-first”. To avoid confusion just ask your call-back vendor to walk you through the timeline, so that this isn’t one of those things “you wish you knew”!
3) Provide Callers with an Escalation Path to Voice
The vast majority of contact centers are using multiple channels to interact with their customers. Each channel has its strengths, but the voice channel really stands apart. That’s because, when you have a tough issue to discuss, when there is an urgent matter, or when the other options have left you frustrated, there’s an instinctive desire to talk to another human.
This isn’t a criticism of self-service channels, since they are cost-effective and most customers prefer them now anyway. But, remember that even the best self-service systems can’t cover every possible path. There will be dead-end moments, where the customer needs to talk to an agent. This is one reason call-backs are so important: they allow your callers to escalate smoothly to a voice conversation from any other channel.
So make sure your call-back solution has strong multi-channel capabilities, like pre-built components that can be added quickly to your web page or mobile app. And make sure that all the relevant teams in customer service are aware of your new call-back functionality.
Until recently, adding call-backs to your call center required installing hardware or software offered by the vendor of the call-center system. For example, Avaya sells CallBack Assist for its platform and Cisco sells Courtesy Callback for its platform.
Fonolo changed all this by introducing a new way to add functionality to an existing call center: A cloud-based platform-agnostic approach that is easy to deploy on any call-center.
The secret to being platform-agnostic is that the interaction between the call-back solution and the call-center is accomplished purely with phone calls. Because all centers can accept phone calls (by definition!) this makes the Fonolo solution universally compatible. We make it simple to use, but a lot of work “under the hood” is required to make that possible. Some of that work is spelled out in our many patents on the topic.
For more details on picking a solution, see “Make Callbacks a Priority”. That post includes 6 key questions that you should ask your vendor before deciding.
What if Your Platform has a Call-Back Option?
Many platforms, both on-premise and cloud-based, have at least some form of call-back functionality. Even in these cases, the Fonolo approach has advantages. It’s tempting to just go with the built-in back feature, but there are several potential downsides to consider:
- If you change platforms in the future, you will have to start over. (As a bonus: having call-backs in place from a 3rd party during a platform transition is great way to mitigate any hiccups that might occur.)
- If you have a multi-site or multi-platform scenario, you will need to configure each call-back solution separately.
- If you send some of your calls to a BPO/outsourced call center, the call-back strategy won’t extend to those calls.
- If you’re looking for a feature rich product with intelligent reporting features, turning on a module in your current platform likely won’t provide that
Call-backs are one of those rare win-win situations in the call center world: Callers have a more pleasant experience and the call center gets a more efficient operation. If you’re exploring this option today, we are happy to help any time. Sign up for a live demonstration to learn more about how call-backs work.