twilio-org / toolkit Goto Github PK

Support ticket 1228900 requested the following functionality:

An admin sends a text to Twilio number:

remove {subscriber-phone-number}

and then the subscriber is removed from the broadcast list.

A common need for organizations doing field work is the ability to collect data from folks who may not have access to a computer, smartphone, or a reliable Internet connection. Examples might be:

• Collecting data from community health workers in rural communities
• Collecting data from social program participants in underserved communities

One approach to solving this problem is to replace web/mobile forms with an IVR system which collects responses to survey-style questions during a phone call. I'd propose a new Function template, using Sync as a data store, to power an IVR that would conduct a phone interview/survey. In addition, it should be paired with another Function which can dump the results of the survey to a CSV document for further analysis.

To define a survey, we might use a data structure like this (proposed):

const questions = [
  {
    question: 'Does anyone near you require medical attention?',
    type: 'boolean'
  },
  {
    question: 'How many people require medical attention?',
    type: 'number'
  },
  {
    question: 'Is there anything else first responders should be aware of?',
    type: 'speech'
  }
]

Definition of done:

• A Function which powers an IVR that collects answers to a survey during a phone call
• A Function which allows the survey data to be dumped into a CSV for processing/visualization
• Relevant documentation to allow users to set up the Function(s)

A common need for nonprofit orgs using Twilio is to coordinate ad hoc groups of volunteers (or volunteered supplies) over SMS. I believe a lightweight solution for this would be doable via SMS, backed by Twilio Sync as a data store.

Desired features:

• Create "events" via SMS
  -- upon event creation, optionally broadcast new event to all registered volunteers
• Associate "needs" with events
• Allow listing upcoming events via SMS
• Display needs for an event via SMS
• Allow volunteers to commit to covering all or some of a need for an event
  -- If volunteers attempt to volunteer for a need that's already covered, tell them so and say if there are other needs.
• Remind volunteers when their event commitment will be needed via SMS
• Allow volunteers to un-commit/cancel their commitment via SMS
• Upon cancelation, SMS registered volunteers to let them know that someone backed out, and requires backfill.
• Ability for admins to broadcast to all volunteers manually

Probable solution:

• Function that handles incoming SMS (bot interface)
• Function that will be executed on an interval to send out commitment reminders, for now using something like Zapier or IFTTT

Real world use case descriptions:
A group of chefs want to provide free meals at a shelter. They need 5 volunteers to show up, and they need 100 servings of fruit, 100 sandwiches, and 100 desserts. They need chefs to be able to volunteer and commit to bringing food via SMS.

A disaster relief org learns about a natural disaster. They need 10 volunteers immediately at the disaster site. An admin creates an event, and broadcasts all volunteers. Volunteers immediately respond, until all needs have been met.

Thanks for this toolkit app!

I am finding that when I try to broadcast a message more than 160 characters in length (sending from my iPhone) that the message is truncated. Is there a way to send one long message and have Twilio send it on intact?

Thanks,
Caleb