If enquiries arrive in several places, the first improvement may be a clearer routine—not a bigger CRM. Work through these checks with the person who receives messages and the person who follows them up.
A small enquiry register, clear ownership, a follow-up boundary and one end-to-end test you can repeat.
Choose one place to record enquiries
An inbox holds messages; a working register shows what should happen next. Start with a small shared record that the people responsible can actually maintain.
- List your inbound channels: website, business email, phone, WhatsApp and referrals. Assign someone to check each one.
- Use one row per genuine enquiry, with received date, contact method, request summary, stage, owner, next action and due date. Store only what the team needs.
- Agree how to recognise a duplicate. Link repeat messages to the existing enquiry instead of treating each message as a new opportunity.
Give each enquiry a named owner
“The team will reply” is not an assignment. A named owner makes the handover visible even when the original recipient is away.
- Assign one person to take the next action. Name a backup for leave, sickness or a full inbox.
- Define how ownership is handed over: the new owner acknowledges it and the register is updated.
- Restrict access to people who need it. Keep passwords and unnecessary customer records out of the register.
Separate receipt from a useful response
An automatic receipt can confirm that a message was saved. It cannot promise that someone has reviewed the request or that the business can deliver it.
- Write a short acknowledgement that describes only what is confirmed. Do not promise a quote or availability before checking.
- Agree a response target that matches your staffed hours. Make an owner responsible for checking overdue enquiries.
- For the first human response, acknowledge the specific problem and ask only for the missing details needed to recommend the next step.
Record a next action, not just a status
“Open” does not say what anyone should do. Pair each active stage with a concrete action and a date that the owner can review.
- Use clear stages such as New, Contacted, Consultation arranged, Proposal sent, Won, Lost or Closed—not interested. Define what each means.
- Write next actions as a verb and an outcome: “Confirm consultation time” or “Ask which booking tool is used”.
- Before closing the register, check that every active enquiry has an owner, a next action and a review date.
Make follow-up relevant and easy to stop
Follow-up should help resolve the person’s original enquiry. A repeated sales sequence is not a substitute for paying attention to the conversation.
- Base the next message on the last exchange: answer an open question, offer a useful next step or ask whether the request is still active.
- Set a small, defined follow-up limit appropriate to the enquiry. Stop when someone declines, requests no further contact or the request is no longer relevant.
- Record a stop-contact instruction where everyone handling that enquiry can see it. Do not turn enquiry details into a newsletter list by default.
Test the handover with labelled test enquiries
A test should exercise the whole route, not just prove that a form submits. Use your own contact details and clearly mark the record as a test.
- Send one test from each channel you actually use. Confirm it reaches the right person and appears in the working register once.
- Ask the backup owner to handle a test handover. Check that they can see the context without needing someone’s personal password.
- Test a duplicate and a notification failure. Confirm the underlying enquiry can still be found, and exclude all test records from sales totals.
Review missed actions before buying another tool
A brief register review shows whether the problem is missing information, unclear responsibility or a task that genuinely needs automation.
- Review unassigned and overdue enquiries at a cadence your team can sustain. Give unresolved items a specific owner and action.
- Count genuine enquiries, completed consultations, proposals and outcomes separately. Do not treat a website click as a received enquiry or a sale.
- Write down one recurring failure and its cause. Fix that failure, then repeat the test before broadening the workflow.
A useful boundary
When not to automate yet
- There is no agreed owner or response routine. Define those before adding automatic messages.
- The process relies on broad unsolicited outreach, ignores stop-contact requests or uses contact information for a new purpose without checking what is appropriate.
- Enquiry volumes are small enough for a reliable manual process and the proposed tool adds more upkeep than it removes.
Educational guidance for planning a business workflow, not a comprehensive security assessment or legal advice. Check the requirements of your tools and business before changing a live process. Examples describe suggested checks, not promised results.