Automations

Set up an approved first reply for the moments when you are busy on a job.

  1. Someone gets in touch

    A form, a text, an email or a missed call.

  2. They get a reply

    A text or email, using wording you approved.

  3. You are told

    A message to your phone with who it is and what they want.

  4. They are booked in

    They pick a free time and it goes in your diary.

  5. A reminder goes out

    Before the appointment, so it is not forgotten.

What it is, in plain words

An automation is a set of small jobs that run by themselves, so the first reply never depends on you having a free hand.

When a customer fills in your form, sends a message, or rings and you cannot pick up, the system answers for you, saves their details and lets you know. It does the part that is easy to forget when you are with a customer.

It can use tools such as n8n, Twilio and Supabase. The agreed account setup, access and data handling are written down before anything goes live.

Example: A reply to a website enquiry

Customer: Hi, can anyone look at a leaking tap this week?

Automatic reply: Thanks for getting in touch. We have your message and will confirm a time shortly. Does Thursday morning or Friday afternoon suit you better?

An example only. The wording is written with you and approved by you before anything goes live.

What we do

Each of these is built, tested and switched on with you.

  • Instant reply to form enquiries

    A text or email goes back the moment someone fills in your form, whichever they chose.

  • Missed-call text-back

    If you cannot answer, the caller gets a text, aiming for about a minute, asking what they need.

  • Booking

    Customers can pick from the free times you have set, with the booking added to the agreed diary.

  • Reminders

    Reminders go out before each appointment, so people are less likely to forget.

  • A message to you for every enquiry

    Every enquiry is saved, and you are told who it is, what they want and how to reply.

  • Your wording, your approval

    We write the replies with you, using your real prices and hours. Nothing is sent to your customers until you have approved it.

What you get

  • A system that answers for you while you are working
  • A saved record of every enquiry and every reply
  • Replies that sound like you, written with your real prices and hours
  • A documented account and access setup, agreed before launch

Who it suits

A good fit if

  • You miss calls because you are on a job or with a customer
  • Enquiries arrive by form, text, email or phone and some wait hours for an answer
  • You take bookings or quotes and want fewer to slip through

Probably not the right time if

  • You get very few enquiries at the moment, so a clearer website may need to come first
  • You want a robot to run the whole conversation with no person involved

What to expect, and how long it takes

Most of the time goes on getting your wording and details right, not on the technology.

  1. 2 to 3 days

    Learn how you work

    Your services, prices, hours and the way you talk to customers.

  2. 1 to 2 weeks

    Build and connect

    Set up on your accounts and connected to your form, phone and diary.

  3. About 1 week

    Test

    We test with our own numbers and yours before any customer is involved.

  4. To agree

    Support after launch

    Ongoing checks and reply changes are included only if they are part of the agreed support plan.

These are typical ranges, not promises. If wording takes longer to approve, the start date moves too.

Questions people ask

Will my customers know it is automatic?
We do not pretend to be a person. The reply says who it is from, gives a quick first answer, and a person follows up. You choose the wording.
What if it says something wrong?
You approve the replies before they go live, and you can pause the system at any time. Prices and facts come from the details you give us, so it does not make them up.
Whose accounts does it run on?
The account owner, editors, payment method and handover route are agreed before the build. The current hosting model is explained in the project plan rather than assumed on this page.

Talk it through with us

Book a call