For business4 min read
A Website Enquiry Handled in 60 Seconds: How to Automate Your Contact Form from Click to Reply
Half of website enquiries die in an inbox because the reply comes a day later. Here is the workflow we deploy most often: form → row in a spreadsheet or CRM → message to the team → confirmation to the customer — within a minute and without a human.
The first business to respond to an enquiry usually wins it. B2B sales research has shown the same thing for decades: the odds of reaching someone who left an enquiry are several times higher within 5 minutes than after an hour. Yet the typical contact form works like this: an email lands in info@, which somebody checks in the evening. Below is the workflow that turns that email into action within a minute.
Four steps that happen on their own
- The form saves a record. It does not just send an email — it writes the enquiry into a spreadsheet (Google Sheets, Airtable) or a CRM with the date, source and every field. An email can get lost; a row in a table cannot.
- The team gets a message where it already is. A Telegram group, a Slack channel or an SMS to the person on duty: name, phone, service, message text and a "call" button. The mechanics are in our article on Telegram notifications for existing systems.
- The customer gets a confirmation. An automatic email: "Received, we will reply by 12:00 tomorrow" — with your contact details and, where it fits, a booking link or answers to common questions. The person stops shopping around because they know when to expect an answer.
- Nothing falls through. If the enquiry's status in the table has not changed within a set time, the system reminds the team a second time. An enquiry unanswered after two days is exactly what this workflow prevents.
What happens between the form and the table
Technically, the form sends its data to one address (a webhook). There, a small script or an n8n/Make scenario does three things: checks for spam, writes to the table, sends the messages. All of it takes 1–3 seconds.
The spam filter matters more than it seems. Without it, a week brings 40 "SEO services" offers into the group and the team mutes notifications. What we use:
- Cloudflare Turnstile — a free alternative to reCAPTCHA, without traffic-light puzzles.
- A hidden field (honeypot) — bots fill it in, humans never see it.
- Rate limiting — the same email can submit one enquiry per hour; a second one quietly lands in the same row.
- Content rules — links in the message, typical spam phrases, a mismatch between the form's language and the text.
Together these four reject over 95 % of spam without getting in a real customer's way.
Three tiers by business size
| Tier | What | Tools | Price |
|---|---|---|---|
| Starter | form → table → Telegram + email to the customer | website form, webhook, Google Sheets, Telegram bot | from €150 |
| Working | + CRM (HubSpot, Pipedrive, your own), routing by service or city, reminder after 24 h | n8n or a custom script, CRM API | €300–800 |
| Sales | + automatic first reply by service, calendar link, lead scoring, weekly report | custom code, calendar API, database | €800–2,000 |
Most service businesses need the starter or working tier. The sales tier makes sense above 100 enquiries a month or when several people handle them.
The first-reply rule
The automatic confirmation must promise what you will actually do. "We reply within 24 hours" followed by a reply in 20 builds trust. "We reply within an hour" followed by silence until evening does more damage than no confirmation at all.
Mistakes that break the workflow
- A form with 9 fields. Every extra field lowers completions. Name, contact, what you need — three fields; the rest you will learn in the conversation.
- Enquiries by email only. Email providers sometimes reject, filter or delay. The table or database is the single source of truth; the email is a copy.
- A notification without an action. "New enquiry" without a phone number and a button forces a search. The notification must contain everything needed to call right now.
- Nobody is responsible. Five people see the message in the group, none replies. Assign a person by service or in rotation, and tag them in the notification.
What to do tomorrow
Fill in your own contact form from your phone. See when and where the enquiry arrived, who saw it, and when the customer would get a reply. If the answer is "someone will check info@ at some point", the workflow above pays for itself with the first customer you no longer lose. Forms by service with every step are on the automation page.
Frequently asked questions
Can this be done with a WordPress form?
Yes. Contact Form 7, WPForms, Gravity Forms and most others have webhooks or add-ons that send data to an external address. Your website stays the same; only what happens after "Send" changes.
Where is customer data stored, and is it GDPR-compliant?
In a table or CRM that you choose, hosted in the EU. The privacy policy states the purpose (replying to the enquiry) and the retention period; after it, records are deleted automatically. The Telegram message is only a notification to the team, not a data store.
How long does the setup take?
The starter tier takes 1–2 days, including the spam filter and the customer email. The working tier with a CRM takes a week. The sales tier takes 2–3 weeks with testing.
Updated 11 October 2026