How to run customer support for a small UK team.

Running support for a small UK team is mostly about structure, not headcount. One person with the right setup beats three sharing an inbox and hoping. The seven moves below take you from a shared mailbox no one owns to a queue where every message has an owner, a target and a record.

1. Set up a proper support address your customers write to.
2. Give every email a single owner, so nothing is everyone's job and no one's.
3. Separate the public reply from the private note, with a hard wall between them.
4. Set response-time targets against UK business hours, not a calendar clock.
5. Use saved replies for the questions you answer over and over.
6. Measure first response and resolution to see what is working.
7. Add a helper at the right moment, without a full seat for occasional cover.

You do not need an enterprise suite. You need ownership, a clean split of reply and note, honest targets and a couple of reports. The rest of this guide takes each move in turn.

Start with one clear address your customers write to, such as [email protected], not a personal mailbox or a tangle of forwards.

A shared support address gives customers one place to write and you one place to work from. The common mistake is to scatter support across a founder's personal inbox, a generic info@ address and a few forwards, so replies go out under different names and nobody sees the full picture.

You do not have to move your email hosting to fix this. Solves is forwarding-first: you point your existing support@ address at Solves, run the guided checks, and keep your current provider. Setup walks you through the DNS records in plain English, and live sending stays blocked until an address passes its checks or a recorded founder override is in place.

Why not just keep the shared inbox?

A shared inbox is fine until two people open the same email, or a customer chases a reply someone thought a colleague had sent: no owner, no timer, no record of who did what. Moving to owned tickets keeps the email feel and removes the guesswork. For the full walk-through, see the guide on turning a shared inbox into support tickets.

Assign each ticket to one person. Ownership is the single change that does most to stop messages slipping.

When an email is everyone's job, it is no one's. Assignment fixes that: one owner per ticket, visible to the whole team, so a customer never waits on a reply two people each assumed the other had sent. A ticket can be handed on, but always belongs to someone.

Tickets move through clear states as the work progresses: New, Open, Waiting for Customer, Snoozed, Resolved and Closed. Priority and tags let you sort the urgent from the routine.

Saved queue views keep the work visible

Rather than scroll one long inbox, your team works from saved views: New, Unassigned, Waiting, Snoozed, Breaching SLA, Resolved and All, each filterable by brand, mailbox, assignee, state, priority, tag and search. Unassigned earns its keep first thing, showing exactly what still needs an owner.

Keep the message the customer reads and the note your team shares in clearly different places, with no way to send one as the other.

The most embarrassing support mistake is sending an internal aside to the customer: the offhand comment, the discount you were not going to mention, the half-formed plan. Solves keeps a hard separation. A public reply goes to the customer; a private note stays inside the team. The composer makes which one you are writing obvious, and a guard stops a note going out as a reply.

One more safeguard matters for a busy team. A stale-reply check warns you if the ticket has moved on since you started typing, so you do not answer a question a colleague already handled. For the detail, see the guide on public replies and private notes.

Decide what good looks like, then measure against your real working hours, not a 24-hour clock.

A response-time target, often called an SLA, is simply a promise about how quickly you will reply. Decide the target that matches the hours you actually work, then hold yourself to it. Solves has first-response and resolution SLA timers, with per-brand or organisation targets set in minutes, so each ticket carries a due date you can act on.

A Breaching SLA view, alongside an ageing report, surfaces what is overdue, so the team can act rather than apologise.

How fast should a small team be?

There is no single right number, but a common, achievable target is a first reply within one business day, with urgent issues handled faster by priority. Set a target you can keep and let the breaching view hold you to it. For more, see the guide on setting a support email SLA.

Most support volume is a small set of questions asked again and again. Answer each one well once, then reuse it.

Where is my order, how do I get a refund, what are your opening hours, how do I reset my password: a handful of questions usually make up the bulk of a small team's inbox. Saved replies let you write a clear, courteous answer once and drop it in seconds, so the tenth person to ask gets the same quality as the first.

Saved replies can be scoped to a single brand or shared across the organisation. They are a starting draft, not an autoreply: you read and adjust before sending, so the customer still gets a human answer. Dynamic placeholders, such as automatically inserting a customer's name, are not built yet, so treat a saved reply as a vetted draft you personalise.

Two numbers tell you most of what you need to know: how long customers wait for a first reply, and how long until their issue is resolved.

First response time is how long a customer waits before they hear from a human; resolution time is how long until the issue is actually sorted. Track both and you can see whether your team is keeping up, where the delays sit, and whether a target is realistic. Solves reports on both, so you can see whether the promise you made is being kept.

A few more reports round out the picture: open backlog, ageing, waiting and created-versus-resolved together show how much is in flight, what is getting old and whether you are clearing work as fast as it arrives. You can filter by brand, which matters once you run more than one. A simple habit, the five D's of email management, then turns those signals into action.

Add a second pair of hands when the reports, not your gut, say one person can no longer cover the hours or volume comfortably.

The signals are in the numbers you already track. If first response time is creeping up, the ageing report is filling out, or the backlog is growing faster than you clear it, that is the case for help. Bringing someone in early is far easier than digging out later.

The usual blocker is pricing, because most helpdesks charge per agent, so the colleague who picks up overflow on a busy Monday costs a full monthly seat. Solves uses GBP team bands instead, so you size the plan to the team and let occasional helpers help without a per-seat penalty. A helper can be given notes-only access and limited brand visibility.

Moving your old support history across is on the roadmap. A guided Freshdesk import is in pilot, not a working one-click transfer today, so plan a move with that in mind and ask us for help. Setting up your support address and forwarding mail in, by contrast, is shipped and guided, so you work a clean queue quickly while a history import follows.