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
inclinedthough these days maybe snapchat is a a better
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,
Scaling the number of people being notified is important. Though I have no
delusions of grandeur and that will still be a small number relative to
many other companies. I do not expect to scale the number of
notifications, because they are either about outages, which we minimize, or
feature
Well, but presumably you're trying to come up with a scalable solution that
dimensions to a lot more than that. Half a dozen of almost anything can be
handled manually, but perhaps should not be.
-- Alex
--
Principal, Evariste Systems LLC (www.evaristesys.com)
Sent from my Google Nexus.
@voiceops.org> on behalf of Carlos
> Alvarez <caalva...@gmail.com>
> *Date: *Thursday, June 1, 2017 at 4:40 PM
> *To: *"voiceops@voiceops.org" <voiceops@voiceops.org>
> *Subject: *Re: [VoiceOps] How do you update/manage your notification
> contacts?
>
&g
<voiceops@voiceops.org>
Subject: Re: [VoiceOps] How do you update/manage your notification contacts?
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 unex
On Thu, Jun 01, 2017 at 01:40:36PM -0700, Carlos Alvarez wrote:
> 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.
In the logic of our new system, we designate who the standard "need to
know
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,
We're not a VoIP service provider, but we manage infrastructure for
them. We're working on an internal OSS solution to streamline this.
On Thu, Jun 01, 2017 at 01:37:12PM -0700, Ryan Delgrosso wrote:
> Weve recently starting testing a statuspage internally http://staytus.co/
> and like it
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
Wouldn't it be both? A customer-facing interface of some sort to get them
to update their info, and an internal side where we are able to get all of
that data or send them notifications. I guess Mail Chimp is one possible
answer, but we also are interested in gathering multiple types of contacts
Are you talking internal or customer facing?
On May 31, 2017 3:59 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.
May 31, 2017 17:59
Subject: [VoiceOps] How do you update/manage your notification contacts?
To: <voiceops@voiceops.org<mailto:voiceops@voiceops.org>>
We're at the point where we really need to clean up and update our
notifications contact list (people to notify of outages, changes, e
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
14 matches
Mail list logo