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 (billing, sales, tech) since they may not be the same. Most tech contacts don't want to hear about feature changes or billing, and those contacts don't really care about outages.
On Wed, May 31, 2017 at 3:42 PM, Mauricio Lizano <[email protected]> wrote: > Are you talking internal or customer facing? > > On May 31, 2017 3:59 PM, "Carlos Alvarez" <[email protected]> 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 list >> [email protected] >> https://puck.nether.net/mailman/listinfo/voiceops >> >>
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
