Guide

The form that doesn’t get lost in your inbox: how to capture leads directly into your CRM

In this article
  1. Why Do Leads Disappear From Traditional Contact Forms?
  2. What happens when a form submission goes to a CRM?
  3. How do you create a form in the client portal?
  4. Why add a “reason for contact” field?
  5. Consent and privacy: what the form does, and what it doesn’t
  6. Chatbot or form: which one for which visitor?
  7. How do you add the form to WordPress or another site?
  8. When is a form connected to a CRM more than you need?
  9. Frequently Asked Questions

A visitor fills out your contact form: name, email, a short message about what they need. They click Submit and see "Thank you, we’ll be in touch". Then nothing happens for a long time.

On the other end, the form submission arrives in someone’s email inbox. It sits between a newsletter from a SaaS product nobody uses anymore and a reply-all thread about the office kitchen. The person who owns the inbox is in a meeting. By the time they see it, three hours have passed. They forward it to the sales rep who should handle it. The sales rep is on the phone. The email gets buried. By the end of the day, the lead is cold, or the competitor who answered in twenty minutes has already booked the consultation.

The form works and the email arrives. What is missing is everything around it: a contact form that sends submissions to an inbox has no memory, no priority, no owner and no reminder.

This guide explains how to send form submissions into a CRM instead, which fields to ask for, and how a form and an AI chatbot share the work. The examples use ChatDirect, an AI chatbot and a CRM for small businesses, built in Montréal by Tangram HQ Studio.

Why Do Leads Disappear From Traditional Contact Forms?

The traditional contact form has three fields, name, email, message, and one destination: an inbox. This design made sense in 2006, when businesses received five form submissions a week and the owner personally read every email. It does not make sense in 2026, when the same form competes with dozens of other emails for attention, and the person who should respond may not be the person who owns the inbox.

The problems are predictable. Submissions get buried under unrelated email. Nobody can see at a glance how many leads came in this week. The person asking for a $50,000 project quote looks identical to the person who wants your office hours. Nobody is assigned, and nothing reminds anyone if four hours pass without a reply. The inbox also keeps no record of what happened next.

Some businesses try to fix this with process: check the form inbox every two hours, log the leads in a spreadsheet, add a shared label in Gmail. It holds until the business gets busy, which is exactly when more leads come in.

The fix is a different destination. When a form submission lands in a CRM instead of an inbox, it becomes a contact with a score, a status and an owner, and it no longer depends on someone remembering to check.

Form that emails an inboxForm that feeds a CRM
Where the request landsAmong the other emailsIn a contact record, with each field in its place
PriorityOrder of arrivalA score and a reason for contact
Who handles itWhoever opens the inboxThe person the contact is assigned to
Reminder if nobody answersNoneAn activity with an alert, if you schedule one
What happened nextUnknownNotes, activities and, if you open one, a deal
Monthly count by sourceBy handIn the dashboard and the CSV export
The contact record, with the conversation that brought them in.

What happens when a form submission goes to a CRM?

Seven things happen, in this order. The description follows ChatDirect’s web forms; other tools work in a similar way.

Step 1: The visitor fills out the form. Name, email, phone, and, critically, a “reason for contact” dropdown. We will come back to why that dropdown matters. They check the consent box. They click Submit.

Step 2: The data arrives in the CRM in real time. Not in an inbox. Not in a spreadsheet. In a structured record with every field in the right column. The lead is created immediately, with a timestamp and the source marked as “web form.”

Step 3: The lead is scored automatically. Based on the fields they filled (a phone number is worth more than just an email, a company name and a detailed message add points) and the completeness of the submission. This score appears next to the lead’s name in the pipeline.

Step 4: A notification fires. The business owner or sales rep gets an email, a Slack message, or an in-app alert. The notification includes the lead’s name, email, phone, company, reason for contact and message. No digging through an inbox. No forwarding.

Step 5: The lead lands in the CRM. It appears with the “New” status in your contacts (list or kanban view), ready to be moved to “Contacted” once someone picks up the phone. Schedule an activity with a reminder so nobody forgets to call back; when the request becomes a real opportunity, open a deal in the sales pipeline.

Step 6: The follow-up is tracked. When a team member calls the lead, they log a note. When they send a follow-up email, the activity appears in the lead’s timeline. When the lead converts to a client, the pipeline stage changes. Six months later, you can look at the record and see the entire journey from form submission to closed deal.

Step 7: The data is reportable. At the end of the month, the CRM dashboard and the lead source tell you how many leads came from forms and how many became deals; a CSV export lets you analyze the reasons for contact.

How do you create a form in the client portal?

From the Pro plan, ChatDirect’s form builder is in the client portal, under "Web Forms". There is no separate software to learn: the form and the chatbot share the same CRM and the same notifications. Allow about five minutes for a first form.

Here is the actual process. You open the form builder. You give the form a name, something internal, like “Contact Page Form” or “Quote Request, Services Page.” You choose which fields to include: name, email, phone, company, and a message field are the defaults. You add a “reason for contact” dropdown with your own options (more on this in the next section). You toggle on the consent checkbox and customize the text. You pick a colour scheme that matches your website. You click Save.

The portal generates two things: an embed code and a preview. The embed code is a snippet of HTML you paste into your website wherever you want the form to appear. The preview shows you exactly what it will look like. The form is responsive, it adapts to the width of its container, whether that is a full-page section or a sidebar widget.

Every submission that comes through this form creates a lead in your ChatDirect CRM. The lead is scored, marked with “web form” as its source, and given the “New” status. If you have connected an external CRM like HubSpot or Pipedrive, the lead is sent there too. If you have Slack notifications enabled, your team gets pinged. It is one more entry into the same contact list.

The form builder works in the four languages of the portal, French (Canada), French (France), English, and Spanish: the field labels of the generated code follow the language of your portal, and you write the consent text yourself. For a multilingual clientele, create one form per language.

Why add a “reason for contact” field?

Most contact forms have a free-text “Message” field. People type whatever comes to mind. “Hi, I’m interested in your services.” “How much does it cost?” “Can someone call me?” These messages tell you that someone wants something. They do not tell you what, or how urgently, or which person on your team should handle it.

A “reason for contact” dropdown changes this. You define the options: Request a quote. Book a consultation. Technical support. Partnership inquiry. General question. Press. Careers. Whatever categories make sense for your business. The visitor picks one before submitting.

This does three things a free-text field cannot.

First, it shows intent at a glance. A “request a quote” submission and a “general question” do not call for the same speed. Your team sees which leads are likely buyers before reading a single word of the message. (The automatic score itself rewards complete submissions, not a particular reason.)

Second, it helps routing. If your business has different people handling sales, support, and partnerships, the reason for contact tells you who should take the lead: assign it to the right person in the CRM. Nobody wastes time reading messages that are not for them.

Third, it gives you data. After three months, you can see what share of your form submissions are quote requests, general questions or support. That tells you something about what your website visitors want, and what your website is failing to answer on its own. If many people ask general questions, your FAQ page probably needs work. If many need support, maybe your chatbot should handle those queries before they ever reach the form.

The list takes a minute to set up, as a dropdown or as checkboxes.

A form collects personal information, so privacy law applies to it: Quebec’s Law 25, the federal PIPEDA, or the GDPR for European visitors, depending on where you and your visitors are. This article is not legal advice and does not summarize those texts. For Quebec, the Commission d’accès à l’information publishes the reference material. The practical idea common to all of them is that people should know what you collect and why at the moment you collect it.

A privacy policy page somewhere else on the site does not do that job alone. The person filling out your form should understand, when they click Submit, what will be done with their information.

ChatDirect’s form builder includes an optional consent checkbox with customizable text. You write the consent statement in plain language: “I agree that [Business Name] may use my contact information to respond to my inquiry. See our Privacy Policy.” When you enable it, the checkbox is required, the form cannot be submitted without it, and the lead’s history keeps the date of the submission. Keep a copy of the consent wording you used, with the date you put it online.

The form does not set tracking cookies and does not collect device fingerprints. Besides what the visitor types, it records the page it was sent from and the IP address, stored according to the anonymization level you choose in your privacy settings (full, partial, anonymized or not stored). The less invisible data collection you do, the simpler your obligations become.

Form submissions are stored in Canada, like the rest of ChatDirect’s data. If you have obligations about where personal information is kept or sent, that is one less transfer to document. Check what applies to you in the official texts.

No form makes you compliant by itself. You still need a privacy policy and internal procedures. A form that asks for consent at the point of collection, keeps the date and does not over-collect is a better starting position than one that sends everything to an inbox with no record of what the visitor agreed to.

Chatbot or form: which one for which visitor?

A chatbot does not replace a contact form. They serve different people at different moments, and a website with both leaves fewer visitors without a way to reach you.

Think about the visitors who prefer a form. They are the ones who know exactly what they want. They have a specific request, a quote, a consultation, a support issue, and they want to submit it and get on with their day. They do not want to have a conversation. They do not want to answer qualifying questions one at a time. They want to fill in the fields, hit Submit, and know that a human being will read it and respond. For these visitors, a form is the shortest path.

Now think about the visitors who prefer a chatbot. They are the ones who are not sure what they need yet. They have questions before they are ready to commit to a form submission. “Do you offer this service in my area?” “How long does the process take?” “What is the price range?” A form cannot answer these questions. A chatbot can. And once the chatbot has answered them, it can capture the visitor’s contact information naturally, within the conversation, and create a lead in the same CRM where the form submissions land.

The two channels are complementary. The chatbot handles the explorers. The form handles the deciders. Both feed the same pipeline. Your team does not need to check two systems or merge data from two sources. The lead from the chatbot and the lead from the form sit side by side in the same CRM, with the same scoring, the same labels, and the same follow-up workflow.

There is a third scenario worth mentioning. Some visitors talk to the chatbot first and then fill out the form. They use the chatbot to get their questions answered, and then they submit a formal request through the form because they want a paper trail or because the form asks for information the chatbot did not collect. Each interaction creates its own lead record, so the same person can appear twice. Duplicate detection spots matching emails, phones and names, and lets you keep a single record; your team then sees what the visitor asked the chatbot and what they submitted through the form.

Run both, connected to the same CRM, and each visitor uses the one that suits them.

How do you add the form to WordPress or another site?

If your website runs on WordPress, embedding a ChatDirect form takes one paste: add a Custom HTML block to any page or post and paste the form’s embed code. The form renders inline, styled to match your configuration, and submissions are routed straight to your CRM. There is nothing to install (see the documentation).

If your website does not run on WordPress, Wix, Squarespace, Shopify, Webflow, or a custom-coded site, the process is just as simple. The form builder generates an HTML embed code. You paste it into your page wherever you want the form to appear. It loads as an inline snippet, respects your colour choices, and submits data to your ChatDirect CRM over a secure connection. The only requirement is that your page can include a snippet of HTML, which is true of every website builder on the market.

A few practical notes on where to put it:

  • Landing pages: Embed the form directly on your landing page instead of linking to a separate contact page. Fewer clicks between interest and submission means fewer people lost on the way.
  • Service pages: Put a form at the bottom of each service page. You can create one form per service, with a title and a reason-for-contact list that match it.
  • Blog posts: Embed a form at the end of educational content. A reader who has just finished an article may be ready to ask a question; a form on the page saves them a trip to the contact page.
  • Physical locations: Pair the form with a QR code on printed materials. The QR code opens your website; the form captures the lead.

If you already use ChatDirect’s chatbot, the form and the chatbot coexist on the same page without conflict. The chatbot widget sits in the corner. The form sits inline in the page content. They are two separate interaction points feeding the same CRM. Some visitors will use both. Most will use whichever one matches their intent at that moment.

For businesses already using external CRMs, every form submission can also be sent to HubSpot (as a contact) or Pipedrive (as a person with a note) through the CRM integrations (Pro plan and above). The form captures the lead in ChatDirect; the integration sends it where it needs to go. The configuration takes a few minutes and does not require a developer.

When is a form connected to a CRM more than you need?

If your site brings in two or three requests a month and one person reads them the same day, an email is enough. The CRM becomes useful when several people share the requests, when quotes take weeks to close, or when you want to know which pages and which reasons bring in business.

In those cases, the change is small: you keep your contact page, you change where the submissions go, and you add a list that tells your team what the person wants.

Web forms are part of the Pro plan ($89 CAD per month, before tax) and up; see the pricing page. To go further, read our guide to a CRM built into the chatbot and the one on lead generation with a chatbot.

Frequently Asked Questions

Can I embed a ChatDirect web form on any website, not just WordPress?

Yes. ChatDirect generates a standard HTML embed code for each form you create. You paste it into any website, WordPress, Wix, Squarespace, Shopify, a custom-coded site, or a landing page builder. The form loads as an inline snippet, inherits your chosen colours, and submits lead data directly to your ChatDirect CRM. On WordPress, paste the embed code into a Custom HTML block on any page or post. See the documentation for detailed instructions.

Do leads captured through the form get scored automatically?

Yes. Every lead captured through a ChatDirect web form receives an automatic lead score based on the information provided, name, email, phone, company, reason for contact, a detailed message. That score appears immediately in your CRM. The score rewards complete submissions; the reason for contact itself is shown on the record so your team can prioritize quote requests.

Does the form help me meet Quebec’s Law 25 and GDPR?

It helps, but no form makes you compliant on its own. ChatDirect’s form builder includes an optional consent checkbox with customizable text, so you can state what data you collect and why; once enabled, the form cannot be sent without it. The form does not set tracking cookies, records the page and the IP address according to your anonymization settings, and submissions are stored in Canada. You still need a privacy policy on your site and your own processes.

What happens if someone fills out the form AND talks to the chatbot?

Both interactions feed into the same CRM, as two lead records. Duplicate detection spots that the form submission and the chatbot conversation come from the same person and lets you keep a single record; move the notes you need first, since the other record’s notes are not copied.

Are web forms included in every ChatDirect plan?

No. Web forms are available from the Pro plan ($89 CAD per month, before tax). On every plan, the chatbot’s own lead capture form records contacts in the CRM.

Does a form submission create a deal in the pipeline?

No. It creates a contact with the “New” status, a score and the source “web form”. You open a deal when the request is worth pursuing, and you schedule the follow-up yourself; no follow-up email is sent automatically.

Build a form that feeds your CRM

Web forms are included from the Pro plan. Every submission is scored and recorded in the CRM, next to your AI chatbot’s leads.

See the AI agent