Customers
Desks that stopped guessing who owed whom an answer
Four operations, four different problems, the same five zones on screen. Here is what each of them changed and what it moved.
4
sectors, one desk
Freight, marine service, software and professional practice.
11
departments at the largest
Routed by parser rule before anybody opens the message.
0
threads split by a reply
Threading survives Gmail, Exchange and every sender that rewrites headers.
74%
chats closed live
The rest convert to a linked ticket with the transcript attached.
Composite accounts written for this site. The mechanics behind each figure — working-hours clocks, parser routing, chat-to-ticket conversion — are the ones the product ships.
Stories
Four teams, in their own words
Each one names the mechanism that did the work, so the claim can be checked against the product rather than against the number.
Veldwerk Logistics
Freight and warehousing · 340 staff · 22 on the desk
The problem
Three depots each ran their own mailbox. A shipment query could sit unanswered for a day because everyone assumed another depot had it, and nobody could say what had already been promised to the customer.
What they run now
One queue per depot inside a single desk, with mail parser rules filing by route code on arrival and a working-hours SLA plan per contract tier. Escalations now fire on genuinely overdue work rather than on weekends.
Shared inbox
SLA plans
Mail parser
Reporting
“The thing that changed was the working-hours clock. A Friday ticket is no longer three days late by Monday, so when an escalation lands it means something and people act on it.”
MD
Marieke Doornbos
Head of Customer Operations, Veldwerk Logistics
−41%
first-reply time
3.1%
SLA breach rate
1 900
tickets a month
Nordkap Marine
Marine equipment service · 110 staff · 9 on the desk
The problem
Engineers answered the same eight questions about part compatibility every week, and customers mailed again the next day to ask where their ticket stood.
What they run now
A knowledgebase built from the answers the team was already typing, exposed through the self-service portal alongside each customer's own ticket history. Article ratings showed which pages were doing the work.
Knowledgebase
Self-service portal
Downloads
Troubleshooter
“We underestimated the portal. Customers stopped mailing to ask for status because they could simply look, and the article we pointed them at answered the follow-up before they asked it.”
JH
Jasper Holt
Service Delivery Manager, Nordkap Marine
−28%
inbound volume
164
published articles
91%
found articles helpful
Brightline Software
B2B SaaS · 65 staff · 6 on the desk
The problem
The chat widget lived outside the helpdesk. Anything that needed follow-up was copied into an email by hand, and roughly one in ten never made it across.
What they run now
Chats queue by department inside the same desk. What can be answered live is answered live; what cannot becomes a linked ticket carrying the full transcript, so the thread survives the handover.
Live chat
Shared inbox
Canned responses
Visitors
“Copy-pasting transcripts into a mailbox was where our work leaked. Converting a chat into a ticket in one action removed a whole category of dropped promise.”
PR
Priya Raghavan
Support Lead, Brightline Software
74%
chats resolved live
1 click
chat to ticket
4.7
average chat rating
Kessler & Co
Accountancy and payroll · 210 staff · 14 on the desk
The problem
Payroll, tax and onboarding queries all arrived at one address, and a practice this size cannot let a client file sit in a queue nobody owns while somebody works out whose it is.
What they run now
Eleven departments with custom roles and per-module permissions, and parser rules that read the subject and the sending address and file the message before anybody opens it.
Roles & permissions
Mail parser
Departments
Shared inbox
“We chose it for the routing. Nobody triages a mailbox here any more — a payroll question is in front of the payroll team before we have read it.”
AW
Anke Wielinga
Practice Operations Director, Kessler & Co
11
departments routed
6
permission groups
0
messages sorted by hand
Start today
Put the whole queue on one screen
Fourteen days with your own mail, your own departments and your own SLA clocks running. Nothing to install.
No card required · Set up in an afternoon
Connect your own mailbox
Keep your existing mail addresses
No ticket numbers in your subject lines