[VoiceOps] Service notification lists (outages, etc)

[Henning Westerholt]

Hello,

Doing a yearly mailing to the old members of the list is how its usually done in larger IT organisation. Some of them also have internal tools, e.g. I am interested and want to subscribe to all network changes, I am interested in all VoIP changes etc.. You could of course also build something like this with the mentioned tools.

Cheers,

Henning

-

From: Carlos Alvarez <caalvarez at gmail.com>
Sent: Wednesday, August 31, 2022 6:20 PM
To: Henning Westerholt <hw at gilawa.com>
Cc: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Service notification lists (outages, etc)

Yeah, those are good for the actual sending, but the maintenance was my primary question.  Wondering how others keep updated.  I suppose I can just do a mailing yearly and say "please respond with any changes."  But again, curious whether others have clever solutions.


On Wed, Aug 31, 2022 at 9:14 AM Henning Westerholt <hw at gilawa.com<mailto:hw at gilawa.com>> wrote:
Hello,

maybe I’ve got your question wrong, but I think most people in this area just use something like mailchimp, cleverreach etc.. to send out periodic mailings and maintain lists.

Cheers,

Henning

From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> On Behalf Of Carlos Alvarez via VoiceOps
Sent: Wednesday, August 31, 2022 5:51 PM
To: VoiceOps <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Subject: [VoiceOps] Service notification lists (outages, etc)

How do you smaller players maintain lists to notify people of issues, planned outages, etc?  We can't get them to update 911, let alone who should get these.  Right now it's rather manual in our CRM.  It would be nice to send something out to the list say yearly, and ask them to update themselves with new employees or whatever.  For frame of reference, we're very small and would notify a couple hundred people, with events less than monthly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20220831/35f4ac27/attachment-0001.htm>