Automating Lead Capture and Follow-Up
From form submission to follow-up, with the failure modes that quietly lose enquiries designed out.
This is an implementation example, not a client case study. It describes how this work is actually carried out — the method, the sequence and the reasoning. No client is named and no result is claimed, because inventing either would make it worthless as evidence.
The most expensive lead problem is not conversion rate. It is enquiries that arrive and are never seen — sitting in a spam folder, in an inbox nobody checks, or lost because a form silently stopped delivering months ago.
- Project type
- Lead capture and follow-up automation
- Sector
- Professional services
The challenge
Enquiries arrive through several routes, get handled inconsistently depending on who sees them, and follow-up depends on someone remembering. Meanwhile the delivery path has no monitoring, so a failure produces silence rather than an alert.
The objective
Every enquiry captured durably, visible immediately, qualified consistently, and followed up on a schedule rather than from memory.
Approach
Store first, notify second. The most important design decision is that the enquiry is saved to a durable store before any notification is attempted, so a mail failure loses the alert but never the lead.
Implementation
1. Capture, durably, first
The form writes to a database before attempting to send anything. If email delivery then fails, the enquiry still exists.
This ordering is the single most valuable line in the whole flow. Systems that email first and store second lose leads permanently whenever mail breaks.
2. Ask the qualifying questions up front
Service, budget range, timeline, how they found you. Four fields, chosen because each changes how the enquiry is handled.
Every additional field costs submissions, so each one has to earn its place. "How did you find us" earns it by telling you which channels work.
3. Validate properly
Server-side validation, a honeypot field for bots, and rate limiting per IP. A honeypot plus rate limiting stops most automated submissions without making real people solve puzzles — CAPTCHAs cost genuine conversions.
4. Notify, and make failure loud
Notification goes out immediately. Critically, failures are logged loudly rather than swallowed.
A .catch(() => {}) around a mail send is how a business goes months without realising its contact form stopped delivering. Every failure path here writes a warning naming what failed and where to find the enquiry instead.
5. Acknowledge immediately
An automatic acknowledgement that sets a realistic expectation — "you will get a written response within one working day" — and is honest about it.
6. Follow up on a schedule
A reminder if an enquiry has gone unanswered, and a prompt if a proposal has had no response after a set period. Reminders to a human, not automated chasing of the customer.
7. Surface failures where someone looks
Not in a log file nobody opens. In the place the team already works.
Technology
- Zod validation
- Rate limiting
- Transactional email
- CRM integration
- Webhooks
Decisions worth explaining
Store the enquiry before attempting to notify
Decouples the lead from the mail path. A delivery failure then costs an alert, not a customer.
Honeypot and rate limiting instead of CAPTCHA
Stops most automated submissions with no friction for real users. CAPTCHAs measurably reduce genuine conversions.
Every failure path logs loudly
Silent failure is the specific way businesses lose months of enquiries without noticing. This site logs an explicit warning when its mail key is absent, for exactly that reason.
What it produces
An enquiry path where leads are stored durably before anything else can fail, qualified consistently, surfaced immediately, and followed up on a schedule — with every failure mode visible. No conversion figures are claimed.
What it teaches
- Store before you notify. Everything else is secondary to that ordering.
- A swallowed error on a mail send is the most expensive line of code on a business website.
- Every form field costs submissions, so each must earn its place.
- Automated reminders should target your team, not your prospect.
Related services
Related guides
AI & Automation
How AI Can Automate Lead Follow-Up
Following up reliably without sounding like a sequence. The line between helpful and irritating is narrower than most tools assume.
AI & Automation
AI Automation for Customer Enquiries
Faster handling without making people feel processed. Where the automation should stop.
Conversion & Growth
Why Website Visitors Are Not Turning Into Leads
Work through these in order. The first one is more common than anyone expects, and it is entirely invisible.
