Fewer calls to support
An informed customer does not call to ask, and your team can focus on fixing the outage.
When a service goes down, your customers will find out anyway. The difference is whether you tell them first or they discover it by calling support.
An incident that is not communicated turns into a flood of calls: every affected customer asks the same question and your team repeats the same answer for hours. A message sent when the outage starts, and another when service is restored, stops that flood at the source and also shows that the situation is under control.
What changes day to day when this notice is sent by SMS.
An informed customer does not call to ask, and your team can focus on fixing the outage.
Send to the segment of your database that matches the affected area or service.
The "service restored" message is worth as much as the first one: the customer knows they can use it again.
The same channel works for announcing a scheduled shutdown days in advance.
For this use case, the channel we usually recommend is Bulk SMS.
Yes, by sending to the part of your database that matches the affected customers.
Yes, through the API, from your own monitoring system.
Yes. The system automatically adapts to the load and has several network connections: if one fails, the message goes out through the next.
Tell us what you need to send and we will tell you which of our services fits best.