RapidPro & U-Report news: Categorizing “wait for response” actionsets’ filters
Less is more! Trust the power of a simple Wait for Response’s category
One of the greatest features of RapidPro resides at Wait for Response’s sorting options.
It can help your poll have a huge response rate and 100% accuracy if used correctly, but you can get in trouble if miss-typed words or actionset links.
Let’s overview the feature and understand best practices.
That’s a common Wait for Response:
The first column is related to the filter type, that is the rule used to validate the user message. Try it out and see there’s plenty more than just the usual “has any of these words”.
The second column is where you must enter the parameters that will be used to filter the content. Taking the usual “has any of these words” you can type many similar words that would be interpreted as the same category.
The third one is just the category name, or how all that previous values could be interpreted as. This is simple but very relevant, see why in the image below.
I will use numbers to demonstrate the feature, but it’s also applicable to strings.
It has a lot of different categorization filters, right? But see how it looks once done.
Well, that’s just a sample with no valid use in real life.
Now let’s improve it a bit more. Take a look at the image below and see if you can find the mistake? Some previous images also contain the same mistake…
Don’t cheat, think!
Take a look at the first categorization type, as the user types any numeric reply it will always be the system path chosen!
The has a number, highlighted in red, has a similar work as the has a number between, in purple. To filter users’ replies correctly that order must be changed.
My goal is to filter replies at 1 to 5 range differently from any other, but still having numeric values such as 2019. That can be done correctly, only using has a number between on the first categorization. Then, only if the range isn’t found, the ruleset searches for different categorization methods.
Using the right strategy you’ll be able to build flows to deal with many exceptions categories filtering the users’ replies to search for some piece of valid info. Like this:
Now, what you should avoid using
Capitalized characters are irrelevant as using commas to separate strings. So there’s no difference between this:
Another behavior that may put you in trouble is using more than one word/string without choosing the correct categorization type. See the image and look for the error:
As has any of these words categorization type is set, the Yes category option will never be filled! Because the same words are present in the first string, so the system will always use that category.
The correct type, in this case, is has all of this words. And most important, the order also matters! If inverted, the accuracy would also be compromised!
That’s it for today! Remember you can always reach us at [email protected]