What support tickets taught us about service businesses

Support teams answer the same twenty questions forever. The patterns they learn are the same patterns every service business could fix in an afternoon.

The BittaFlow team

3 min read

On this page
  1. 1. The same five questions, forever
  2. 2. Speed beats polish
  3. 3. The promise is the product
  4. 4. Handovers lose more than anything else
  5. 5. The angry ones are usually right about something
  6. What support teams get wrong too
  7. The one habit worth copying
  8. Where this shows up in a service business
  9. Where BittaFlow fits

Support is the least glamorous part of any software company, and the most honest. Every ticket is a customer telling you exactly where the product, the website, or the process failed them.

After a few hundred of them, the same lessons appear. They apply to almost any service business.

1. The same five questions, forever

Roughly eighty percent of tickets are one of a handful of questions, asked by people who could not find the answer.

The fix is never a better support team. It is putting the answer where the question starts: on the booking page, in the confirmation, at the top of the form.

Most service businesses have the same five questions. “Do you take insurance”, “how much is a call-out”, “can I park”, “how long will it take”, “what if I need to cancel”.

Each one belongs on a page, not in a person’s memory.

2. Speed beats polish

A fast, slightly rough reply is better than a perfect reply two days later. Customers forgive a plain answer. They do not forgive silence.

This is uncomfortable for people who care about doing things properly. The instinct is to wait until you have the full answer. The customer has usually moved on by then.

Send the holding reply. Then send the full one.

3. The promise is the product

Support teams learn this quickly: the time you quote matters more than the fix.

“Within four hours” and then two hours is a good experience. “As soon as possible” and then three hours is a bad one, even though it was faster.

Service businesses make the same promise on every call. Most of them do not track whether they kept it.

4. Handovers lose more than anything else

A ticket passed between two people loses context unless someone writes it down. The customer repeats themselves, and the second person starts from zero.

In a clinic, that is the patient explaining their history again. In a garage, it is the mechanic asking what the noise was.

The fix is boring: one record, notes that a stranger could read, and a rule that the next person reads before they call.

5. The angry ones are usually right about something

Not about everything. But there is almost always one true thing inside an angry message: a promise not kept, a message not returned, a bill that did not match.

Support teams learn to find that one thing and fix it, rather than defending the rest.

What support teams get wrong too

Worth saying, because the pattern is not all wisdom:

  • Treating volume as success. Answering a thousand tickets is not better than preventing eight hundred.
  • Closing tickets to hit a number. The customer is not done because the queue says so.
  • Hiding behind policy. “That’s our process” is a sentence that ends conversations and relationships.

The one habit worth copying

Write the answer down the first time you are asked.

Every support team has a knowledge base, badly maintained. Every service business has a front desk answering the same question from memory, twice a day, for years.

A shared note with the five common answers, written in plain words, is a morning’s work and it saves hours a month.

Where this shows up in a service business

  • A patient asking whether the practice takes their insurance, for the fourth time.
  • A client asking how long a colour takes, because the website says “varies”.
  • A customer asking whether the call-out fee includes the first hour.

None of these need a person. They need a page and a sentence.

Where BittaFlow fits

BittaFlow’s shared inbox keeps the history of every conversation, so a handover does not lose the thread. Common answers can be saved as replies, and the questions that keep coming back are visible in the conversation list.

Answer once, in writing. Then point people at it.

Useful? Send it to someone who runs the phones.