DEV Community

Cover image for Website Enquiries: Save Them, Acknowledge Them, Then Reply in Person
The Doctor
The Doctor

Posted on Originally published at thedoctorau.wordpress.com

Website Enquiries: Save Them, Acknowledge Them, Then Reply in Person

Where does a website enquiry go after someone presses send? If it lands in an inbox you only check between jobs, that enquiry is relying on your memory to get a reply.

That's the gap this automation closes. It doesn't write your replies for you. It makes sure the enquiry is saved, the person hears back straight away, and you get a nudge to answer them properly.

What the automation does

On my automations page I describe it as "An enquiry that doesn't get lost."

The setup is simple to explain: connect your website form to your CRM or task list, send an acknowledgement, and give yourself a reminder to reply personally.

It runs in three steps:

  • Enquiry arrives. Someone fills in the form on your website.
  • Details saved. Their name, contact details and message land in your CRM or task list, not just in an email thread.
  • Follow-up ready. They get an acknowledgement, and you get a reminder to write back yourself.

That last part matters. The acknowledgement tells the person their message landed. The personal reply still comes from you, because that's the bit a customer actually wants.

What's included when I set it up

This sits under my Systems, CRMs & process service, which covers tools, customer records and automated workflows organised around how your business runs. The site lists what that includes:

  • Connected tools and customer records, with less copying between systems
  • Clear operating procedures, staff onboarding guides, and reusable templates

For an enquiry workflow, that means the form, the place enquiries are stored and the reminder all talk to each other. It also means someone else in the business can follow the same steps without asking you how it works.

What a first paid job could look like

I don't start with a big project. On my how it works page, step two is to choose one bottleneck to fix: enquiries and quotes, customer records, or a process your team can follow.

If enquiries are the bottleneck, that's the job. We agree the scope, timing and price before I build and test the setup. I'd look at the form you already have and where you'd like enquiries to live. I'd also work out what the acknowledgement and the reminder should say.

If you'd rather keep going from there, the same pattern extends to other repeat work. My automations page also covers client onboarding, invoice reminders, content scheduling, team handovers and reporting. The first job can be whichever repeat task costs you the most time.

What the handover leaves behind

When it's running, I'll show you how it works and leave instructions you can use yourself or pass to new staff. Ongoing support is optional. You end up with a working setup, clear instructions and a guided handover, not a system only I understand.

Start with free advice

If enquiries are the thing that keeps landing back on your desk, tell me about it. Email me at calebmartin@belac.au or send an enquiry through belac.au. A sentence or two is enough. I'll reply by email with a suggested starting point, and you can use the advice yourself.

Top comments (0)