Table of Contents

Part I — Stakeholder Input

Chapter 3

Customer Support Team

"It takes months to find a customer and seconds to lose one." — Vince Lombardi

We had a saying at my IT company: "Those who say the customer is always right have never worked in IT." All businesses have demanding clients, but none are more trying than the ones with a direct line to your personal cell phone — and no demographic perfects this art quite like family members who are also subscribers to your service.

In the nineties, I co-founded the first company to track legislative information on the Internet. My father, a longtime and well-respected lobbyist, became our first subscriber. His patronage was crucial in a niche market deeply skeptical of this new-fangled SaaS model. For over a year, things operated smoothly.

Then came the 5:00 a.m. phone call. My father was furious that he couldn't load a document in the portal. We worked through every troubleshooting step — including the dreaded "is the computer plugged in?" inquiry, which never carries an upside.

The staffer eventually conveyed the problem with the careful diplomacy of a man walking a very thin wire. The service was almost certainly working fine. The issue was the monitor. My father had been using the screen as a surface for his Post-it notes. Someone had replaced his actual monitor with a realistic-looking plastic display prop — the kind used for marketing — and put the sticky notes back. I suggested the young man quietly pilfer a monitor from a junior partner's office and take the knowledge of the plastic monitor to his grave.

Every customer support team is a library of these stories. And beneath the humor are genuine data points — buried in ticket systems, embedded in interviews with support staff, and latent in conversations with key accounts. Some of the best intelligence for designing or retooling a SaaS platform lives in your support operation, waiting to be mined.

The final shape of your SaaS service must include an efficient system for reporting, auditing, and resolving issues. It must also reflect a clear-eyed assessment of what you'll have to support in order to maintain a high level of customer satisfaction over time.

Ways To Gather Customer Intelligence

◆ Use existing data. Ticket volume, category, and resolution time tell a story before you ask a single question. ◆ Solicit structured customer feedback. Surveys, NPS scores, and post-resolution follow-ups reveal patterns the individual ticket view misses. ◆ Customer journey mapping. Walk the entire experience from awareness through support resolution — from the customer's perspective, not yours. ◆ Direct input from the service team. Front-line support staff are often the most honest voice in the company about what is and isn't working. ◆ Competitive analysis. Study what your competitors' customers complain about publicly — those are your opportunities. ◆ Social media listening. What are people saying in community spaces, forums, and review platforms about your category? ◆ Keyword research. The questions people search for around your type of product are often the questions they never think to ask you directly.