Great point about automated systems. Now I'm imagining a future where there's better telecom integration so that the phone tree options are integrated into the caller's UI.
For example, speaking to your cell phone company, you could see:
1 [Billing] 2 [Account] 3 [Add a line]
4 [Problem] 5 [Option5] 6 [Option6]
7 [Option7] 8 [Option8] 9 [Option9]
0 [Operator]
This would be customized to whatever phone tree you're interfacing with.That sounds like it'd require a huge overhaul to the phone system. At which point... why do the telcos even need to be involved here? VoIP is common enough now that you could just have a menu system before the call and trigger a VoIP call to the right department automatically.
And heck, let's get rid of phone queues while we're at it - just have the agent trigger a callback rather than making them listen to an awful hold music loop for potentially upwards of 15 minutes.
maybe the phone tree options could be described using some sort of markup language.
That's a clever idea, but I can so easily imagine a world in which a company's malformed markup causes a buffer overrun in my phone.
Do you use a browser on your phone?
Re:Redesigning the smartphone dial pad
by kalleboo on Saturday October 07, 2017 @04:27AM
(#15422902)
Or they could just list direct numbers to each division on the company's website...
Re:Redesigning the smartphone dial pad
by mmphosis on Saturday October 07, 2017 @04:09AM
(#15422859)
and make it tuRing complete
Automatic speech recognition that would spell out the menu item next to the corresponding digit would be sweet.
I'd take a couple of thoughts.
Most of my dailing is done via voice, phone URL or stored contact.
Most of my time in dialpad is spent entering digits for automated systems (e.g. "press 1 to join meeting" or "dial meeting code then #" or "press 0 to talk to a receptionist").
What dedicated call vs. hangup buttons?