The Problem
Queries that live in email have no owner, no status and no end date. A client asks about an invoice on Monday, two people read it, each assumes the other replied, and the client chases on Thursday. Nobody can say how many queries are open right now or how long the average one takes to close.
The occasional missed query hurts. The larger loss is that patterns never show up: if the same billing question arrives forty times a quarter, the inbox treats it as forty separate conversations and the process causing it never gets fixed.
What a Query Management System Does
It gives every query a lifecycle. A query comes in through a web form or a monitored mailbox, gets a category and an owner, moves through statuses the whole team can see, and closes with the resolution written down. Our explainer on query management systems covers the concept itself; this page is about what we build.
A typical build includes:
- Structured intake, so a query arrives with a category, a priority and the reference it relates to (an invoice number or a matter reference)
- A named owner on every query, with the team inbox used only as a holding area
- Statuses visible to the team and, where it helps, to the person who raised it: open, in progress, waiting on the client, resolved
- A permanent, searchable history of every query and reply
- Categories that show which issues keep coming back
- Response and resolution targets, with an alert before one is missed
Once queries are tracked this way they become data. You can see volume by week, which categories dominate, how long each type takes and where they stall.
Query Management Software or a Custom Build
Search for query management software and you will find two kinds of product. There are general help desks such as Zendesk or Freshdesk, and there are niche tools built for one job, usually invoice queries in an accounts receivable team. Both deserve a look before you pay for anything custom.
A help desk suits queries that look like standard support tickets, handled by a team that works in one place. A custom system earns its cost in three situations we come across repeatedly:
- The query is tied to a record in another system. An invoice query needs the invoice, the customer’s payment history from Xero or Sage, and the account manager’s name beside it. Copying those across by hand is the job you were trying to get rid of.
- Your clients raise queries inside a portal they already use, and a separate help desk login would send them back to email.
- You have to prove response times to a regulator or under a client contract, and the evidence has to come from your own records.
If none of those apply, a help desk will serve you well and cost less than a build.
Queries, Enquiries and Requests
These words get used loosely, and the systems behind them differ. A query is a question or issue from someone you already work with, such as a client or a supplier. An enquiry, in the sense most UK businesses use the word, is a prospect asking about your services, and it belongs in a sales pipeline with follow-ups and conversion tracking. A request asks for work to be done, like a change or a new feature, and the request management system handles that with approval steps a query never needs.
Plenty of businesses need two of these. We often build them on one platform with separate workflows, because a single shared queue is where off-the-shelf setups tend to go wrong: sales enquiries get handled like support tickets and nobody follows them up.
How We Build This
We build on Laravel with a React front end, and most of the design work happens before any code is written. What categories of query do you receive, who handles each one, and what counts as resolved? A small team might start with three categories and one queue. A finance team handling customer and supplier queries might need twenty, routed by rules on the account or the value involved.
Integration is usually where the value sits:
- Email in and out, so a query can be raised by email and every reply is logged against it
- Your accounting or practice management system, so the record a query is about appears next to it
- Notifications when a query is assigned or close to breaching its target
- Reporting that feeds your wider operational dashboards
- A client portal, if your clients raise queries themselves
For one client-facing team handling several hundred queries a week, we built the system into their existing portal, and dropped queries went to zero. The query management platform case study explains how.
What You Get
- One view of every open query, who owns it and which ones are overdue
- Categories and routing rules that match how your team works, and that you can edit as it changes
- Reports on volume, resolution time, recurring query types and target compliance
- Search across every query by keyword, date, client, category or status
- Separate views for the people raising queries, handling them and managing the team
- Connections to the tools you already use, so the context arrives with the query
Who This Is For
Teams with a steady flow of queries from clients or suppliers who have outgrown a shared inbox. In practice that means finance and accounts teams, professional services firms fielding client questions on live matters, and operations teams dealing with supplier issues. The tipping point is usually when one person can no longer hold the whole queue in their head.
If you get a handful of queries a week, a well-run shared inbox is enough, and a system would cost more than it saves.
Why This Matters
Tracked queries show you where your own processes confuse people. If a third of client queries are about the same line on an invoice, the fix is the invoice layout, and email would never have told you that. Over a year, those fixes reduce the number of queries you have to handle at all.
Talk to Us About Query Management
If queries are slipping through your inbox, or a help desk has your team working around it, get in touch and we will say whether a custom query management system makes sense for you or an off-the-shelf tool will do. The systems overview shows what else we build, and our custom software development page explains how a build runs.
