Give every enquiry a next step.
An inbox tells you that someone wrote. It does not reliably tell the team who owns the reply or what should happen next. A small shared record can make that visible without introducing a complicated system.
Use four fields that mean something.
Start with one record per enquiry. Link to the original conversation instead of copying the whole message into several places. Give the enquiry a short description that makes sense to the people handling it.
- Owner
- One person responsible for moving it forward, even when several people help.
- Status
- New, waiting on us, waiting on the customer, agreed, or closed. Define what each means.
- Next action
- A verb and an object: ask for the address, check availability, prepare the quote.
- Due or review date
- When the owner should act or check again. Waiting still needs a review point.
Walk one enquiry through.
Illustrative example: a customer asks for a quote but leaves out the job location. The owner records “waiting on us”, with “ask for location” as the next action. After sending the question, the status becomes “waiting on the customer” with a review date.
When the answer arrives, the owner updates the same record. A quote being prepared is a new next action on this enquiry, not a second enquiry. If someone else takes over, that person explicitly accepts ownership.
Handle a duplicate before replying twice.
If the customer phones after emailing, check for the existing enquiry. Link the second conversation to the same record, keep the latest information and make it clear who will reply. Do not merge two records just because their names look similar.
If you cannot tell whether they are the same request, ask the owner to check. A false merge can lose a distinct job just as easily as duplicate records can create repeated replies.
Make the review small and regular.
Review new items and actions that are due. Ask: does every open enquiry have an owner, and is its next action still correct? Move genuinely finished or declined enquiries out of the open view.
The review needs a person and a useful rhythm for your business. Faster alerts will not repair a queue whose statuses nobody trusts.
Test the process before automating it.
Try it on a few real enquiries using your existing tools. Include a duplicate, a missing detail and a handoff. Check whether the next person can understand the record without asking you to explain it.
If that works, reminders or record creation may be worth automating. If it does not, tighten the ownership and status rules first. Our workflow map helps you set out that boundary.
