How to follow up on website leads before they go cold
Most lost enquiries aren't turned down, they're answered too late or not at all. Following up well needs four things: an alert you will actually see, a first reply you can send in two minutes, one place where every lead is written down, and a weekly check that the log and the website agree.
Why the first hour matters
Someone who fills in a contact form may well have filled in two or three. The business that replies first, with something specific, is well placed to get the conversation. That doesn't mean answering at midnight. It means having a stated reply time ("we reply within one working day"), meeting it every time, and replying faster when you can. Speed to lead for a small business is mostly a matter of the alert reaching the right person and the reply being half-written already.
Step 1: make the alert impossible to miss
Anticode saves every contact, booking and newsletter submission in the project and, unless you switch it off, emails it to your account address. Email alone is easy to bury, so add a second route through Connectors:
- Slack, Discord or Telegram for a message in the channel or chat your team already watches, usually within a minute of the form being sent.
- HubSpot if you work in a CRM: anyone who sends a form with an email address becomes a contact, without duplicates.
- Google Sheets, Airtable or Notion for a running log (step 3).
- A webhook to Zapier, Make or n8n if you want something else, such as a text message to the person on call.
Connectors belong to your account or Team workspace, not to one site, so each one receives submissions from every site in it, tagged with the site's name. If you run several sites for different parts of the business, the tag tells you which one the lead came from; route by site with a webhook if they need different people.
Step 2: write the first reply before you need it
Write one template per kind of enquiry in your email tool or phone. A good first reply does three things: shows you read the message, answers the obvious question or asks the one you need answered, and proposes a next step with a time.
Anticode doesn't send replies to your visitors, so this message goes from your own inbox. Phone if the visitor left a number and the job is worth it; follow the call with an email that confirms what you agreed.
Step 3: keep one lead log
A spreadsheet is enough. With the Google Sheets connector each submission arrives as a row with the time, the site, the form and every field. Add your own columns beside them: who replied, when, the outcome (booked, quoted, lost, spam) and a value if you win it. Keep it to those columns; a log nobody updates is worse than none.
Step 4: the weekly missed-lead check
- Open the project's submissions and count this week's entries.
- Count this week's rows in your log. The numbers should match.
- For any gap, find the submission and reply now, with an apology if it's late.
- Scan the outcome column for leads with no outcome after a week and send a short second message.
- Glance at the site's views by source in the dashboard: if views held steady but enquiries dropped, look at the form page, not your marketing.
What goes wrong
| Symptom | Likely cause | Fix |
|---|---|---|
| A lead is in submissions but not in Slack or the sheet | Connectors send each submission once, without retries, so a webhook that was down missed it | The weekly check catches it; the email copy and saved submission are still there |
| Notification emails land in spam | Your mail filter | Mark one as not spam and add the sender to contacts |
| Two people reply to the same lead | Nobody owns the channel | Name one owner per day; react to the alert to claim it |
| Replies are fast but leads don't convert | The first reply is generic | Rewrite the template to ask the one qualifying question |
How you know it's working
Every submission in the project has a matching row with a reply time inside your stated window. The weekly check takes ten minutes and finds nothing most weeks. And when a customer says "I sent a message on your site", you can find it.
Where Anticode stops
Anticode collects the form, stores the submission sealed at rest, emails you and passes it to your connectors. It doesn't reply to leads, send reminders, score leads or track whether a deal closed; your inbox and log or CRM do that. For deciding which enquiries deserve a fast call, see qualifying website leads; for sending different enquiries to different people, routing contact form enquiries.
Questions people ask
How fast should I reply to a website enquiry?
Within the time you promise on the site, every time. Same working day is a reasonable promise for most small businesses.
Can Anticode send an automatic reply to the person who filled in the form?
No. Submissions reach you and your connectors; the reply comes from your own email. A webhook into an automation tool can send one if you need it.
What's the simplest way to follow up on website leads without a CRM?
Email alerts plus a Slack or Telegram message, a reply template, and a Google Sheets log you check once a week against the project's submissions.