How to handle downtimes
Every app is going to go down at some point. No matter how good your team is you are going to have a major downtime. It’s not a question of “if” it’s a question of “when”. Even Google goes down from time to time. And when downtimes do happen, things get ugly quickly. These are going to be the hardest times for you and your customer support department.
Every serious outage causes loses. How much you lose depends directly on how your customer support agents have handled it.
How to prioritize your support queue
So, you come into work in the morning, open up your help desk app and see 50 tickets waiting in the queue. How do you go about responding in a most effective way? The obvious way is to handle old issues first — going bottom to top. That's what I was doing for a long time until I realized it's wrong. Oldest issues aren't always the most important ones.
Building a support site for your startup
You've already launched your product now it's time to set up a "self-service" help page for your users. Why?
According to Forrester, "72% of customers prefer self-service to resolve their support issues over picking up the phone or sending an email." Our own studies show (we keep an eye on these metrics since we're selling a helpdesk ticketing app) that up to 45% of support issues can be solved without contacting support. Of course it varies throughout specific niches and industries, but on average it's 45%. Which means - almost half of your support burden can be lifted.