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.
We'd get exactly one subscriber, a 20 year old admin at one company. This
wouldn't be a useful thing for our type of customer in general.
Perhaps perspective is important, we generate maybe six such
events/notifications per year.
On Thu, Jun 1, 2017 at 2:30 PM, Matthew Crocker
Set up a status page, configure RSS and let your customers subscribe to the RSS
feed. Their responsibility to maintain notifications and they will drop off
when they are no longer interested.
Or, you could setup a couple twitter handles for notifications and have
customers follow them. No
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
10 matches
Mail list logo
