Fichaloto

Blog Support

Six signals that support@ has run out of road

6 min read

A shared mailbox works remarkably well for far longer than tool vendors admit. And then it stops working all at once, always for the same six reasons.

The six signals

  • Nobody knows whose an email is. Two people answer the same thing, or nobody does, and both happen in the same week.
  • The thread dies on forward. The useful part of the conversation is in a forward that exists in one person's mailbox.
  • Nobody knows what is open. The answer to "where are we with Mendoza?" is to open the mailbox and read.
  • There is no response commitment. When a client asks how long things take, the answer is a feeling.
  • A client has no history. Nobody can see, before a renewal, the eleven times they wrote this year.
  • Support hours are not charged. This is the expensive one.

What a ticket needs, which is five things

And not many more. Most ticketing tools fail in a small company through excess rather than shortage: queues, forms, satisfaction surveys and automations for a team of three.

  • An owner. A person, not a group.
  • A status that is short and plain: open, waiting on the client, resolved. Three, not nine.
  • A response commitment per client tier, visible inside and out.
  • The client it belongs to, and from there their whole history.
  • The hours spent on it, booked against the ticket.

Two numbers, and why medians

Time to first response and time to resolution. Nothing else is needed, and both are read as medians rather than averages: one August ticket that stayed open five weeks moves the quarterly mean and makes you take the wrong decision.

With those two numbers you can hold two conversations that were not possible before: one with the client who wants a commitment, and one with the team when the commitment is missed.

The support hours nobody bills

In a professional services firm, support is real work done by the same people who bill projects, and it is almost always outside every calculation. Not because anybody decided to give it away, but because nobody books it: it is spread across twenty fifteen-minute emails.

Once a ticket accepts time bookings, two things surface at once. What it actually costs to keep each client, which changes renewal conversations. And which clients bought a support allowance and burned through it in March, which is a much easier conversation to have with a figure in front of you.

Moving without leaving anything open

The migration is not the history: it is whatever is live. What works is picking a date, opening a ticket for everything outstanding that day — usually fewer than expected — leaving the mailbox receiving for a month with an auto-reply that explains the change, and not looking back. Importing three years of email so that nobody ever reads it is the most common way for a migration not to happen.

Frequently asked questions

How big does a team have to be for this to pay off?

It is not team size, it is the number of clients who write in. Two clients and five staff: the mailbox is fine. Thirty clients and two staff: the mailbox is already dropping things.

Do we need a client portal?

Not at first, and it is a poor place to start: forcing a client into a portal to ask for help puts a door in the way. Keep email as a way to open a ticket and make the portal optional for clients who want to see their own.

What if the tickets are internal?

It works the same way and needs the same five things. The difference is that the response commitment becomes an internal agreement, and it is still worth measuring: internal support with no numbers is where requests go to be forgotten.

All of this is built into Fichaloto. See how it works.

Keep reading