How to follow up on unanswered service enquiries

Start with the request, then check what changed.

A customer asks your plumbing business about a dripping tap. You reply asking which day suits them, then hear nothing. Before sending another message, find out whether a teammate took their call, a visit was booked or the customer no longer needs the work.

This guide is for an existing customer enquiry: someone has already asked your business for help. It does not cover sending sales messages to a list of people who have never contacted you. Keep any follow-up relevant to the original request and use the contact preferences the customer has given you.

Your manual follow-up checklist

You can use this in a shared inbox, notebook or existing job system. Start with one unanswered enquiry and work through these five checks.

1. 01

   Name one person responsible.

   Choose the office coordinator, owner or teammate who will check the enquiry and handle the response. Keep that name beside the next action so two people do not chase the same customer.

2. 02

   Read the request and the latest conversation.

   Confirm what the customer asked for, what you last said and when. Check the inbox, call notes and job record for a reply, a booking or a request to stop. A silent email thread does not mean nobody has spoken on the phone.

3. 03

   Decide whether a follow-up is useful now.

   Use any timing agreed with the customer and the urgency of their request. If they asked you to wait until next week, record that date. If the work is already booked, completed or declined, update the record instead of asking again.

4. 04

   Draft one clear next step.

   Refer to their actual request and ask an easy question. Do not promise a price, appointment or availability you have not checked. Let them say that the enquiry can be closed.

5. 05

   Review, recheck and record the outcome.

   Before sending through your usual channel, check the recipient, details and latest replies again. Record what you sent and the next review date. A reply goes back to the owner; an opt-out stops the follow-up. Do not leave a repeating reminder running indefinitely.

A useful record has: the request, its owner, the last contact date, the latest reply or opt-out, and the next action with a review date. If you cannot confirm the current status, ask the owner before preparing another reminder.

A short message you can adapt

Replace the brackets with details you have checked. This is an example for a routine enquiry where the customer has asked for help and has not replied or asked you to stop.

If the customer replies, read what they need and continue that conversation. If they ask you to stop, record it and stop the follow-up. Silence alone is not a reason to send an endless sequence. Agree a stopping point with the person who owns the enquiry.

See the four decisions in the demo

Open the lead follow-up sample and try each named scenario. It uses the fictional business Northstar Studio and fictional contacts. The same decision pattern can help you think through a plumbing or service enquiry.

The demo prepares a draft after at least three days without a reply. Three days is a fixed rule in this sample, not a universal recommendation. A real workflow needs a timing rule agreed for your business, service and customer expectations.

On the due scenario, read the draft, edit it and approve the sample action. Approval records the draft in the demo only; it does not send an email. The other three scenarios stay held with no draft to approve. Sample state stays in browser memory and clears when you reset, switch workflows or reload. Use fictional details throughout.

Write the rules before connecting your tools.

Once the manual process is clear, decide where the latest reply and opt-out are recorded, who maintains that record, and what happens if the information is missing. Agree who approves messages and who handles a failed connection. Check any automation features you already have in your inbox or job software.

A live workflow should be tested with due, replied, opted-out and not-yet-due examples before it handles real enquiries. The browser sample helps you discuss those rules; it does not establish that your software is connected or that a particular integration is available.