cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
294
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: null on 05-03-2007 11:42:06 PM
Hi,

I'm using Menu option elements widely in my application and with no dynamic configuration. I've set the MAX-NOINPUT and MAX-NOMATCH to 3, assuming that caller gets a max tries of 3. In audio tab, I've Initial audio group, noinput1, nomatch1, noinput2, nomatch2.

But after the second noinput prompt, the app waits for the caller's input, but caller didn't enter. The application should supposed to take the max_noinput exitstate, but instead it played the noinput prompt one more time and immediately proceeds to the corresponding exitstate(ie, call transfer) without waiting for the caller's input.

I tried changing the settings with MAX-NOINPUT & MAX-NOMATCH to 2, so intial_audiogroup is played, caller doesn't enter any input, noinput1 prompt is played, caller doesn't enter any input, noinput2 prompt is played and without waiting for caller's input immediately proceeds to the corresponding exitstate(ie call transfer).

Analyzing the generated VXML, for MAX-NOINPUT set to 3, the catch block for count 3 should have only the submit tag with no prompts in it. And if you suggests me to set the MAX-NOINPUT to 2 to realise that the caller be given 3 tries, I did try that too, in which case the generated vxml has for the catch block for count 2 having the noinput2 promtps followed by the submit tag, thereby the timeout of 5secs for the second noinput prompt is missing. Attaching the generated vxml herewith.

I'm not sure if this is a known Audium platform issue. Pls clarify and suggest a solution.

I would really appreciate for any quicker response.

Thanks,
Vijay

Subject: RE: maxnoinput and maxnomatch settings
Replied by: null on 07-03-2007 10:34:05 PM
Hi Vijay,

For support requests which require timely answers please refer to Cisco TAC.

Regards,
Roberto

Subject: RE: maxnoinput and maxnomatch settings
Replied by: Janine Graves on 08-03-2007 01:32:26 PM
My experience with setting MaxNoinput = 3, is that the NoInput3 prompt will play when that third NoInput event occurs and then the systen exits immediately down the MaxNoinput exit state. Which agrees with what you are seeing.

This seems to be the 'behavior' - so the NoInput3 prompt should either be omitted, or should be some sort of apology before giving up on that collection step ('Im sorry, we just can't hear you')

Janine Graves
[email protected]

Subject: RE: maxnoinput and maxnomatch settings
Replied by: Michael Bochynski on 08-03-2007 02:01:51 PM
Vijay,

Janine is correct, the last NoMatch/NoInput prompt is designed to play back a message only. It is an intended behavior to gracefully play back a prompt to a caller instead of exiting the dialog without any warning. In the default settings, the third prompt is the last one.

Imagine the following scenario:
[code:1:cc1e3ee85e]
System: Please tell me your account number
User : [NoInput 1]
S: I didn't hear you. Please tell me your account number
U: [NoInput 2]
S: I still did not hear you. You can enter the account number by saying it digit-by-digit or entering it via your keypad
U: [NoInput 3]
S: I am sorry, I couldn't get your input. I will transfer you to an operator.
[caller is transferred to an agent]
[/code:1:cc1e3ee85e]
The above dialog can be done in one element only, where your third prompt will explain to the caller that he is transferred to an agent due to reaching MaxNoInput.

Hope it explains everything,
Michael

Subject: RE: maxnoinput and maxnomatch settings
Replied by: null on 08-03-2007 04:14:46 PM
Michael,

Pls correct me if I'm wrong, although initially I've set the max_noinput count to 3, the audio tab has initial, noinput1 and noinput2 audiogroups and I didn't create noinput3 audio group. So after noinput2 prompt played, and caller still doesn't enter anything, since the max_noinput count was set to 3, the noinput2 audiogroup is played again and immediately transferred.

The solution you suggest is, create noinput3 audiogroup and have the audioitem jus playing "I am sorry, I couldn't get your input. I will transfer you to an operator" followed by call transfer.

But this will have a major design change, as the noinput3 prompt is played before the actual Transfer element in a different page as we thought its easier to have it in one place rather than have this audio item played as noinput3 for all the Menu elements present in the application.

your comments pls,

Thanks,
Vijay

Subject: RE: maxnoinput and maxnomatch settings
Replied by: Michael Bochynski on 08-03-2007 04:44:42 PM
Vijay,

The default behavior is to reprompt the last prompt, if nothing has been specified. Hence, if you define an audio group for 2nd NoInput, the same message will be played back for the 3rd NoInput.

Remember that Studio is a tool allowing easy voice application creation. The actual design details are up to designers, including prompt management.

Typically you would play a different message when MaxNoInput or MaxNomatch are reached in order to explain next steps to the caller. You can split the last message and in your element have a prompt saying "I didn't hear you" for NoInput and "It's not a valid input" for NoMatch and then in the Transfer element "I will transfer you to an operator". You can also define an empty prompt for the last audio groups in each category. For some browser, putting a dot (".") works fine, however please refer to your voice browser's documentation for details.

The above scenarios are only two sample approaches to this issue, and it is really up to the VUI developers to choose the approach suitable in their particular application. We cannot suggest the "correct" approach, since it is specific to the scenario designers and developers chose for their application.

Hope it helps,
Michael
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links