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

Twilio Integration #3172

Closed
1 task done
Yodie98 opened this issue Dec 19, 2022 · 9 comments
Closed
1 task done

Twilio Integration #3172

Yodie98 opened this issue Dec 19, 2022 · 9 comments

Comments

@Yodie98
Copy link

Yodie98 commented Dec 19, 2022

Description

Delivering notifications to non-tech-savvy users has always been almost impossible for me. I don't want my users to download another app to receive notifications or anything. Ideally, an SMS message would be perfect

Desired Behavior

Having a way to integrate Twilio into Overseer in Settings > Notifications and users' phone numbers under User>Settings>Notifications would be an awesome way to notify users when their requests are available. A simple SMS message for notification delivery would be painless for them.

Additional Context

Potentially adding options for notifications on the confirmation page when requesting would be a good idea as well.

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
@SnippetSpace
Copy link

I'm using email. The email used for their plex accounts receives a notification when their request is fulfilled. Is this not sufficient?

@Yodie98
Copy link
Author

Yodie98 commented Dec 20, 2022

I'm using email. The email used for their plex accounts receives a notification when their request is fulfilled. Is this not sufficient?

Email would work but I honestly feel an sms message would be the ultimate form of notification. Twilio has a powerful api too so this would be easily implemented, I'd imagine.

@SnippetSpace
Copy link

SnippetSpace commented Dec 20, 2022

More options is of course always better. My point was just to say we already have a “painless” global notification system that requires no specific app.

@M91
Copy link

M91 commented Dec 26, 2022

you could push an email as a text you could do 1234567890@txt.att.net, every carrier has there own email address for texting.

T-Mobile – number@tmomail.net
Virgin Mobile – number@vmobl.com
AT&T – number@txt.att.net
Sprint – number@messaging.sprintpcs.com
Verizon – number@vtext.com
Tracfone – number@mmst5.tracfone.com
Ting – number@message.ting.com
Boost Mobile – number@myboostmobile.com
U.S. Cellular – number@email.uscc.net
Metro PCS – number@mymetropcs.com

@Yodie98
Copy link
Author

Yodie98 commented Dec 27, 2022

More options is of course always better. My point was just to say we already have a “painless” global notification system that requires no specific app.

Yeah you're totally right 👍🏻. I'm just weird 😂

@Yodie98
Copy link
Author

Yodie98 commented Dec 27, 2022

you could push an email as a text you could do 1234567890@txt.att.net, every carrier has there own email address for texting.

T-Mobile – number@tmomail.net

Virgin Mobile – number@vmobl.com

AT&T – number@txt.att.net

Sprint – number@messaging.sprintpcs.com

Verizon – number@vtext.com

Tracfone – number@mmst5.tracfone.com

Ting – number@message.ting.com

Boost Mobile – number@myboostmobile.com

U.S. Cellular – number@email.uscc.net

Metro PCS – number@mymetropcs.com

Good idea! I'll try that and see how it goes.

@mderubertis
Copy link

Can I suggest HTML5 notifications? If I'm not mistaken, the web app already has a service worker registered on the client.

@stale

This comment was marked as resolved.

@stale stale bot added the stale label May 1, 2023
@danshilm danshilm removed the stale label May 3, 2023
@stale
Copy link

stale bot commented Jul 15, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants