I like to think of “templates” when I see how I can extend a business process using voice. It helps me think faster. Voice templates are examples of voice based solutions and remind me when I can use voice to solve a particular problem. For instance, if you are faced with the problem of communicating information to the general public, voice is a great way to accomplish that task. Another example would be to use voice to carry data outside the firewall to support remote workers. My latest one? Decision support systems.
Decision support systems deliver context sensitive data to a decision maker in real time. Here’s an example: you are a manager of a technical support team, and a new trouble ticket comes in. The trouble ticket is escalated to a second level support, and you’ve got to figure out which of your support team has to handle the issue. You can use voice to reduce the human latency in the process by calling all of the available support managers. When one picks up, the call would announce that a new second level ticket was just entered, and the subject was “user interface crashes on install”. As a manager, you could then decide that Vitaly is your best engineer for that, assign the task to him, then hang the phone up. Or, you might know that Vitaly is on vacation, or swamped, and assign it to Bill. By presenting data along with an opportunity to decide on the path, the process minimizes human latency.
This scales and manages well too:
- By fanning the call to multiple managers, you manage individual schedules among your management team.
- If no one answers, you can call later on in the day. Multiple tickets could be presented sequentially in the same phone call.
- The solution doesn’t care where the manager is: she is freed from her desktop.
- The solution plays nicely with existing infrastructure.
When viewed in the context of other great voice attributes, decision support is an excellent feature that voice can carry.

