On this page
- 01Key takeaways
- 02What are the six stages?
- 03Where do queries usually wait?
- 04How do you design the handoffs?
- 05What does a mapped workflow look like?
- 06Where does outsourcing help most?
- 07When is a formal workflow too much?
- 08What does this look like in practice?
- 09Workflow checklist
- 10Next step
- 11Sources and further reading
- 12Frequently asked questions
Key takeaways
A customer service workflow is the set path every query follows from first message to closed. Six stages cover most small businesses: receive, triage, respond, resolve, close and learn. Each needs an owner and a target time. Most delays happen between stages, when a query waits for someone else, so design the handoffs as carefully as the replies.
- 6 stages: receive, triage, respond, resolve, close and learn.
- Each stage has an owner and a target time.
- Most delay sits between stages, not inside them.
- The learn stage cuts future contacts.
Want your customer service workflow mapped? Message us on WhatsApp.
Chat on WhatsApp →What are the six stages?
Every query, whether email, call or chat, passes through the same six stages. Writing them down makes ownership clear and shows where queries wait.
- Receive: the query lands in one place with a timestamp.
- Triage: it is categorised, prioritised and routed.
- Respond: the customer gets a first meaningful reply.
- Resolve: the issue is fixed, with any internal handoffs.
- Close: the customer confirms or the ticket closes after a set time.
- Learn: the reason is tagged and reviewed weekly.
Where do queries usually wait?
Queries usually wait at three points: before triage, when nobody owns the inbox; at resolution, when another team must act; and before closing, when nobody confirms the fix. Measure time at each stage for a sample of tickets to find which of these is your main delay.
How do you design the handoffs?
Design handoffs with a clear trigger, a named receiving team, the information they need and a target turnaround. A refund request passed to finance should arrive with the order number, reason and amount, and finance should have a target to act. Without targets, internal handoffs become the slowest part of service.
What does a mapped workflow look like?
In an illustrative e-commerce workflow, all messages arrive in a helpdesk, are triaged within 30 minutes, and get a first reply within two working hours. Order issues are resolved by the first line using authority limits. Refunds over £50 go to the owner's daily list. Tickets close after three days without reply. Tags are reviewed every Friday. Example design.
- Customer service outsourcing for UK e-commerce
- Customer feedback loop: turn complaints into fewer contacts
Want a workflow like this designed around your business? Send us your query types on WhatsApp.
Chat on WhatsApp →Where does outsourcing help most?
Outsourcing helps most at receive, triage and respond, where volume is high and the work follows clear rules, and in the routine part of resolve. A managed team can hold those stages to target every day. Keep complaints, goodwill decisions and the learn stage's findings with your own team.
When is a formal workflow too much?
For a business answering a few messages a day, a formal six-stage workflow is more than needed. One owner, a shared inbox and a weekly look at what customers asked are enough. Formalise it once more than one person or channel is involved.
What does this look like in practice?
A pattern we see: first replies are quick, but resolution is slow because refunds and replacements wait in another team's inbox with no target. Adding a turnaround target and a daily list for those handoffs shortens resolution more than any change to the replies.
Workflow checklist
Check your workflow against these.
- All queries arrive in one place.
- Triage rules and priorities are written.
- Each stage has an owner and target.
- Internal handoffs have targets too.
- Tickets close by a set rule.
- Contact reasons are reviewed weekly.
Next step
Tell us how customer queries reach you and who handles them now. We will map the six stages with you and show where queries wait longest.
Message us on WhatsApp to map your workflow, or book a 30-minute consultation.
Chat on WhatsApp →Sources and further reading
- UK Customer Satisfaction Index · Institute of Customer Service
- Stop trying to delight your customers (Dixon, Freeman and Toman, 2010) · Harvard Business Review
Frequently asked questions
What is a customer service workflow?
A customer service workflow is the set path every customer query follows, from first message to closed. It usually covers receiving, triaging, responding, resolving, closing and learning from each query, with an owner and a target time for each stage.
How do you improve a customer service workflow?
Measure time at each stage for a sample of tickets, find where queries wait longest, and fix that stage first. Often it is internal handoffs with no target. Add owners and targets, give first-line staff authority for common fixes, and review contact reasons weekly.
Which parts of customer service can be outsourced?
Receiving, triaging and responding to queries, and resolving routine issues within agreed limits, are well suited to a managed team. Complaints, goodwill decisions and changes based on what customers are saying are usually best kept with your own team.
Written by

Global Bridge Labs (GBL) is a UK–Sri Lanka partner for social media, websites and BPO. Everything here comes from client delivery, not theory.




