The best CRM for website enquiries: what to check before you choose
- Who it is for
- Small businesses whose leads come from their website
- The problem
- Enquiries from a contact form usually end up in someone's mailbox, get answered late or not at all, and never become a pipeline you can see. Most CRMs can store them, but the details that decide whether a lead is answered are easy to miss when you compare tools.
- The solution
- Judge each CRM against a short checklist: does it accept the form you already have, does it stop bots without a captcha, does it keep enquiries apart from cold contacts, does it put the conversation in one place and does it tell you what to answer today. Then set it up in under an hour.
- What you get
- A checklist you can use on any CRM, and a working enquiry setup in Cold Leads: form, tags, stage, optional automatic reply campaign and the Today queue.
Addresses, IDs and results in the examples are illustrative. example.com is reserved for documentation, so a real check of these addresses returns invalid.
The checklist
| Question | Why it matters | How Cold Leads does it |
|---|---|---|
| Can it take my existing form? | Rebuilding forms costs time and breaks your site's design | Any form that can POST: plain HTML, WordPress, Webflow, and form builders through Make or Zapier |
| Does it stop spam without a captcha? | Captchas lose real enquiries | A hidden honeypot field, 30 submissions a minute per IP and 500 a day per website key |
| Does it merge repeat enquiries? | Duplicates split the history | An existing e-mail address is matched; new tags are added to the existing contact |
| Does it keep consent apart? | An enquiry is not permission for cold outreach | Website contacts are saved with consent status inquiry; imported cold lists use B2B outreach |
| Is the conversation in one place? | Answers get lost between mailboxes | Replies from Gmail, Microsoft 365 or IMAP are synced into one chat per contact |
| Does it show what to answer today? | Speed of reply wins deals | The inbox's Today queue lists contacts that need a reply and follow-ups that are due |
| Can it reply automatically? | A quick first answer sets expectations | A website key can add each new contact to an automatic campaign, immediately or after 10 minutes up to 3 days |
Set it up in Cold Leads
- In Settings → API keys, create a website key (lk_…). It is public by design: it can only create contacts.
- Set the key's allowed website to your site's address, so the form can redirect visitors back to your thank-you page.
- Choose the default stage (subscriber or lead), tags such as website or contact-page, and optionally a list.
- Optionally pick an automatic campaign and a delay; each new contact from this key joins that campaign's audience.
- Point your form at the endpoint (example below) and send a test enquiry from your own address.
<form id="enquiry">
<input name="email" type="email" required>
<input name="name">
<textarea name="message"></textarea>
<input name="website" tabindex="-1" autocomplete="off" style="display:none">
<button type="submit">Send</button>
<p id="enquiry-status" role="status"></p>
</form>
<script>
document.getElementById("enquiry").addEventListener("submit", async (e) => {
e.preventDefault();
const status = document.getElementById("enquiry-status");
const res = await fetch("https://coldleads.app/api/hooks/lead", {
method: "POST",
headers: { "x-api-key": "lk_your_website_key" },
body: new FormData(e.target),
});
status.textContent = res.ok ? "Thanks, we will reply soon." : "Something went wrong, please e-mail us.";
if (res.ok) e.target.reset();
});
</script>What happens to an enquiry
- A contact is created with the name, company, phone and message (saved in notes), the source web_form, the key's tags and stage, and consent status inquiry.
- Addresses on the global do-not-contact list are silently ignored, and the form still shows success.
- If the plan's contact limit is reached, new addresses are refused with contact_limit (HTTP 402); existing contacts are still updated.
- If the key has an automatic campaign, the contact joins its audience now or after the chosen delay, and the campaign sends within its daily cap.
- When the person replies, the reply appears in their chat and is classified; the first human reply moves the contact to lead.
Cold Leads does not e-mail you about each new enquiry. Open the inbox's Today queue or the contacts list filtered by your website tag to see new enquiries.
When another CRM is the better choice
- You need deal amounts, forecasting and custom objects: a sales CRM such as HubSpot or Pipedrive fits better.
- You need landing pages, ads and marketing automation around the form: a marketing platform fits better.
- You need instant alerts in Slack or by e-mail for every enquiry: Cold Leads has no outgoing notifications, so add them in your form tool or with Make or Zapier.
FAQ
Do I need a paid plan to capture website enquiries?
Website keys work on every plan, including the trial. The plan's contact limit applies: 25 contacts in the trial, then 200, 1,000 or 10,000.
Is the website key safe to put in my HTML?
Yes. A website key (lk_…) can only create contacts through the lead endpoint. It cannot read data, send e-mail or change anything else.
Will people from my form get my cold campaigns?
They are saved with consent status inquiry, so you can keep them out of cold campaigns. Only add them to a campaign that answers their enquiry, such as an automatic first reply.
Why does the redirect send visitors to the wrong place?
The redirect must be a full address on the website set as the key's allowed website. Otherwise Cold Leads answers with JSON instead of redirecting.