Discuss Home · Bootstrapped Podcast · Scribbleton Personal Wiki · HelpSpot Customer Service Software · Thermostat NPS

Remote customer support options


#1

Hi all.

One thing I love about a SaaS is how much easier it is for me to remotely support than a desktop app. But a problem I still occasionally encounter is trying to support users hardware, such as printers. For example my software prints to receipt printers via a POS screen.

But sometimes users just can’t manage to configure the hardware themselves and get it running. How do other people typically manage this? Do you remote desktop into users computers, keeping in mind they have a mix of Mac and PC’s? If so what software do you use? Any other hints for managing this?

One thing I am trying to do is set up a network of resellers so there will hopefully people locally to major cities who can come in and personally help out the users (for a price).

Craig


#2

Here’s my approach:

  • First, make sure you have excellent docs. eg. A how-to page for each specific printer problem with screenshots. The steps need to be clear, detailed, and illustrated with a screenshot for each step.
  • Second, create how-to videos showing the steps clearly. Making a good how-to video is an art: you need to be concise, and speak slowly and clearly, and resist that urge to move the mouse cursor maniacally over the screen in a rapid pace.
  • Third (and in answer to your specific question), use remote desktop software. I’ve tried Copilot and Team Viewer. Both work well on Mac and Windows.

Granting remote access is scary for some users. It is also a time sink. So once you’ve used remote desktop software to trouble-shoot a specific problem, do whatever you can to make sure it isn’t necessary again. That leads to the next step:

  • Fourth, modify your software to do the diagnostics/set-up stuff that you had to do manually. We’ve added a diagnostics screen to our flagship product, Poker Copilot, modelled on OS X’s “Network Preferences” dialog. It checks a few things on the computer, and for each, gives the user a green light or red light. For each red light, steps to solve the problem are given. This has reduced our support load, and has also given us a way to double-check that the user has followed each step properly. In your case, you could have a “help me print” part of your software, which walks the user through printing a test page.


#3

Thanks Steve. I tend to agree that the documentation approach is the best one. Every time a support question comes in I view it as a opportunity to improve the documentation or software to avoid the same question in the future.

Having to remote in is a real time sink that doesn’t really scale.


#4

I try to avoid remote access if at all possible.

  1. It uses up your time.
  2. The user might then blame you for something unrelated that goes wrong afterwards.
  3. The user might start to regard you as a free IT support desk.