Website enquiry automation
The form is not the finish line.
Most websites end at the moment somebody fills in the contact form. Everything that decides whether that enquiry becomes a customer happens afterwards, by hand, when you get round to it.
Website enquiry automation is the chain that runs after a form is submitted: an instant acknowledgement to the sender, a qualifying question or two, routing to whoever should actually deal with it, a record created in your CRM or spreadsheet without anyone retyping it, and a follow-up that goes out on a schedule if nobody replies. Werehouse Media builds that chain as part of a website project or onto a site somebody else built. It runs on your own accounts and tools, and it keeps working if you stop working with me. The reason it matters is timing rather than tidiness: an enquiry answered in minutes is worth considerably more than the same enquiry answered tomorrow afternoon, because most people who fill in one form fill in three.
The chain
What happens between the form and the sale.
Six steps. Most businesses do all six by hand, and drop two of them on a busy week.
- Acknowledgement. The sender gets a real reply within seconds saying what happens next and when. Not a grey "thank you for your submission" bar that vanishes on refresh.
- Qualification. One or two questions that separate the job you want from the one you do not, asked automatically so you are not spending a phone call finding out.
- Routing. The enquiry goes to the person who handles that kind of work, by service, by area, or by value, rather than into one inbox everybody assumes somebody else is watching.
- The record. A row in your CRM, your spreadsheet or your job system, created from the form rather than retyped from it. Retyping is where details get lost and where the same customer ends up in the system twice.
- Follow-up. If nobody has replied within the window you set, a chase goes out. It stops the moment a human replies or the job is marked won or lost.
- The count. How many enquiries arrived, where from, and what happened to them. Assembled and sent to you rather than reconstructed from memory at the end of the quarter.
If you only do one of the six, do the acknowledgement. It is the cheapest to build, it works the same whether you get four enquiries a month or four hundred, and it is the only one the customer actually sees.
Scope
What this connects to.
The chain is built on whatever you already run rather than on a platform you have to move to. In practice that usually means a website form, an email or SMS sender, a CRM or spreadsheet, and a calendar. Where a tool has a documented API the connection is direct. Where it does not, the honest answer is that the automation stops at the last system that will talk, and the remaining step stays manual rather than being faked.
WhatsApp is a common request and worth being precise about: business messaging through WhatsApp runs on the WhatsApp Business Platform, needs an approved sender and template messages for anything you initiate, and has its own per-conversation costs. It is entirely doable and it is not the same job as sending an email, so it is scoped and priced as its own piece of work.
Everything is built under your logins, on your accounts, so the running costs are yours, visible, and cancellable. Typical platform subscriptions for a small business running two or three automations are modest by comparison with the admin time they replace, but they are a real ongoing cost and you should hear the number before you agree to anything, not after.
Honest limits
When this is not worth building.
When the volume is too low. If four enquiries arrive a month, you can answer all four yourself faster than the automation pays for itself. Build the acknowledgement, skip the rest, and revisit it when volume changes.
When the enquiry is the sale. Some businesses win work on the first call precisely because a person picks up. Putting a qualifying step in front of that costs more than it saves.
When the answer has to be judged. Complaints, unusual specifications, anything a regulator expects a named human to sign. Those get routed quickly and answered personally, never composed automatically.
Where one of these applies I will say so on the call rather than quote for it. Turning a fast, personal process into a slower automated one is a real way to lose money, and it happens often enough to be worth naming.
Pricing
Why there is no headline number.
The same brief costs different amounts in different businesses, and the variable is not the automation. It is where your data currently lives. A firm keeping every enquiry in one system is a short job. A firm holding them across an inbox, a spreadsheet and a notebook needs that untangled before a single step can be automated, and that is the more common case.
So it is quoted in writing after a short call, fixed before work starts, and scoped against what you actually run. Built alongside a website project it is usually the cheaper route, because the form, the data and the destinations are being designed at the same time rather than reverse-engineered afterwards. Added to an existing site it is a standalone piece of work and priced as one.
Common questions
Questions people ask.
How fast should a website enquiry be answered?
As close to immediately as you can manage, because most people enquiring with you are enquiring with two or three others in the same sitting. An automatic acknowledgement does not close the sale, but it holds your place while you get to the real reply, and it stops the enquirer assuming the form failed.
Do I need a CRM before any of this is worth doing?
No. A well-structured spreadsheet is a perfectly reasonable destination for a business doing modest volume, and it is a cheaper place to discover what you actually need to record. A CRM earns its cost once several people need the same view of the same pipeline.
Will automated follow-ups annoy people?
They do when they are obviously automated, arrive too often, and keep arriving after somebody has replied. Those are all build decisions. A single, well-timed, plainly-written chase that stops the moment a human responds reads as organised rather than pushy.
Does this work on a website you did not build?
Usually, yes. It needs a form that can send its data somewhere, which most platforms allow. Where a site is built so it cannot, that limitation gets named up front rather than discovered halfway through.
What happens if an automation breaks?
It alerts you, and the enquiry still reaches a human inbox. Nothing in the chain is allowed to be the only path an enquiry can take, because a silent failure that loses work is far worse than no automation at all.
Where do your enquiries go now?
Tell me what happens after somebody fills in your form, and I will tell you which steps are worth automating and which are not.