Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore and Integrate SMS #101

Open
daltonfury42 opened this issue Dec 19, 2020 · 0 comments
Open

Explore and Integrate SMS #101

daltonfury42 opened this issue Dec 19, 2020 · 0 comments
Assignees

Comments

@daltonfury42
Copy link
Collaborator

daltonfury42 commented Dec 19, 2020

When a new token is created, we want to send an SMS to the mobile number which was given. This SMS would have a link to the token status page, this will allow the person to know the live status while he is waiting, mainly the number waiting in front of him:

Hi <name>, 
You have been added to  <queue-name>. 
Live status: <token-status-link>.
Token number: <token-number>.

AWS SNS

AWS SNS lets you send SMS worldwide, and and their pricing is as follows (converted to Rupees):

Country Price per SMS
USA Rs 0.47
UK Rs. 2.86
India Rs 1.60
UAE Rs. 2.83
Random Other Country (Ukraine) Rs. 8.57

If we adhere to some India specific regulations which might require us to be a registered company, and also might require us to pay an additional registration fee (₹5900) then we can send SMS in India for Rs. 0.20.

Direct Integration With SMS Service Providers

We can integrate with an SMS service provider, whose API we can call to trigger the SMS. Integration is very easy, you just have to set up an account, pay as per their plan. A random example service I found for India is TextLocal

image

@akashkbaburajan was exploring this, and I think we will need to be registered as a company to send transactional SMSes.

Companion App to Send SMS

We could also let the queue owner install and set up a SimplQ companion app on his mobile phone to send SMSes in the background. This was discussed here.

Other thoughts

  1. Except in case of the companion app, SMS is a paid resource that we cannot leave open on a public site without protecting it, otherwise someone might use it to spam others or will simply consume our quota. We can get around this by allowing only logged in users to enable SMS, and if they want to send more that a certain amount of SMS, they would have to contact us offline and we can increase their limit.
  2. We would integrate multiple providers and use the best one per each region. Also we should enable SMS as a feature only for certain regions (for example, enabling SMS for Ukraine is very costly). So we might end up using AWS for UK and US, while another service like TextLocal for India etc.
  3. If the companion app is feasible, we can offload this responsibility to the user, and also keep the platform free for ever. We could always do all.

But SMS does seem like a good feature to have, from a product perspective.

@daltonfury42 daltonfury42 self-assigned this Jan 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant