Slack SLA and Support
Slack has done a remarkable job keeping up with its fast growth, and that extends to how the company has implemented its customer support and SLA offerings. Generally speaking, Slack handles support exactly how you might think it would: the more money you pay, the higher level of support you get. In the Slack for Teams product, free plans get standard support, mid-tier plans get priority support, and the highest tier (called Plus) receives 24⁄7 support.
Companies that move up to Slack’s enterprise offering, which it calls Enterprise Grid, receive the same 24⁄7 support, as well as a “dedicated account and customer success team” and more personalized support options.
If there’s one thing Slack could do a better job of here, it’s explaining the differences between these support levels—something it does not do either on its pricing website or in its documentation. The assumption might be that anybody not paying for a high-tier plan won’t care too much about support, but there is nonetheless a lot of room for interpretation with “standard” and “priority,” compared with the specific guarantees at the Plus level.
Notably, Slack is also one of only a handful of prominent SaaS companies—outside giant ones like Microsoft, Google, Salesforce and SAP—to publicly share details about its SLA for application uptime. Slack offers a 99.99 percent uptime guarantee for Slack for Teams Plus customers and Slack Enterprise Grid customers. Slack handles service credits a little differently than many companies: instead offering a portion of the monthly subscription fee for each percent (or less) below the promised uptime, Slack credits customers 100 times the amount they paid during the time the service was down.
In theory, this would mean that a company paying for 100 users on the Plus plan would receive approximately $173.61 in credits for an hour of downtime. ($1,250 / 720 hours in a month = $1.736 per hour.) However, Slack doesn’t calculate uptime on an individual level, but rather based on what percentage of users were affected. As the company explains:
This means that the service credits added to your account may not match your exact experience: when only a small minority of workspaces are affected, the downtime will average to a lower number and you may receive less than you expected. On the other hand, it also means you’ll receive credits for significant outages even if your workspace felt no impact. If you feel like a particular case was not handled correctly, don’t hesitate to contact us: we aim to please.
That practice might result in some disgruntled users, but Slack is at least clear in its explanation of how these calculations work. Additionally, customers who feel like they’ve been burned especially hard can always contact Slack support and try to work out a more satisfying arrangement.
This was published on Jul. 3, 2018.
Is a feature of your app EnterpriseReady?
We'd love to work with you to breakdown your implementation and share it with the EnterpriseReady community.