<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://dashes.com/anil/1999/10/bitching-about.html" />
  <link rel="self" type="application/atom+xml" href="http://dashes.com/anil/atom.xml" />
  <id>tag:dashes.com,2009:/anil//1/tag:www.dashes.com,1999:/anil//1.80-</id>
  <updated></updated>
  <title>Comments for bitching about voice mail</title>
  <subtitle>A Blog About Making Culture</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.3-en</generator>
  <entry>
    <id>tag:www.dashes.com,1999:/anil//1.80</id>
    <link rel="alternate" type="text/html" href="http://dashes.com/anil/1999/10/bitching-about.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://dashes.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=80" title="bitching about voice mail" />
    <published>1999-10-24T16:00:01Z</published>
    <updated>2005-08-12T06:49:23Z</updated>
    <title>bitching about voice mail</title>
    <summary>So the updates to this page have been erratic due to all the extra effort I have to put in for my upcoming move... but,...</summary>
    <author>
      <name>Anil</name>
      <uri>http://anildash.com/</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://dashes.com/anil/">
      <![CDATA[<p>So the updates to this page have been erratic due to all the extra effort I have to put in for my upcoming move... but, having had the chance to spar with several voice mail/voice menu systems over the past few days has yielded some <strong>quick suggestions</strong>.</p>
<p>First, and most obvious, is that every menu (&quot;Push one for <em>x</em>, push two for <em>y</em>&quot;) should begin by revealing the <strong>number of choices on that menu</strong>. I know some systems do this already, but it's certainly very rare, and doesn't seem as if it would be very difficult to implement. How 'bout &quot;Please choose from the following four options.&quot;</p>
<p>Next, make the choices <strong>sequentially numbered</strong>. Don't give me 1, 2, 4, 6, and the pound sign. Number them one through five.</p>
<p>Make top-level menu choices <strong>based on the type of user</strong>. Just as links on a web page shouldn't be designed around the organization of the company, the main voice menu shouldn't be broken down according to divisions within the company. <strong>Bad:</strong> &quot;Press one for sales, two for technical support, or 9 to repeat this menu.&quot; <strong>Good:</strong> &quot;Press one if you want to find out more about our products before purchasing, press two if you already own one of our products and need help with it.&quot;</p>
<p>It's been mentioned a million times, but it bears repeating: Make <strong>An Actual Human</strong> one of the choices. I suggest standardizing on 0 reaching the operator, but I have the suspicion that the people who design these systems are already so user hostile that asking for anything like standards would be anathema to them.</p>
<p>This last idea I'm not sure how to implement, but let me try to explain. (Feel free to <a href="mailto:anil@dashes.com">offer suggestions</a>.) Have a &quot;soft selection&quot; option. Perhaps pushing pound and then the number of the menu option would indicate &quot;<em>Maybe</em> that's the one I want.&quot; Then, when the user reaches the end of the menu, the system would automatically repeat the menu, but only listing those options that had been soft-selected. Instead of the 9 top-level choices, the caller knows they either want 4 or 6, and those two menu descriptions are repeated to them.</p>
<p>Regardless, the sorry state of voice mail makes the web seem downright easy, and that's amazing if you consider that various forms of voice mail have been around for <strong>15 years</strong>.</p>]]>
      
    </content>
  </entry>

</feed>
