Spike on RapidPro for customizing notifications messages

Description

Research RapidPro to determine how and if it supports requirements to customize notification messages

  • Result of this spike will be a review of RapidPro to determine if we will use this to customize notification messages.

Activity

Nikodem Graczewski 
January 8, 2019 at 5:01 PM

Nikodem Graczewski 
January 8, 2019 at 11:31 AM

I’ve taken a quick look at RapidPro and I think it’s not the tool we’re looking for. From what I have grasped, it looks like it deals with collecting data through SMS by building some kind of SMS-based forms. It feels like using it for simply sending SMS is a bit of an overkill and something that the tool wasn’t designed for.

Chongsun Ahn 
January 7, 2019 at 7:37 PM

As Sam is out sick today, I'll try to answer the questions as best as I can (as this is the first time I've heard of RapidPro):

  1. Probably not an official list, but the approach here would be to keep the Customizable notifications requirements in mind, particularly requirements 2 (SMS support) and 3 (customizable messages). We would spike on what RapidPro can do and see what matches up with what we want in that Epic.

  2. I suspect the output would depend on the results of the spike. If RapidPro doesn't really match what we are looking for, then it would probably just be a document that outlines the pros and cons. If it does match well, then we could potentially organize the work needed to implement and write tickets.

Nikodem Graczewski 
January 7, 2019 at 5:40 PM

  1. Do we have a list of requirements that RapidPro should support?

  2. What form should the review have? In other words what should be the output of this ticket? Should it be a document, a set of tickets or something else?

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Original estimate

Time tracking

3d logged

Sprint

Fix versions

Priority

Time Assistant

Created December 19, 2018 at 8:48 PM
Updated January 30, 2019 at 11:35 PM
Resolved January 23, 2019 at 1:46 PM