I think it's the implementation of systems and not being consistant with systems. I've called T-Mobile on several occasions and in the "log in process" when you call they ask you to enter your ten digit phone number. If you ask for certain information such as billing they will ask for the last four digits of your SSN. Then the frustrating thing sometimes happens when you speak to a rep. They don't have
*any* of the information that you have keyed in. It's not always this way but it is a lot of the time. I've asked reps why this is and they claim it's because those identifying fields are not filled in on their display. I'd say that this is a technical problem which could be fixed if there was a demand for it.I have seen really good IVR implementations such as what T-Mobile uses. With T-Mobile's IVR you are not limited to just the standard commands that the IVR expects you to give. It will do all sorts of normal variants e.g. saying representative, operator, or assistance will transfer you to a real person. Saying text message or saying SMS will give you your text message use. There are also "touch tone" shortcuts. If you want minute useage key 2. For billing key 1. For a representative key 0.
Then on the other hand extremely poor implementation of an IVR you can look at Fido (mobile provider in Canada.) It will only understands the exact words it wants to understand. Even on words that it's supposed to know such as "agent" you'll get fed back "I didn't get that" repeatedly. Also the Fido IVR absolutely does not permit any touch tone input for any menu items. If you do you get "that function is not supported." You can't even time out to get a real person!
Another problem with IVRs is if you're using it with a mobile handset any outside noise will confuse the IVR. Why mobile providers think it's a good thing to use IVRs with mobile services I have yet to understand.