Sending notifications is the easy part, lots of services for that. It's the maintenance of who the right contacts is which I find challenging. Since we see support tickets arrive from unexpected/new contacts, we know there must be people who need to know, but we don't know who they are.
On Thu, Jun 1, 2017 at 1:37 PM, Ryan Delgrosso <[email protected]> wrote: > Weve recently starting testing a statuspage internally http://staytus.co/ > and like it enough we will probably go live with it customer facing. this > allows us to have pre-formatted emails for different event classifications, > and the users opt in/out on their own. Its fairly extensible being written > in ruby, and has an API to take machine-generated events. > > Atlassian has their own as well if you want to pay atlassian money > > https://www.atlassian.com/software/statuspage > > > On 5/31/2017 2:58 PM, Carlos Alvarez wrote: > > We're at the point where we really need to clean up and update our > notifications contact list (people to notify of outages, changes, etc). > I'm curious what people here use. We use Freshdesk for our support > tickets, and that was a good list to start with, but as employees change it > wouldn't get updated necessarily. > > Something we can simply pay for and outsource is ideal. We're an open > source company, but time is a precious resource right now. > > > > _______________________________________________ > VoiceOps mailing > [email protected]https://puck.nether.net/mailman/listinfo/voiceops > > > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
