viciousfish/easysms

A simple way to send out mass SMS, originally developed for charities

EasySMS

Server Testing Status:

easysms's Issues

Implement password changing

Users should be able to change their password if they are authenticated

Add opt out functionality

When we receive a reply from Twilio, we should check for an opt out keyword and mark the user as opted out in their preferences

Router link items should only highlight one at a time

Send a generic help message if we have never sent a message to the user before

If the user has no preferences (we've never sent them a text before), then we should send a generic info message

e.g. "You have been added to a message list for ${orgName}. Reply STOP to opt out. Reply HELP to see this message again in the future."

Add a webhook for Twilio message delivery status

Twilio will send us a webhook when a message's status has been updated. We should store the twilio id of the message on the delivery object, and then update the delivery object whenever we receive a message from that webhook

Scheduled message time

Scheduled messages should have a time, not just a date

Animations should be slightly faster in the UI

Implement authentication

Title. Need to add authentication and login to the client side, and on the server side we need to properly and securely store passwords

Fix editing a message

Editing messages on the client doesn't send api calls or properly update state on the client side. A partial implementation is running on the branch update-message

Add twilio's authentication to twilio webhooks

https://www.twilio.com/docs/usage/tutorials/how-to-secure-your-express-app-by-validating-incoming-twilio-requests

More forgiving CSV parsing on the client side

We probably can just remove email. But we should specifically look for the phone numbers

A client should be able to see phone numbers associated with a campaign

• Currently after they click “My data looks good”, you can never see the numbers again except in reports