Solution

Follow up every enquiry without remembering to

You reply once. They go quiet. Nobody chases, because chasing is the job that never makes it to the top of the list.

This page covers how we make follow-up happen on its own, without it feeling like spam.

Where the work disappears

An enquiry that gets one reply and no follow-up converts far worse than one that gets three. Customers are busy, not uninterested — they meant to reply and forgot.

Without a system, follow-up depends on whoever is least busy noticing. In a small business that is nobody.

How follow-up runs

  1. 01

    Every enquiry gets a timestamp and an owner the moment it arrives.

  2. 02

    If there is no reply after an agreed gap, a short follow-up goes out referencing what they asked about.

  3. 03

    After a set number of attempts the enquiry is closed with a reason, so your list stays honest.

What is automated, and what stays with you

Handled automatically

  • Timing and sending the follow-ups
  • Tracking who has replied
  • Closing dead enquiries with a reason

Stays under your control

  • The quote and the conversation
  • Anything requiring judgement about the job
  • Deciding tone and how hard to chase

What changes

You stop discovering enquiries a week late. Conversion improves because more people get a second and third prompt. And you can see, for the first time, how many enquiries you actually get versus how many you win.

Start with a free strategy call

We start by measuring how many enquiries you get, how fast they are answered, and where they stall.

Book a free strategy call

Questions we get asked

How many follow-ups is too many?
Two or three, spaced sensibly, is usually right for service work. We agree the limit with you rather than guessing.
Can it use my own wording?
Yes. Every message is drafted with you and signed off before it goes anywhere near a customer.
What happens if the automation gets something wrong?
It stops and hands the job to you. Anything the system is not certain about is flagged rather than guessed at, and you see it the same day.
How long does implementation normally take?
Two to four weeks for a first build in most cases, starting with the one workflow that costs you the most time.