Help desk ticket workflow for a small team: set one up in five steps
A practical guide to building a help desk ticket workflow without big software: where requests come in, a five-status model, how to triage and prioritize, how an owner works a ticket, and a weekly review that turns repeats into fixes.

When a business is small, customer questions arrive everywhere: a shared inbox, a text to the owner, a message in a chat tool, a comment on a social post, a phone call that someone scribbles on a sticky note. For a while that works. Then two people answer the same email, a request sits untouched for a week, and a customer writes, "Has anyone looked at this?"
A help desk workflow fixes that without needing a big team or an expensive system. It is simply an agreed way to capture every request, decide who owns it, move it through clear stages, and close it. This guide shows you how to set one up for a team of two to fifteen people: what a ticket is, which statuses you need, how to prioritize, and how to review the whole thing each week. It is general guidance, and the examples come from published practice at universities that run large service desks, scaled down for a small business.
What a help desk workflow actually is
A "ticket" is just a record of one request: who asked, what they need, who owns it, and where it stands. A "help desk" is the habit of turning every request into a ticket and working through them in order of importance.
The three jobs of a ticket system
- Capture: nothing gets lost, whichever channel it came from.
- Ownership: every ticket has one named person responsible at any moment.
- Visibility: anyone can see what is open, what is waiting and what is done.
If your setup does those three things, it is a help desk, whether it lives in a dedicated tool, a shared board or a spreadsheet.
When you are ready for one
You probably need a workflow when requests regularly get answered twice or not at all, when customers have to chase you, or when you cannot say how many open issues you have right now. If you receive only a handful of requests a week, a simple shared list may be enough.
Step 1: Decide where requests come in
The more doors you have, the more things fall between them. Choose a short list of official channels and make everyone use them.
A sensible small-team set
- One support email address, shared by the team rather than one person's inbox.
- A web form on your site, so requests arrive with the details you need.
- Phone and chat, with a rule that whoever takes the call creates the ticket straight away.
Collect the right details up front
A good intake form asks for the customer's name and contact details, the order or project involved, what they expected, what happened, and how urgent it is for them. A few required fields save many back-and-forth messages later.
Step 2: Use a small set of statuses
Resist the temptation to invent twenty statuses. Boston University's information services team publishes its ticket lifecycle, and the core set is short: a ticket starts as New, becomes Assigned once it has an owner, can be placed On Hold while waiting, and moves to Resolved when the work is done. Their status guide also shows a useful detail: if a customer replies on a resolved ticket, it returns to Assigned rather than staying closed.
A five-status starter model
| Status | Meaning | Who moves it | |---|---|---| | New | Captured, not yet owned | The system or whoever logs it | | Assigned | Has one owner and is being worked | The triager | | On hold | Waiting on someone else, with a reason | The owner | | Resolved | Fix delivered, awaiting any reply | The owner | | Closed | Confirmed done, or no reply after a set time | Owner or automatic |
Require a reason for "On hold"
The same Boston University guide asks staff to give a code explaining each hold, such as waiting for the client, waiting for a vendor, or work scheduled for an agreed time. This stops "On hold" becoming a place where tickets go to be forgotten, and it makes clear whose move it is next. If the reason is "waiting on the customer," set a reminder to nudge them in a few days.
Step 3: Triage and prioritize
Triage means reading each new ticket once, quickly, and deciding three things: what kind of request it is, how urgent it is, and who owns it. Appoint one person per day or per week as the triager, so tickets do not wait for "someone" to notice.
Work out priority from impact and urgency
The Colorado School of Mines publishes service targets by priority. Its highest level covers widespread impact with high urgency, while its lowest covers one user with low urgency. You can borrow the idea: ask how many people are affected and how badly the work is blocked.
| Priority | Typical example in a small business | Target first response | |---|---|---| | Urgent | Customers cannot pay or log in; many affected | Within the hour | | High | One important customer is blocked | Same business day | | Normal | A question or minor fault, workaround exists | Within one business day | | Low | A request or idea, no deadline | Within a few business days |
These are example targets to adapt, not a standard. Our guide on response-time standards and escalation rules explains how to choose numbers you can really meet.
Keep priority honest
If everything is urgent, nothing is. Make "urgent" mean something specific and review how many tickets get that label each week.
Step 4: Work, resolve and close the loop
Once a ticket is assigned, the owner's job is to move it forward or say clearly why it cannot move.
A simple routine for the owner
- Read the whole thread before replying, so you do not ask for things the customer has already given.
- Reply with what you will do and when, even if you cannot fix it yet.
- Add internal notes about what you tried, for the next person who touches it.
- When done, mark it Resolved and tell the customer what changed.
- Close it after a set period with no reply, such as a few days.
The Mines service targets track two clocks, one for the first response and one for resolution, and the clock pauses while a ticket waits on someone outside the team. Even if you do not formalize targets, keeping those two ideas separate helps: reply quickly, resolve properly.
Hand off, do not hand over blindly
When a ticket needs someone else, such as billing or the person who built the project, reassign it with a short note rather than forwarding an email. The new owner should never need to ask the customer to start again. That is the same principle we describe in our guide to handling angry customers.
Step 5: Review weekly and improve
A help desk that is never reviewed only gets busier. Spend twenty minutes each week looking at four numbers:
- How many tickets are open, and how many are older than your target.
- How many are On hold, and for what reason.
- The most common request types this week.
- Any ticket that bounced between owners more than once.
Turn repeats into fixes
If the same question appears five times, write an answer once and publish it. Our guide to a customer FAQ and knowledge base shows how. If one product or process generates most of the tickets, the real fix is upstream.
Common mistakes
- Too many channels. Requests spread across personal inboxes cannot be seen or counted.
- No single owner. "The team" is not an owner.
- Too many statuses. If people cannot remember what each means, they stop using them.
- Silent holds. On hold without a reason is a hiding place.
- Never closing tickets. An endless open list hides what matters.
- Measuring speed only. Fast, wrong answers create repeat tickets.
Where WorkBOS fits
WorkBOS does not claim to be a dedicated help desk product, but many small teams can run a light version of this workflow with the pieces it has. A form on your site can collect requests, tasks can hold the owner, status and due date, the CRM keeps the customer's history in one place, and chat lets the team discuss a case without cluttering the customer thread. Automations can remind an owner when a ticket has waited too long, and roles and permissions control who sees what. See pricing for plans, including a free one, and the docs for set-up details. If you are weighing whether to consolidate tools, our guide to running your business from one platform may help.
Frequently asked questions
Q: Do I need special help desk software? A: Not at first. A shared inbox plus a board or spreadsheet with owner, status and due date can work for a small team. Move to a dedicated tool when volume or complexity outgrows it.
Q: How many statuses should I use? A: Five is plenty to begin with: New, Assigned, On hold, Resolved and Closed. Add more only when you can name a real decision that depends on the new status.
Q: Who should triage tickets? A: One named person at a time, rotating daily or weekly. Their only job at triage is to decide type, priority and owner.
Q: Should customers see their ticket status? A: It helps if you can do it cheaply, since customers chase less when they can see progress. If not, an acknowledgement with an expected reply time does most of the work.
Q: How do I know the help desk is working? A: Fewer repeat contacts, fewer tickets past target, and customers who stop asking whether anyone has looked at their request.
Sources are linked in the text above: Boston University Information Services and Technology, Colorado School of Mines.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →