I'm curious to hear from administrators who have experience setting up automated phone trees. What are some of the unusual or challenging requirements you've had to deal with during the process? I used to work in phone support and found that navigating these systems can be incredibly frustrating. Let's share our experiences!
2 Answers
One key challenge I've faced is explaining to clients that their budget-friendly hosted solutions can't match the advanced call routing functions of their expensive old systems. Even when they want features similar to what they had before, they often resist opting for higher-end options that really would give them what they need. It's a tough conversation!
We transitioned to a Teams VOIP system recently, and I had to replicate our old phone system's setup, which included recording audio prompts in both English and Spanish. Over the past year, I've completely redesigned it three times because people kept asking for changes, assuming it wasn't efficient. Since our company has merged with others, we now have to create variations for each entity, plus maintain separate English and Spanish options. In total, I've set up 125 automated attendants! It took nearly 20 hours to generate the audio and connect everything, especially since they didn't want my voice in the recordings anymore. Now, if there's a script update, I need to change it across many attendants, which can feel endless!
Questioning the logic behind these systems makes me wonder if companies make them complicated on purpose just to keep you from reaching a real person faster.
I totally get that! It's frustrating when a simple change turns into a massive project. Have you thought about mapping out the responses to avoid confusion? That might help streamline things.