The comma just inserts a pause before the next set of touch tones are sent, so the only rule of thumb is to use commas where you want this pause and use as many as you need, depending on how long it takes before the voice response systems starts expecting the new touch tones. The semicolon will wait until you double tap before sending the next set of touch tones, so this is good if you just don't know how long to wait before you need to respond with the new set of touch tones.
On 14/08/12 13:07, Tara Prakash wrote: > Hi Michelle. Sounds great. So, is there a rule of thumb about putting > commas? Is it fair to assume that everytime a response is expected from > the caller a comma should be inserted? > > > > ----- Original Message ----- From: "Michelle McQuigge" > <[email protected]> > To: <[email protected]> > Cc: <[email protected]> > Sent: Tuesday, August 14, 2012 11:05 AM > Subject: Re: iPhone and automated numeric response prompts > > > Tara, > The comma system would almost certainly work on an automated credit card > line, but I personally don't ever plan to use it for that purpose. If > anything should happen to my phone, I'd hate to think of such sensitive > information being readily available to whoever found it. If you don't > share those concerns, though, this will work for you no problem. > Best, > Michelle > > Sent from my iPhone > > On 2012-08-14, at 9:45 AM, "Tara Prakash" <[email protected]> wrote: > >> Have you tried the same to check your credit card bills? You dial the >> number and the automatic system tells you to enter your credit card >> number. Do you think the comma system can work with credit card >> inquiry number? >> >> ----- Original Message ----- From: "Michelle McQuigge" >> <[email protected]> >> To: <[email protected]> >> Sent: Friday, August 10, 2012 10:23 PM >> Subject: RE: iPhone and automated numeric response prompts >> >> >>> You have been well-informed about the comma, and I have recently >>> tested the >>> system on a teleconference line that demands a password, then a menu >>> option >>> to verify my choice. It worked flawlessly. You can hear the numbers >>> being >>> entered, and they sound very natural. No menu option was activated >>> until the >>> automated prompts had been allowed to run on for a second or two. In my >>> case, I had to call the number in question once or twice to figure out >>> precisely what menu options to pre-program. Here's what I did: >>> >>> 1. In my contact for the number in question, I entered the phone >>> number for >>> the teleconference line as usual. The numeric keypad used to enter phone >>> numbers features a shift key. Once I'd entered the phone number, I >>> double-tapped that shift key to pull up other options. >>> 2. Certain punctuation marks appeared in place of the numbers. I did not >>> enter a space, but simply entered comma immediately after the >>> teleconference >>> number. >>> 3. In my example, I followed this comma with the teleconference >>> password, >>> plus the pound symbol to expedite the menu. >>> 4. I then entered another comma, then the number 1 (which was the menu >>> choice to verify the password I had provided). >>> >>> It was that straight-forward. Please let me know if I misunderstood your >>> question, confused you even further or need to provide any >>> clarification. >>> >>> Best, >>> Michelle >>> >>> >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On >>> Behalf >>> Of Kramlinger, Keith G., M.D. >>> Sent: August 10, 2012 10:00 PM >>> To: [email protected] >>> Subject: iPhone and automated numeric response prompts >>> >>> Hi, >>> >>> With an iPhone, how does one go about entering numeric keypad >>> responses to >>> navigate within an automated system? >>> >>> I've heard one can use a comma after the phone number. The comma >>> introduces >>> a pause; several commas produce a longer pause. >>> >>> But not all automated systems are one layer deep, and some require a >>> fair >>> degree of interactivity within the system before one knows which is the >>> desired numeric response, or series of responses. >>> >>> Thanks in advance for any insight. >>> >>> Keith >>> >>> >>> -- >>> You received this message because you are subscribed to the "VIPhone" >>> Google >>> Group. >>> To search the VIPhone public archive, visit >>> http://www.mail-archive.com/[email protected]/. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/viphone?hl=en. >>> >>> -- >>> You received this message because you are subscribed to the "VIPhone" >>> Google Group. >>> To search the VIPhone public archive, visit >>> http://www.mail-archive.com/[email protected]/. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/viphone?hl=en. >> >> -- >> You received this message because you are subscribed to the "VIPhone" >> Google Group. >> To search the VIPhone public archive, visit >> http://www.mail-archive.com/[email protected]/. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/viphone?hl=en. > -- Christopher (CJ) chaltain at Gmail -- You received this message because you are subscribed to the "VIPhone" Google Group. To search the VIPhone public archive, visit http://www.mail-archive.com/[email protected]/. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/viphone?hl=en.
