notify users - Githubissues

sodiumjoe commented 7 years ago

daily?

edhille commented 7 years ago

I would assume so

edhille commented 7 years ago

Started to dig into how sending SMS messages works and I think we have two routes:

1) The roll-our-own

You have to send the message through a gateway that is carrier-specific
In order to know which carrier a number is associated with, we'd need to send a confirmation text to every known gateway when a user applies. Only one will succeed and we note that with the User
When time to send a notification, use the User.carrier_gateway
- we'd need to account for users changing carriers and so capture errors and somehow let the user know (resend the confirmation message perhaps)

2) Use Twilio

They have a SMS API: https://www.twilio.com/sms
The pricing appears to be $1/mo + $0.0075/msg (https://www.twilio.com/sms/pricing)

Since we're currently footing the bill, I'm tending towards approach #1, but that is going to be a lot more work and more error-prone...

edhille commented 7 years ago

Also, there is another OS alternative called Kannel that I have not dug into too much but looks fairly old, so I'm a little concerned it might be out of date

sodiumjoe commented 7 years ago

I vote for twilio. seems like the cost will be negligible vs hosting unless we get massive adoption, which we can deal with if it happens

edhille commented 7 years ago

Going the Twilio route.

Should this handle all notifications? Meaning, should it also be responsible for verification emails?

sodiumjoe commented 7 years ago

oh I didn't realize twilio did email too, I'll check it out

edhille commented 7 years ago

Oh, I didn't mean that. I just meant that should the notifier library should own emails as well as sms.

sodiumjoe commented 7 years ago

oh gotcha. Yeah, that probably makes sense. let's talk about it tomorrow

sodiumjoe / citizen-advocate

notify users #5