I am revisiting this, as this also relates to conditional branching, although it seems a bit more complicated than when I asked the question a few months ago.
I have a SurVo where I am going to process a credit card. I ask the caller to enter their credit card number. I want to prompt the caller to enter the security code. However, I don't want to have to ask them what type of card they have. There are conventions for telling what type of card you have by looking at the first few digits of the number. However, for this purpose its even more simple. An American Express card is the only typical card where the security code is in a different place. And an American Express card is 15 digits where Visa, MC, and Discover are all 16.
So my suvo looks something like this
...
12: Please enter your credit card number.
13: Please enter your expiration date.
{if the string length of the answer to question 12 is 16, go to 14. If the string length of the answer to question 12 is 15 go to 15.}
14: Please enter the 3 digit security code from the back of your card.
{go to 16:}
15: Please enter the 4 digit security code from the front of your card.
{go to 16}
16: Please enter the amount...
I just can't figure out how to do this conditional branching. This is elementary programming, and the constructs have been available in every language I have used. I looked into the "advanced branching" and setting the threshold based on whether the caller enters 15 or 16 digits. But so far I haven't been able to use that approach either. Is there a way to do what I'm wanting here?
-- Edited by AnswerSoft on Saturday 9th of April 2011 04:06:20 PM
I'm not sure that advanced branching is going to meet your needs here. I think the two choices are :
1 - Break apart the call flow into multiple Survo's. You can evaluate the string length as part of a script that is hit with the NetGet. Redirect back and get the rest of the information and supply a Text to Speech message using User Parameters with 'three digit' or 'four digit.'
2 - Don't prompt for the specific number of digits.
I dont' think we have anything in the near term that is going to address this issue. Generally speaking, I know a revamp of the Survo is on the horizon, but I have not heard of adding a check for string length of a question type with separate threshold values as part of it.
