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

Support for notifications #2107

Closed
MikeKMiller opened this issue Sep 22, 2016 · 11 comments · Fixed by #2295
Closed

Support for notifications #2107

MikeKMiller opened this issue Sep 22, 2016 · 11 comments · Fixed by #2295
Assignees
Labels
Milestone

Comments

@MikeKMiller
Copy link

MikeKMiller commented Sep 22, 2016

We currently use StatusPages.io and our users overwhelmingly utilize the SMS notifications over the email (i.e.. 5392 SMS, 297 email). This also comes into major play if services you are reporting on include email servers(i.e.. Exchange, Office365 etc...), as if they are down subscribers will not get notifications.

I recommend Twilio for this as it is dirt cheap, and extremely easy to integrate with, just about anything.

@ConnorVG
Copy link
Contributor

Thanks for the input, SMS notifications would be pretty swish. If we were to add SMS support, we wouldn't limit it to one service (like Twilio) though. This would be pretty easy to add with Laravel 5.3's notification system 😉

@MikeKMiller
Copy link
Author

The most common options are Twilio, Nexmo, and Plivo. I am not familiar with the programming interfaces of Nexmo and Plivo, so not sure of their level of difficulty for integration.

@MikeKMiller
Copy link
Author

Looking at the Doc's at the Larevel Notifications - SMS, It appears out of the box it supports Nexmo after getting the Nexmo library with composer.

@jbrooksuk
Copy link
Member

This is something we'll do once we've upgraded to Laravel 5.3 :)

@jbrooksuk jbrooksuk added this to the V2.4.0 milestone Oct 20, 2016
@ericvhileman
Copy link

SMS is killing feature! Our customers all want SMS notifications more than email :) We're a web hosting provider. Most of the time when we have a problem and need to notify a customer email won't work because the service affected has killed email. But even if email isn't killed, SMS is real-time and the best way to notify someone of an important problem. In today's world, even 5 minutes of downtime of an online service is a critical problem that requires SMS notification. You'll also likely see adoption from the status.io users too. I really hope this is released soon cause it's a killer!

@giubueno
Copy link

Is someone implementing it? I've created a handler and I will use a similar structure used to send e-mails to send the SMS. I am completelly new to Laravel. Some suggestions and advices would be great.

@CosmicPuppy
Copy link

Just wanted to chirp in that perhaps integration with a REST-API based notification service might be a suitable SMS alternative in some situations; or, at worst, an additional feature request.

Examples:

@jbrooksuk
Copy link
Member

I'm working on this 👍

@jbrooksuk jbrooksuk self-assigned this Jan 3, 2017
@jbrooksuk jbrooksuk changed the title Support for SMS Notifications Support for notifications Jan 3, 2017
@jbrooksuk
Copy link
Member

Since we're using Laravel 5.3, we're now making use of the new Notification system which makes these really simple to start integrating :)

@MikeKMiller
Copy link
Author

If I can be of assistance, let me know.

@MikeKMiller
Copy link
Author

One thing I would recommend, especially if we can integrate SMS reply handling, as one of the first SMS messages to a new SMS subscriber. Send a message like the following: "Reply with your email to be able to manage Email and SMS subscritions together", then you can add the phone number to the profile for the email if it already exists.

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

Successfully merging a pull request may close this issue.

6 participants