[VoiceOps] How do you update/manage your notification contacts?
Ryan Delgrosso
ryandelgrosso at gmail.com
Thu Jun 1 20:57:38 EDT 2017
I still think a status page is the answer.
Opt all new customers in. Most solutions have opt-out links in the
emails. The rest as they say should solve itself.
Most status systems can support twitter outputs for the presidentially
inclined....though these days maybe snapchat is a a better notification
medium to reach young hip sysadmins, and have your outages be forgotten
about in 15 min.
On 6/1/2017 2:51 PM, Carlos Alvarez wrote:
> Well, that's really the question. I assume others are doing it with
> some success and could tell me what they do. Perhaps just an e-mail
> twice a year to all the contacts asking them to update themselves.
> These are customers who can respond to e-mails and click links, but
> they aren't using RSS, guaranteed, and may not be using Twitter and
> the like. Slack? Not a chance. The only universal thing would be
> e-mail.
>
> Also if we were hitting them with daily messages, such things would
> make sense. But nobody wants to monitor some channel for a message
> every other month.
>
>
>
> On Thu, Jun 1, 2017 at 2:48 PM, Alex Balashov
> <abalashov at evaristesys.com <mailto:abalashov at evaristesys.com>> wrote:
>
> So, if the customers aren't technically adept or very prudent, how
> are you going to get them to self-maintain a list of key contacts?
> Or did I misunderstand the goal?
>
> -- Alex
>
> --
> Principal, Evariste Systems LLC (www.evaristesys.com
> <http://www.evaristesys.com>)
>
> Sent from my Google Nexus.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
> <https://puck.nether.net/mailman/listinfo/voiceops>
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170601/840b7fd2/attachment.html>
More information about the VoiceOps
mailing list