Make the hidden queue visible
An inbox is good at receiving messages and less good at explaining what the business owes each sender. Take a small set of recent enquiries and classify what each one needs: an answer, a question, a quote, a booking or a clear decline. Do this in your existing system before choosing another tool. The exercise should reveal where requests become stuck, especially when a conversation has been read but no next action was recorded.
Distinguish waiting from forgotten
A customer awaiting your response and a request awaiting customer information should not look identical. Give each an owner and a short note explaining the next step. For a team, decide how ownership transfers when somebody is away. For a solo business, reserve a review point for unanswered requests rather than trusting memory. Keep unnecessary personal details out of labels, shared spreadsheets and subject lines; the status should describe the work rather than expose the person.
Test an awkward example
Imagine an enquiry arrives twice, through email and a contact form. Then imagine the customer changes the requested date. Work through how you would join the conversations and preserve the current request without losing the earlier promise. Use that rehearsal to refine the process. At the end of a review, sample a few open enquiries and ask whether another person could identify the next action. If they cannot, the status names may be decorative rather than operational.
U.S. Small Business Administration: manage your business ↗
This article combines general educational guidance with original planning exercises. It does not claim first-hand field testing or an endorsement from the linked organization. Sources checked October 2026.
