Imagine a furniture workshop on a busy Monday. One buyer asks for a delivery quote by email. Another calls about a repair. A third sends the room measurements after yesterday's conversation. Everyone remembers replying. Nobody can say which person is still waiting.
Customer enquiry tracking means recording each request, who owns it, what happens next and when to check it again. Start with one shared list your team can keep current. A longer contact database will not help if the next action is blank.
The idea, at a glance
One enquiry. A visible next step.
- 01Capture
Keep the question and its source together.
- 02Own
Name the person responsible for progress.
- 03Schedule
Write the next action and check time.
- 04Finish
Record the outcome and any return route.
Record the work, not just the contact
A customer record tells you who someone is. An enquiry record tells you what they need now. One person can have two different requests, so give each request its own reference and link it to the right conversation.
Keep the first version small
Use the fields below. The example is invented; replace its dates, people and promises with your own. Link the original message in a place your team is allowed to access, rather than copying private attachments into an open sheet.
| Field | Worked example | Why it helps |
|---|---|---|
| Reference | ENQ-041 | Finds the same request again |
| Request | Delivery quote for two chairs | Names the job |
| Owner | Meera | Makes responsibility clear |
| State | Waiting on workshop | Explains the pause |
| Next action | Confirm packing dimensions | Says what to do |
| Due check | Tuesday, 11:00 IST | Makes the pause reviewable |
| Last update | Buyer told we will confirm Tuesday | Preserves the promise |
Give states plain meanings
Start with New, In progress, Waiting on customer, Waiting on team and Done. Write a one-line meaning for each. Waiting is a dependency, not permission to forget the request. Every waiting item still needs someone to check it.
Make ownership visible before anyone replies
Google's Collaborative Inbox documentation distinguishes assigned, unassigned and resolved conversations. That is a useful separation even when your first tracker is a sheet.
Agree that the person who takes an enquiry updates its owner before answering. If someone else needs to help, ask for that specific help without quietly abandoning ownership. Use the shared-inbox routine when several people work from one address.
Give every pause a return date
“Waiting for the supplier” describes yesterday. “Call the supplier on Tuesday at 11” describes the next move. If the supplier has not answered, the owner still owes the buyer an update at the time already promised.
Use the follow-up planner to separate internal checks from customer messages. An internal reminder may be needed even when another message to the customer would add nothing.
Close the request with a reason
Record what finished the work: quote sent, question answered, buyer declined or duplicate linked to another request. Do not mark a job complete only because nobody replied for a while. Note the last message and how the person can return if they still need help.
Zendesk's metric definitions treat unanswered and unresolved requests as different things. A reply can exist while the work remains unfinished. Keep both visible in your own review.
Test the list on one working day
At the start of the day, inspect unassigned requests and checks that are due. At the end, take five open items and ask a colleague to explain the next action without asking their original owner. If they cannot, improve the note before adding more columns.
This process can work with tools you already use. The Kyloth Desk overview shows the product direction and its current access boundaries; this guide does not depend on a particular connection or automation being available.
A conversation worth having
Reader comments
What has worked in your business? Share a useful example or ask a question. Comments are reviewed before publication.
Loading comments…