CODEWITHSUNDEEP
timeouttwilio
Lili
Lili

Reputation: 23

Twilio <Gather> enhanced attribute

I used widget in my project to receive the person answers on a phone call and based on the respond it proceeds to the next step. The responds are limited to 'yes' and 'no'. I noticed most of the time, the 'timeout' situation happens in step which prevents the flow to go to the next step which is 'split based on'. It means it does not receive the answer no matter how the person says the word. I looked for the possible solution and I came across the premium speech model by adding the enhanced attribute. I'm not sure know if it is the solution or there is a better way to overcome this issue. any suggestion in this matter would be much appreciated since I couldn't find anything helpful through my google search.

Upvotes: 0

Views: 301

Answers (2)

Alan
Alan

Reputation: 10771

For Studio, place the Text to speech in the Gather Input on Call Widget rather than a Say Widget, that will accomplish what @jack has mentioned in Studio (allow you to barge into the conversation for speech or DTMF collection). Studio doesn't currently support Enhanced Gather.

You can look at the Studio Execution logs, to see what the Gather Widget received as Input (SpeechResult) or the Split Based on Widget, to see what it received and what it is comparing to based on your logic. Sometimes, Yes or No may end in a period for example, but you are looking for Yes or No (.)

Widget Library

Understanding Twilio Studio Flow

Upvotes: 1

jack
jack

Reputation: 348

make sure <Say> or <Play> are nested in the tag like this

<Response>
<Gather>
<Say>Please say Yes Or No</Say>
</Gather>
</Response>

not like this

<Response>
<Gather>
</Gather>
<Say>Please say Yes Or No</Say>
</Response>

If you can share some images or code, it would be helpful.

Upvotes: 0

Related Questions