Peter Law
2016-11-11 18:57:55 UTC
Hi,
CC: Teams Coordinator for feature visibility
A suggestion Rob has apparently made is that we could capture the
phone numbers of Team Leaders and have them verify them by sending a
text with an access code - somewhat like we already do with emails.
This would allow event organisers and Team Coordinators to phone them
if needed.
While we already have some phone numbers in teams.git, those aren't
easily accessible to the people who might need them (not that they
should be widely accessible) and it's not clear whether they've been
verified.
I've had a quick look at the top 3 search results and it appears
fairly standard to pay 4 pence per text at the volumes we're looking
at (<1000/year) [1]. As a result I think we should make a choice based
on which provider has the best docs and API.
Given that nemesis/userman already has user details and a verification
flow for emails I propose building this there. The remaining question
is whether we also want to offer other messaging via SMS (e.g: event
reminders), or whether this is purely a mechanism to capture phone
numbers for humans to use, as this may affect the system design.
Thoughts?
Thanks,
Peter
[1] I compared https://www.textmagic.com/sms-pricing/,
https://www.twilio.com/sms/pricing/gb and
http://www.textlocal.com/uk-and-international-sms-text-prices. The
latter has a headline rate of 2.4p, but I couldn't see how to actually
achieve that.
CC: Teams Coordinator for feature visibility
A suggestion Rob has apparently made is that we could capture the
phone numbers of Team Leaders and have them verify them by sending a
text with an access code - somewhat like we already do with emails.
This would allow event organisers and Team Coordinators to phone them
if needed.
While we already have some phone numbers in teams.git, those aren't
easily accessible to the people who might need them (not that they
should be widely accessible) and it's not clear whether they've been
verified.
I've had a quick look at the top 3 search results and it appears
fairly standard to pay 4 pence per text at the volumes we're looking
at (<1000/year) [1]. As a result I think we should make a choice based
on which provider has the best docs and API.
Given that nemesis/userman already has user details and a verification
flow for emails I propose building this there. The remaining question
is whether we also want to offer other messaging via SMS (e.g: event
reminders), or whether this is purely a mechanism to capture phone
numbers for humans to use, as this may affect the system design.
Thoughts?
Thanks,
Peter
[1] I compared https://www.textmagic.com/sms-pricing/,
https://www.twilio.com/sms/pricing/gb and
http://www.textlocal.com/uk-and-international-sms-text-prices. The
latter has a headline rate of 2.4p, but I couldn't see how to actually
achieve that.
--
You received this message because you are subscribed to the Google Groups "Student Robotics Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to srobo-devel+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Student Robotics Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to srobo-devel+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.