Page 1 of 1

Bargein setting on forms

Posted: Tue Jan 23, 2018 5:07 pm
by jverweij
We are experiencing some unusual behavior.
We set up two scratchpads in our dev account Barge In 1 and Barge In 2. Both set a global property disabling barge in. Are you able to view our scratchpads?

Barge In 1 has 3 prompts in 3 blocks. Each prompt sets bargein in a prompt attribute. They alternate false true false.
Expected:
The first prompt cannot be interrupted
The second prompt can be interrupted
The third prompt cannot be interrupted.

Actual:
No prompts can be interrupted

Barge In 2 has 4 prompts in 4 blocks. Each prompt sets bargein in a prompt attribute. They alternate false true false true.
Expected:
The first prompt cannot be interrupted
The second prompt can be interrupted
The third prompt cannot be interrupted.
The fourth prompt can be interrupted

Actual:
The first prompt cannot be interrupted
Any of the remaining 3 prompts can be interrupted


Is the actual behavior what we should expect or is that a bug or the way we have things set up?

Re: Bargein setting on forms

Posted: Thu Jan 25, 2018 8:27 am
by support
Hi,

We advise against mixing bargein types for prompts that will be concatenated as it will result in ambiguity in how the caller will be able to interact with the IVR.

Regards,
Plum Support

Re: Bargein setting on forms

Posted: Thu Jan 25, 2018 9:13 am
by jverweij
That aside, is that expected behavior with how we have it set up. It seems like it may be a bug?

Re: Bargein setting on forms

Posted: Fri Jan 26, 2018 11:03 am
by support
Hi,

Given that mixed barge-in types result in ambiguous functionality, it is hard to say what is an expected behavior. To ensure things work as expected, we suggest using one type of barge-in.

Regards,
Plum Support