A helpdesk built for a small UK team, not a per-seat trap.

For a small UK team, the best helpdesk is the smallest tool that turns your shared inbox into owned, timed tickets, prices in GBP, runs first-response and resolution SLA timers with a breaching view, and does not charge a full seat for an occasional helper. Solves is built for exactly that: email-first ticketing, multi-brand from one queue, and GBP team bands with no per-seat penalty.

Small teams are the default audience for Solves, not an afterthought. The product assumes you have a handful of people, one or several brands, and support email coming into addresses like support@, info@ or accounts@. It turns those shared inboxes into tickets you can own, assign, time and report on, without bolting on chat widgets, phone queues or automation engines you will never staff.

The pricing model matters as much as the features. Most helpdesks charge per agent per month, usually in US dollars, so the colleague who jumps in on a busy Monday costs you a full extra seat. Solves uses GBP team bands ex VAT, so you pay for a band of usage and let people help without watching the bill climb every time someone touches a ticket.

No per-seat penalty	You buy a team band, not a stack of seats. The occasional helper, the owner who dips in at weekends, the part-timer on overflow: none of them adds a per-seat charge.
GBP, ex VAT	Pricing and invoices are in GBP with VAT visible, so there is no currency conversion to track or reclaim and budgeting is straightforward for a UK business.
SLA timers	First-response and resolution timers with per-brand or organisation targets, and a breaching view that surfaces overdue tickets so nothing slips out of sight.
Email-first scope	One channel done well: owned tickets, assignment, notes, SLAs and reporting on email, without paying for chat, phone and social you are not staffing.
Multi-brand if you need it	Run one brand or several from one queue, each with its own mailbox, signature and saved replies, and never pay extra for capacity you are not using.

Nothing falls through the cracks

The first job is simply not losing messages. A shared inbox quietly hides this problem: an email gets opened, looks handled, and never gets a reply. Owned tickets fix it by giving every message a state and an owner, so a question cannot sit half-read for three days. A saved queue view of unassigned and waiting tickets means a quick morning scan tells you what needs picking up, without trawling a thread of two hundred emails.

Two people stop replying to the same customer

The second job is avoiding the embarrassing double reply, where two colleagues answer the same customer differently within minutes. Assignment and ticket states solve this: once a ticket is owned and moved to Open, everyone can see it is in hand. Private notes let the team talk through a tricky case where the customer cannot see it, and the hard separation between notes and public replies means an internal aside never lands in a customer's inbox by accident.

You can promise a response time and keep it

The third job is making a response-time promise you can actually keep, and then seeing when you are slipping. Solves gives every ticket first-response and resolution SLA timers with per-brand or organisation targets, and a breaching view shows what is overdue or at risk, so you can act before a customer chases.

Helpers can help without costing a fortune

The fourth job is letting the wider team pitch in without a punitive bill. In a small business the lines blur: the founder answers a few emails at the weekend, a part-timer covers overflow, someone from another team handles a specialist query. On a per-seat plan each of those people is a monthly charge. With GBP team bands you size the plan to your team and stop counting heads, which is the difference between encouraging people to help and quietly discouraging it.

It works for more than one brand if you grow into it

The fifth job, for some, is handling more than one identity. Plenty of small businesses run two storefronts, a main brand and a reseller line, or a shop alongside a separate services arm. Each wants its own look to the customer, but you do not want a separate helpdesk and login for each. One queue with brand badges, per-brand mailboxes and signatures, and a guard against replying as the wrong brand covers this without doubling your tooling. If you only have one brand, you simply do not use it.

The aim is to buy the smallest tool that does your real job, not the platform with the longest feature matrix. Here is what most small teams can leave for later, and why.

• Live chat, phone and social inboxes: powerful at scale, but they are channels you have to staff. If your customers reach you by email, paying for an omnichannel suite means paying for surfaces nobody is watching.
• Automation and routing-rules engines: rule builders look impressive in a demo and become a maintenance burden for a small team. Saved queue views and assignment cover most of what a handful of people actually need.
• Knowledge bases and customer portals: worth building once your ticket volume justifies self-serve articles. For a small team starting out, a well-run inbox beats a thin, out-of-date help centre.
• CSAT surveys and analytics suites: a small team usually knows when service is slipping from the queue itself. Open backlog, ageing and first-response reports tell you more, sooner, than a survey response rate.
• Developer APIs and integration marketplaces: genuinely useful at scale, rarely the deciding factor for a small team that just needs email handled properly today.

Solves takes the same view of itself and is honest about scope. It does not offer live chat, phone or social channels, an automation or routing-rules engine, CSAT, a customer portal, a knowledge base, custom fields, CSV export or a developer API. Those are deliberate omissions for a small email-first team, not features hidden behind a higher tier. If you genuinely need them now, a broader suite is the better fit and we would rather tell you that than oversell.

One honest exception: importing old tickets

Moving off a shared inbox is smooth, but importing historical tickets from another helpdesk is the one place to set expectations carefully. The Solves Freshdesk importer is in pilot and not a live transfer that reads a real account today, so bringing across old tickets is a guided, hands-on job for now rather than a one-click button. Forwarding your support address so new email arrives as owned tickets, on the other hand, works today.

You do not need a forty-column spreadsheet to choose well. Three questions narrow the field fast, and a short checklist confirms the fit. Answer them honestly about today, not about a hypothetical future you may never reach.

1. Name your one main support channel right now. If it is email, an email-first tool will be cheaper and calmer than an omnichannel suite.
2. Decide whether GBP billing and built-in SLA timers matter to your team. For most UK businesses they make budgeting and promises simpler.
3. Count the brands you answer support for. One is fine; more than one points you towards a single multi-brand queue rather than a login per brand.
4. Check the pricing model, not just the headline price. Per-seat plans punish helpers; a team band does not.
5. Trial it with live email before you commit, and watch how it feels on a busy day rather than in a tidy demo.

Match the tool to your channel, not the leaderboard

The single most useful decision is email-first versus omnichannel, and you should make it before you shop. A broad suite lets you add chat, phone and social as you grow, at a price that reflects that breadth. An email-first tool does one channel properly and costs less to run. If you know you will need chat or phone within the year, shortlist a suite. If email is your channel, an email-first tool like Solves will be cheaper and harder to get wrong. There is no shame in buying the focused tool; for a small team it is usually the smarter buy.

Read free-tier claims carefully

Free plans are where buying guides get sloppy. Some vendors offer a genuine forever-free plan with caps; others offer a time-limited window and call it free. Solves holds itself to the same standard: its Starter at GBP 29 is paid from the start, for small teams, not a free-forever plan. For a balanced, named comparison of which competitors have a real free tier and which do not, read the dedicated round-up linked below; this page keeps to the model rather than dated competitor figures.

Plan for the team you have, with room to grow

Size the plan to the team you actually have today, not the team you hope to have. With GBP team bands you can start on Starter or Team, add helpers without per-seat charges, and step up a band only when your real usage grows into it. Annual billing is twelve months for ten if you would rather commit. The first paid customers in the early-adopter pilot get Team at GBP 49 a month for six months, then GBP 79, with setup help and saved-reply migration in exchange for feedback.