cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2746
Views
10
Helpful
8
Replies

Form Element Clarifications

Roys1994
Level 1
Level 1

Hello Guys,

 

Just need quick information , I am using the form element for 6 options menus , here i need defined the DTMF digit ,

the requirement is we need to defined the DTMF key value 1 - 6.  if callers press 7 , 8 or  like something different number , IVR should not interrupt even though if we enable the barge IN . could you please anyone help us to achieve this configurations in the form element , is it possible? 

 

Thanks!!!!! 

1 Accepted Solution

Accepted Solutions

You might be able to break this into multiple Form elements.
Form01 - set the DTMF Keypress: 1 2  3 4 5 6  and set MaxNoInput Count to 1. Allow bargein.  If the caller doesn't enter anything connect the max_noinput exit state to another Form element Form02.
Form02 is configured just for DTMF Keypress: 7 (or perhaps:  1 2 3 3 4 5 6 7). Set MaxNoinputCount to 1. Disallow bargein on the audio group. Connect max_noinput exit state to another Form element Form03.
Form03 is configured just for DTMF Keypress: 8. Set MaxNoinputCount to 1. Disallow bargein on the audio group.

 

Then determine how you want to handle any other errors.

View solution in original post

8 Replies 8

janinegraves
Spotlight
Spotlight
I don't think it's possible to allow 1-6 to bargein, but 7-9 not to bargein.

thanks for your quick update on this, in the same element we cannot have two bargin IN  control, i am aware , my main ask is there way we can restrict any of the digit by defining something in form element? 

The only thing I'm aware of is that you can configure which DTMF tones
are valid, the others will cause a NoMatch event.

if i want to validate the DTMF 1 to 6 in the same element how we can achieve this in cisco elements, apart from this if customer press any other options we should not interrupt , this is my main ask . how we can achieve this in cisco.

This may be a basic question, but what are you looking for from a caller experience?

So like @janinegraves mentioned, if you have it be no match, you don't have to play no match audio, but otherwise how is the caller to know they are entering in something bad?

In other words, if caller presses 1-6, great, no problem, move onto the next node.

If caller presses 7, in your ideal world, what do you want to have happen? Aren't you going to want to play a no match type of message saying that isn't a valid entry? You don't have to do that, you could simply plain the initial message again and loop it for instance.

This may be a basic question, but what are you looking for from a caller experience? we have 8 options , first 6 options customer can interrupt and last 2 options customer wont interrupt. 

 

I think above one will give you clear pictures, please let me know if you need any other info for this.

 

You might be able to break this into multiple Form elements.
Form01 - set the DTMF Keypress: 1 2  3 4 5 6  and set MaxNoInput Count to 1. Allow bargein.  If the caller doesn't enter anything connect the max_noinput exit state to another Form element Form02.
Form02 is configured just for DTMF Keypress: 7 (or perhaps:  1 2 3 3 4 5 6 7). Set MaxNoinputCount to 1. Disallow bargein on the audio group. Connect max_noinput exit state to another Form element Form03.
Form03 is configured just for DTMF Keypress: 8. Set MaxNoinputCount to 1. Disallow bargein on the audio group.

 

Then determine how you want to handle any other errors.

Thank you very much .... I got the flow now