CallCentreVoice Topic IVR - What do YOUR customers really think?

Created by:
Statistics:
Forum:
Quick links:

David Newton-Dines on 6/6/2001 15:27:37.
Topic has 32 posts; viewed 19293 times.
Technology   [This topic is read only]
Forum List | Unified View | Latest Posts
Popular Topics | Editor's Choice | Voices WebLog

Author

Comments

David Newton-Dines
MD
DND Services

145 posts
0 friends welcomed

IVR - What do YOUR customers really think?  [6/6/2001 15:27:37]

The company I'm working with currently is thinking about installing an IVR...

What I'd apppreciate is real life evidence - one way or the other, positive or negative - as to its impact on your customers' experiences.

Many thanks for your assistance everyone.

David

Gold Level MemberYou don't have the priviledges to view this user's post history

 

Vedula Srinivas
NA
NA

121 posts
0 friends welcomed

IVR the inhuman face of CRM  [7/6/2001 17:36:22]

Dear David,

I think you took a weekend off as I did not see many posts from you for a couple of days.

Regarding my experience with IVR which we installed in our office we faced the following problem. We have 5 lines in our office and wehave a 60 seconds voice recording which greets the caller and later transfers the call as per the options.

I noticed that when IVR is active for one call, the other calls received had no answer and the phones kept on ringing on other lines and our PBX did not respond to the other line. This resulted in annoyed cutomers who thought that the company did not have an operator and many important issues could not be informed in time.This is the problem with call centres also...

My experience has shown that most of the times when the IVR is activated many PBXs do not have intelligent way of understanding the need to give ans tone and play another IVR message as one in progress....

I can not understand why though technology is available, the hardware manufacturerers fail to recognize the importance of responsiveness.A true paradox it is...

Vedula

Gold Level MemberYou don't have the priviledges to view this user's post history

 

Jeannie Turicik
National Account Manager
iBasis

9 posts
0 friends welcomed

Support Facts for IVR's  [7/6/2001 20:17:18]

iBasis is an IVR ASP--in those cases where customers switched from an existing IVR using touch tone to an IVR using speech -- IVR selection for service rose dramatically and "zero outs" decreased. People have become used to IVR's and will use them, but find it much more customer friendly to self serve in a speech enviroment. For very simple applications where the customer does not have to make a great amount of choices, or simply answers "yes" or "no", touchtone does the job fine.

You don't have the priviledges to view this user's post history

 

Vedula Srinivas
NA
NA

121 posts
0 friends welcomed

IVR the inhuman face of CRM  [8/6/2001 00:59:00]

Dear David,

I think you took a weekend off as I did not see many posts from you for a couple of days.

Regarding my experience with IVR which we installed in our office we faced the following problem. We have 5 lines in our office and wehave a 60 seconds voice recording which greets the caller and later transfers the call as per the options.

I noticed that when IVR is active for one call, the other calls received had no answer and the phones kept on ringing on other lines and our PBX did not respond to the other line. This resulted in annoyed cutomers who thought that the company did not have an operator and many important issues could not be informed in time.This is the problem with call centres also...

My experience has shown that most of the times when the IVR is activated many PBXs do not have intelligent way of understanding the need to give ans tone and play another IVR message as one in progress....

I can not understand why though technology is available, the hardware manufacturerers fail to recognize the importance of responsiveness.A true paradox it is...

Vedula

Gold Level MemberYou don't have the priviledges to view this user's post history

 

John Clark
Director
Reynard Thomson Ltd.

1384 posts
0 friends welcomed

"touchtone does the job fine"...  [8/6/2001 12:22:28]

Jeannie, interesting points about IVR versus touchtone.

A few questions for you:

Do you see IVR as a replacement for, or an addition to, existing installations?
What about cases where caller answers are less well defined, e.g. open-ended systems ("which film would you like to book?" as opposed to "would you like to book tickets for FilmName? (answer Yes or No)"), i.e. free format interaction?

Interested to hear how iBasis' approach such things...

John

Community BenefactorGold Level MemberYou don't have the priviledges to view this user's post history

 

David Newton-Dines
MD
DND Services

145 posts
0 friends welcomed

Responses  [8/6/2001 13:51:33]

Does the lack of responses here on the specific question mean that you really don't know what your customers think about your systems?

David

Gold Level MemberYou don't have the priviledges to view this user's post history

 

Antonio da Costa
Sales Engineer
Macomber Computer & Communicatio

20 posts
0 friends welcomed

IVR - What do YOUR customers really think?  [31/7/2001 17:55:17]

My suggestion is that you compile stats from diverse call centres using as benchmark their averaged hold times, calls dropped, calling times. Take those and make sure you have info on equipment utilized, number of agents, whether it's inbound or outbound, the nature of calls performed.

Experiences vary.

You don't have the priviledges to view this user's post history

 

James Dawkins
Telecoms and Network Consultant
iCore Ltd

14 posts
0 friends welcomed

IVR Experiences  [2/8/2001 13:40:14]

As mentioned by others here there is no hard and fast rule for IVR's however some of the guidleines I have previously implememted as follows:

Don't use an IVR unless there is a clear business requirement, here (UK) they are still not particularly liked by most people.
If you do use one try and make menu choices as succint as possible
Never have more than 5 menu choices
Never cascade menus more than once
Try an use IVR's hand in hand with skills based routing.

Hope that helps you

You don't have the priviledges to view this user's post history

 

John Clark
Director
Reynard Thomson Ltd.

1384 posts
0 friends welcomed

Menu design  [2/8/2001 13:58:41]

James wrote:

"If you do use one try and make menu choices as succint as possible. Never have more than 5 menu choices.
Never cascade menus more than once.
"


First of all, welcome to 'Voice - always nice to see new faces!

Your comments ring true; we've actually had a few discussions on effective menu design in the call centre 'interface' - you might like to check out this thread for more on menu design. Feel free to add your ideas, though; I especially agree about the 'cascade' comment - it can be a problem navigating when you have to 'back-up' the chain of interaction.

John

Community BenefactorGold Level MemberYou don't have the priviledges to view this user's post history

 

William Winslow
Partner
Winslow, Rahman & Forde

14 posts
0 friends welcomed

Menu design  [3/8/2001 10:49:32]

Does anyone have a link to a website with advice on how to approach breaking down the problem of menu design ? I have some questions :

Is there a metric or standard for menu design ?
How do we position choices in a menu for optimum usability ?
What to do if we can't avoid a multi level menu ( is this ever the case ) ?

WW

You don't have the priviledges to view this user's post history

 

Antonio da Costa
Sales Engineer
Macomber Computer & Communicatio

20 posts
0 friends welcomed

Support Facts for IVR's [  [28/8/2001 22:13:14]

I see future for the IVR, and off course my opinion is biased.
But improvements are needed.
Baselining on remarks for many posters, I would say that having an organized way to find things is a necessity, so the existence of IVRs.
Yet the perception of lack of human touch always precedes. And for a good reason, because of what they tipically find at the other side of the IVR: Lack of qualified personel, hours on hold, etc.
Voice or DTMF intefaces is mostly a vendor issue. Different speech patterns need to be supported and back end databases need to provide some sort of fuzzy search capabilities. Or a nice enhancement such as voice processed search might as well just add to the frustration of the caller.
The best of the technology,in my opinion, is one that blends the queueing capabilities of ACD with IVR and through different types of media that customer come to accept and use ( chat, voice, fax, web, e-mail, SMS ).
The problem of using these technologies all combined is that putting together different technologies not always present with the best results, since most vendors don't share much other than common CTI standards.
Best case solution: Improve internal processes on problem solving skill sets and hire a vendor orintegrator, who is accountable for the entire contact center technology set.

You don't have the priviledges to view this user's post history

 

Marianne Marrou
Telecom/Reporting Analyst
Outsource callcenter

339 posts
0 friends welcomed

Customer opinions  [6/9/2001 15:59:04]

Unless you do a customer satisfaction survey, you can not know if your customers like the IVR. You will most likely only hear the BAD feedback.

At my last company, when we went from live operator answered calls, to IVR fronted calls, we sent out a customer satisfaction survey. This survey invited people to call in and try the IVR, and evaluate it. We also used that survey to check on the customer service agents, and overall customer satisfaction.

This was about 5 years ago now, so IVRs were still not widely accepted.

The results we received were mixed. Some people wrote flat out 'When I call in I want to talk to a person, not have to press buttons' and 'I hate those computer operators!' There are just some people that willnever like an IVR, no matter how well designed.

We did receive some useful feedback from these surveys. Some customers said, 'I had trouble finding the ....' Or 'It didn't give me enough time to enter my account number.' We made adjustments tothe IVR based on this feedback.

Other customers were very happy that they were able to resolve their problems quickly without having to wait for a representative. In our case, we allowed the customer to make payment arrangements via the IVR, which they liked since they apparently felt embarassed talking to a rep.

Hope this helps.

Gold Level MemberYou don't have the priviledges to view this user's post history

 

John Clark
Director
Reynard Thomson Ltd.

1384 posts
0 friends welcomed

Some people...  [7/9/2001 13:34:25]

Marianne, you said:

"There are just some people that willnever like an IVR, no matter how well designed"


How true that is - as with any technology, there are some people who won't learn because they don't feel that they can and there are those that won't because they have always done things another way. C'est la vie!

John

Community BenefactorGold Level MemberYou don't have the priviledges to view this user's post history

 

Robert Tuck
Planning & Performance Manager
Thames Water

48 posts
0 friends welcomed

Circumstances  [7/9/2001 15:08:53]

I think it all depends on the way the IVR is used by the business. There are certain companies I need to call and I know exactly which department/subsidary and I know will need to speak to a human, to then spend 5 minutes routing myself through the IVR menu's is frustrating and serves no useful purpose for me as a customer. What I need in this instance is a direct number to my end result.

On the other hand I am far more prepared to go through an IVR when I have no idea who it is I need to speak to. Especially if the IVR is used in such a way to make sure I get to the agent who can answer my query. Basically I want a number that I can dial a dept directly with and the IVR to be used for my general queries.

The use of an IVR is poor when it only serves to make my task more complicated or can only complete art of my query. We use the IVR quite heavily and as a mobile phone service provider we offer an automated international bar removal service. It works well but many customers call back and speak to an agent to make sure it happened or ask further queries relating to using the phone abroad. Te end result is it took the customer longer on the phone and we had to deal with the call anyway!

You don't have the priviledges to view this user's post history

 

Vedula Srinivas
NA
NA

121 posts
0 friends welcomed

Complaint logging using IVR  [14/10/2001 11:18:45]

Hi,

I was recntly conducting a training session to a piped gas supplier executives in Mumbai, India. The feedback I received on their IVR ( automated system) is that 80% of the complaints recorded by IVR under various complaint categories was all wrong. To add to complexity, the customer care department has to reclassify the complaints all over again. The voice recording system most of the time had only "hello can u hear me" messages thus defeating the very purpose of IVR solution.

Vedula

Gold Level MemberYou don't have the priviledges to view this user's post history

 

Gerry Miller
Manager CC Support & Development
New York State , OGS

2 posts
0 friends welcomed

IVR  [2/1/2002 19:02:46]

This is one of my major pet peeves. IVR is a great technology that is used so poorly that people have grown to hate it. This is not because of the technology but because of poor implementation. If you pay proper attention to Human Factors concerns from the start you will be able to design and put in production an IVR that people actually like using!! Try the following for starters : Australian/New Zeland IVR design standard ( AS/NZS 4263:1997) available at standards.com.au the only offical standard out there(though the ISO is working on one with HFES to expand ISO 9241 to include voice response), eiginc.com ( great company specializing in teaching people how to design useable applications : I have no finanical relationship with them), HFES.org( Human Factors and Ergonomic Society) Hope this helps.

You don't have the priviledges to view this user's post history

 

Andy Cowhig
Senior Sales Engineer
"Between Jobs" since 31/1/02

1 posts
0 friends welcomed

Measuring the customer's view of IVR  [22/2/2002 10:06:12]

I am new to this forum, so Hi to all!

NB All my comments below refer to true IVR - the ability to provide a complete self-service transaction, rather than merely a call routing device.

David's original question is a challenge to answer,due to the fact that there so few quantifiable results published on the success rates of IVR.

This is ironic, as the two main selling points of IVR are that it reduces the cost of a transaction and that it improves customer service - both clearly measurable!

There are of course various statistics provided by the Henley Centre, which reports that 60 per cent of customers believe auto-access (IVR) systems improve service, but these are often generic examples.

The important point is "what do MY customers think of the service that I am providing on MY IVR".

There are ways of assessing the IVR success rate, but they also need to be considered within the bigger picture.

For example, if should be expected that the percentage of calls transferred to an agent (where the facility exists) should be roughly 15%, a significantly higher proportion of transfers may suggest that the callers are not satisfied with the automated service.

However, this judgement cannot be made unless the reason for these transfers is logged. I know of very few call centres that provide their agents with a mechanism for logging a comment or complaint regarding the IVR. As we are told so often, only 1 in 10 customers who have reason tocomplain actually do, so ignoring the complaints is hiding a bigger problem than stats may suggest!

A simple tick box on the customer record could register the fact that the customer made comments re the IVR, which could be followed up by someone with a vested interest in the performance of the IVR - clearly not the agent. I know how impressed I would be if I received a call from a company who I perceived were genuinely interested in my comments.

It may be that the IVR provides 3 services and for each customer calling for one service, it satisfies the need perfectly. But what if customers want to perform two different services? This sounds obvious but I have encountered systems that require the customer to call back if more than one transaction is required! - or more typically, require the caller to identify themselves again even on the same IVR transaction!

It may be that callers typically do require more than one service and the second service is not addressed by the IVR. For example, a mail order company may provide an automated service that allows their field agents to know how much commission they have made from sales, who will then want to speak to an agent to buy products based on that commission. In this example, the IVR is performing its role, in that the call centre agent is engaged purely in revenue generation activity, rather than being the interface between the back-end data and the customer, which is, of course, the Ivy's job.

Another method would be to track those account numbers who use the IVR and therefore work out who doesn't, for follow up later. This would be very simple to achieve through the IVR and would be an invaluable aid to improvement.

The most effective method, however, is to usethe IVR to assess itself - by asking a question or two at the end of the IVR transaction. This is important for two reasons; The feedback is at the point of the transaction and it is collected by an impersonal device - the IVR. Research out of Stanford University on human behaviour has concluded that if you want true feedback on your company's services, don't get a human to do it, as unless we are truly furious and willing to let go with both barrels, we will tend to play down issues we have experienced.Far better to get an automated system to be the channel for feedback due to its impersonal nature.

I think it is common for us "call centre types" to forget that we are customers of organisations too, which is why I always try to consider my ownreactions to automated IVR services when designing a system or reviewing an existing setup, which is probably the best advice I can give anyone.

My own bank is a good example. I prefer to use the IVR to retrieve my account balance and to pay bills, however I will use the web service to review standing orders and go through my statement. I will only call the call centre when I have a complex query where the agent can actually add value.

I would be keen to hear others' views on this.

Regards

Andy Cowhig (andy.cowhig@ntlworld.com)

You don't have the priviledges to view this user's post history

 

Alex Clay
Telecoms Analyst
Financial Services

57 posts
0 friends welcomed

Are customers Odd?  [25/2/2002 13:13:15]

Andy's post made me think about somehing thats been churning through my mind for some time.

The general track of the though is how often do you actually need to calls your bank etc! Now this may just be me who is odd but I have all house and carbills on DD. I get my CC statements through the post. Now I can't actually think of why I need to call my bank for anything other than a problem or maybe a complex issue issue that would be hard to program into an IVR system.

But from experience(my company is a Credit Card issuer) lots of customers call on a regular basis. Manygo for account balance type info (good for the VRU) but lots have4 repeat queries that I would thinl you only need to tell people once!

So my question would be why do you call your bank etc, and how often? What do you think of the service you recieve?

You don't have the priviledges to view this user's post history

 

David Newton-Dines
MD
DND Services

145 posts
0 friends welcomed

Good root cause analysis negates the need to call at all  [26/2/2002 15:50:33]

Great post Alex…

IMHO all too often business simply reacts to the need to answer calls rather than try and understand just WHY they happen in the first place. In other words they fail to do a root cause analysis.

Many years ago I was asked to take over a world wide product support team. After a few weeks I went to the MD and told him I wanted to see our average call times INCREASE. You can guess his response! When he’d calmed down I explained that what I wanted to do was produce a mechanism whereby we provided our route to market with all the tools they needed to do their job. That meant ‘local’ access to every problem we’d ever tackled. By providing the engineers with CD ROMs with all our tech data they looked there first instead of calling us. This meant that calls that came to us increasingly were stuff we had never seen previously and so were ‘harder’ to solve which meant taking longer…

There is yet another side to this story. All too often people who run support centres want them to grow. This is fundamentally wrong. For a person to be forced to call a support centre means that the company has failed. Either the documentation, explanation or functionality of the product is not as easy to understand as customers need. Work should therefore be done to improve it rather that put more people in place to answer questions about its failings. Any support CC manager worth his/her salt should be looking to make that department redundant by helping to improve products so that they are easier to install and use thereby doing away with the need to call at all.

Comments anyone?

David

Gold Level MemberYou don't have the priviledges to view this user's post history

 

Brent Preece
Vice President
Destination Excellence, Inc.

123 posts
0 friends welcomed

Shrinkage is good!  [26/2/2002 18:40:42]

David, I agree entirely. Tech support, customer care calls that grow ahead of subscriber growth, and the like should be shrunk - else the call center is probably not doing anything more than 'throwing warm bodies at the issue'.

A client of oursrecently worked thru this same thing, albeit out of necessity. Layoffs forced this group to cut their tech support staff by half, when their service levels at full staff were poor to begin with. The ingenious director of the center decided to determineWHY people were calling (a technology that was already inherent in their ticket tracking system) and begin initiatives to work the volumes down by
a)providing some automated fixes to common issues (password changes, etc),
b)providing web-based FAQ that would shift volumes away from the center, directed by their IVR and
c)having his staff focus on fully comprehending and solving the caller issue, leading to diminished repeat calls. Within a few months, these efforts have cut volumes by two-thirds, and service levels are excellent.

No new technology was used and no staffing up was required. Just approaching the issue from a 'customer-centric' point of view did the trick.

Silver Level MemberYou don't have the priviledges to view this user's post history

 
 

Page 1 of 2 - jump to page: 2 

In Read Only View, you cannot reply to any topic