Support glossary: the words behind the workflow.
Plain-English definitions of the customer support terms that come up when you move from a shared inbox to a helpdesk. No jargon, no fluff. Each term has its own short page with how it works, why it matters and the related ideas worth knowing, written for small UK teams who answer customers from email.
Plain-English definitions · Email-first, UK-focused · A reference, not a sales pitch
What this is
The support vocabulary, defined in plain English
When a shared inbox stops coping and you start looking at a helpdesk, the language changes quickly. Tickets, SLAs, deflection, collision detection, sender authentication: useful ideas, often buried under jargon. This glossary defines each one in a sentence or two, then sends you to a short page if you want the detail.
A shared inbox is a single mailbox, like support@ or info@, that several people watch and reply from. It works at first, then starts to creak: two people answer the same email, others quietly fall through, and nobody can say who owns what. A help desk turns those emails into owned, trackable items called tickets, so each one has a clear owner, a state and a history.
Most of the terms below describe parts of that shift. Some are about keeping response times honest, such as first response time and the SLA that sets a target for it. Some are about getting email to arrive at all, such as SPF, DKIM and DMARC. Others describe how a team avoids treading on each other, such as collision detection, or how work moves between people, such as escalation. A few cover the security and trust side: an audit log, where your data lives, and who else processes it.
You do not need to learn all of this to run support well. Read the few that match the problem in front of you, and come back to the rest when you need them. Every definition is general and applies whatever tool you use; where Solves happens to do something a particular way, we mention it lightly and move on.
A quick reference to start with
| Shared inbox | A single mailbox several people watch and reply from, with no built-in sense of ownership or state. |
|---|---|
| Help desk | A tool that turns support emails into owned, trackable tickets with states, history and reporting. |
| Support ticket | A single customer request, owned by one person, with a state, a thread of replies and notes, and a history. |
| SLA | A service level agreement: a target for how quickly you respond and resolve, measured against the clock. |
| First response time | How long a customer waits for a real first reply, the single most-watched support metric. |
All terms
Pick the term you want defined
Fourteen entries, grouped loosely from the move itself, to deliverability and reporting, to trust and security. Read them in any order.
Shared inbox
A mailbox like support@ that several people watch together. Where most teams start, and what they eventually outgrow.
Read the definitionHelp desk
A tool that turns support emails into owned, trackable tickets with states, history and reports. What you move to next.
Read the definitionSupport ticket
A single customer request with one owner, a state, a thread of replies and private notes, and a full history.
Read the definitionSLA
A service level agreement: a target for how fast you respond and resolve, measured against the clock.
Read the definitionFirst response time
How long a customer waits for a real first reply. The metric most teams watch before any other.
Read the definitionCanned response
A reusable, pre-written reply you can drop into a ticket and tweak, also called a saved reply or template.
Read the definitionSPF, DKIM and DMARC
The three DNS records that prove your support email is really from you, and decide whether replies land or bounce.
Read the definitionTicket deflection
Answering a customer before they ever open a ticket, usually with self-service or a clear help article.
Read the definitionCollision detection
A warning that stops two teammates replying to the same ticket at once and sending a customer two answers.
Read the definitionEscalation
Moving a ticket to someone better placed to handle it, by skill, seniority or urgency, without losing the thread.
Read the definitionTicket lifecycle
The states a ticket passes through, from new to open to resolved and closed, and what each one means.
Read the definitionAudit log
An append-only record of who did what and when, so any change to a ticket or account can be traced after the event.
Read the definitionData residency
Where your data is physically stored and processed, and why that matters for UK and EU privacy rules.
Read the definitionSub-processor
A third party your support tool relies on to process some of your data, such as a hosting or email provider.
Read the definitionHow to use it
Match the term to the problem in front of you
There is no right order to read a glossary, but a few clusters tend to be useful together. If you are weighing up whether to leave a shared inbox, read shared inbox, help desk and support ticket as a set: between them they describe the whole move from a crowded mailbox to owned work.
- Leaving a shared inbox: start with shared inbox, help desk and support ticket.
- Keeping response times honest: read first response time, then SLA.
- Getting replies to land: SPF, DKIM and DMARC is the one to read.
- Working as a team without clashing: collision detection and escalation.
- Understanding states and history: ticket lifecycle and audit log.
- Security and trust questions: data residency and sub-processor.
Each entry opens with the definition, then keeps the rest short: how it works, why it matters, the related terms, and a few common questions. Where a term maps onto something Solves does, we note it briefly. Solves is an email-first helpdesk, so it covers owned tickets, wall-clock SLA timers, multi-brand and the trust basics, and it does not pretend to do live chat, phone or social.
Definitions first, product second
These pages exist to explain the term, not to sell. Where Solves does the thing a definition describes, we say so plainly and keep it short, and we only mention features that are actually shipped. If a term covers something we do not build, we leave the product out of it entirely.
FAQ
About the glossary
What is a support glossary?
A support glossary is a short reference that explains the everyday terms used in customer support, written in plain language rather than vendor jargon. This one covers the words you meet when you move from a shared inbox like support@ to a proper helpdesk, so you can read a comparison page, a DNS guide or a pricing table and know exactly what each term means.
Do I need to know all these terms to run support?
No. You can run a small support desk perfectly well knowing only a handful: a ticket, a shared inbox, first response time and an SLA will get you a long way. The rest are useful when you start tuning deliverability, reporting or multi-brand work, so treat the glossary as a reference to dip into rather than a course to finish.
Which terms matter most when leaving a shared inbox?
Start with shared inbox, help desk and support ticket, which describe the move itself. Then first response time and SLA, which is how you keep response times honest. If your replies are landing in spam, read the SPF, DKIM and DMARC entry next. Everything else builds on those.
Are these definitions specific to Solves?
The definitions are general and apply whatever tool you use. Where a term maps onto something Solves does a particular way, such as wall-clock SLA timers with a breaching view or an audit log of who did what, we say so plainly, but the underlying meaning stands on its own.
How often is the glossary updated?
We add and revise entries as the product ships features and as common support practice changes. Definitions are kept deliberately stable, since the meaning of a ticket or an SLA does not move much, while examples and related links are refreshed as the rest of the site grows.
From the vocabulary to a working support desk
Once the terms make sense, the move is simple: forward your support address into Solves and start owning your email. Start at £29, or let us help you set it up.