Chatbot Lead Qualification for CRM: What Actually Arrives
Chatbot lead qualification for CRM works best when the chat gathers the evidence and the CRM makes the call. With Total Chat, on the Pro plan and up, each lead is posted to your CRM once the visitor has shared an email in the chat. HubSpot, Salesforce and GoHighLevel get their own field formats; anything else connects through Zapier, Make or your own endpoint. The lead carries the email, the UTM source, medium and campaign, the outside referrer, the landing page and the visitor’s first chat message. Your qualification rules then run in the CRM, on those fields.
Last updated: November 2026
Everyone knows the flow. Few check what actually lands.
The well-known version: a bot asks a few questions, decides who’s qualified, and pushes the good ones into the CRM. Sales picks them up. Done.
The part that’s little understood is simpler and more annoying. Your CRM can only qualify a lead on fields that arrive filled in, and plenty of what a visitor says in a chat never becomes a field at all. If you’ve suspected your chat leads look thin once they reach the CRM, that’s usually why. If an earlier rollout fizzled for this reason, it wasn’t your sales team’s fault.
So here’s our view: the most important decision in a chat-to-CRM setup isn’t the bot’s script. It’s which CRM properties you build your routing rules on, and whether those properties will ever have a value in them.
What reaches your CRM from Total Chat
Total Chat’s docs publish the universal lead format it sends to Zapier, Make or your own endpoint. Missing fields arrive as null. Here’s how it splits.
| Arrives filled in | Arrives empty (null) |
|---|---|
| First name, last name, full name | |
| UTM source, medium and campaign, taken from the landing page and kept for that visit | Phone, company, job title |
| Referrer (outside sites only) | Industry, company size, website |
| Landing page | UTM term and UTM content |
| First message: the first thing the visitor typed in chat | Conversation summary |
| Source, set to “Total Chat” | Geo and enrichment |
The first message holds up to 2,000 characters in the universal format. HubSpot and GoHighLevel get the first 500. HubSpot receives the lead as contact properties, Salesforce as Lead fields, and GoHighLevel as a contact with tags and custom fields. If your endpoint needs auth, you can set a token that’s sent as a bearer token.
Know two gaps before you write a single rule. Total Chat doesn’t calculate a score or rank leads. And it doesn’t look up the company behind a visit, so every fit field on the right stays empty unless something else fills it.
The nuance: a qualifying answer stays in the conversation
This is where most chat-to-CRM plans break.
Total Chat doesn’t have a qualifying-question builder. The pre-login bot asks for an email when a visitor shows strong interest, and the one lever you have over it is a free-text dashboard setting called Custom System Prompt Additions. You can use that to have the bot raise a qualifying question, such as how big the visitor’s team is.
But the answer lands in the conversation text. It isn’t a structured field, and the CRM receives the first message only. The rest of the conversation stays on the lead in your Total Chat dashboard.
So if your CRM rule says “route to sales when team size is over 20”, it’ll never fire on chat data. There’s no team-size value to read.
You’ve got three honest ways around that:
- Let a person read the conversation. For low lead volume, a rep opening the lead in the dashboard before calling is the most accurate option.
- Enrich on the email. Run an enrichment tool on the email once it reaches your CRM to fill company and size.
- Treat the first message as your intent field. It’s the one piece of the conversation that does reach the CRM.
Build your CRM rules on the fields that arrive
Once you know which fields are real, the rules get short. A starting set we’d use:
- Email domain as the first gate. A work domain moves forward; a personal domain goes to nurture. It’s crude, and it’s the only fit signal you get without enrichment.
- Campaign plus landing page for intent. A visitor who came from a comparison campaign and landed on your pricing page is warmer than one who arrived from a blog post. You get both values on every delivered lead.
- Keywords in the first message. Words like “pricing”, “SSO”, “security” or “integration” in the first message are a strong buying signal. Set a CRM rule or workflow to flag them.
- Referrer as a tiebreaker. It’s only set when an outside site sent the visitor, so a blank value isn’t a delivery fault.
Watch the 500-character cut on HubSpot and GoHighLevel. A long first message may put the important word past what those two systems receive, and a keyword rule on a truncated field will miss it.
If you want to turn these signals into a points model with weights and a threshold, that’s covered in chatbot lead qualification and scoring. This post stops at getting the right data into the CRM.
Your CRM will show fewer leads than your dashboard
Total Chat creates a lead record when an anonymous visitor starts a chat. That happens on every plan. But a lead goes to the CRM only once it has an email.
That’s the right call. A CRM full of contact-less records from people who typed “hi” is worse than useless. It does mean the two counts won’t match. Judge the chat by CRM volume alone and you’ll miss every conversation that didn’t end in an email, even though those still tell you what visitors asked.
Two more details shape what your CRM reports:
- Returning visitors stay one lead. Total Chat recognizes a returning browser with a random visitor ID in local storage (no cookies). A visitor who chatted before and comes back keeps their first chat’s campaign on the same lead.
- No last-touch. So the campaign on a CRM record is the first one that brought a chatting visitor, not the latest. If your attribution reports assume last-touch, label chat leads separately.
When a visitor types an email in the chat, it’s saved to their lead and the lead is sent to your CRM, with no separate form needed.
Test delivery before you go live
Leads captured before a webhook is configured are stored but not delivered, so Total Chat’s docs advise setting up your webhook URL before you go live with the pre-login widget. You do that in Dashboard > Integrations.
Failed deliveries retry 3 times, after 5 seconds, 30 seconds and 2 minutes, and deliveries are recorded in a delivery log in the dashboard. Read that log in your first week. A webhook that fails quietly is a common way a “working” setup turns out not to have been working.
A simple pre-launch test: open your marketing site in a private window, ask a question in the chat, give an email, and check the CRM record has the landing page, campaign and first message filled in. Then check the delivery log.
Fair warning on plans. CRM webhooks start on Pro ($99 a month on the plans table in Total Chat’s docs). On Free and Starter, lead capture and UTM attribution still run, but leads stay in your dashboard. And if your sales process needs company size or job title at the moment of handoff, chat data alone won’t give it to you. You’ll need enrichment or a person in the loop.
For where the widget sits on a marketing site and what it does before login, see AI Lead Generation Chatbot for Website Visitors. For the conversation side of lead capture, see Conversational AI Chatbot for Lead Generation. Questions about your own CRM setup? Contact the Total Chat team.
Frequently Asked Questions
What does a chatbot send to a CRM for lead qualification?
It depends on the tool. Total Chat sends, on the Pro plan and up, the visitor’s email, UTM source, medium and campaign from the landing page, the outside referrer, the landing page and the visitor’s first chat message. Name, company, job title and company size arrive empty. Your CRM then applies its own qualification rules to those fields.
Does Total Chat qualify or score leads before sending them to the CRM?
No. Total Chat doesn’t calculate a score or rank leads. It gathers signals in the chat and sends each lead to your CRM once the visitor has shared an email. Qualification and scoring happen in your CRM or marketing automation tool, which also holds the rest of the lead’s history and whether past leads became customers.
Which CRMs can receive leads from Total Chat?
HubSpot, Salesforce and GoHighLevel each get their own field format: contact properties for HubSpot, Lead fields for Salesforce, and a contact with tags and custom fields for GoHighLevel. Any other CRM, such as Pipedrive or Zoho, connects through Zapier or Make using Total Chat’s universal lead format. CRM delivery is on the Pro plan and up.
Can a qualifying question in chat fill a field in my CRM?
Not as a structured field. You can use Total Chat’s Custom System Prompt Additions setting to have the bot ask something like team size, but the answer stays in the conversation text. The CRM receives the first message only, and the full conversation stays on the lead in your Total Chat dashboard.
See what your chat leads look like in your CRM
Total Chat captures an email in the conversation, records the campaign and landing page, and posts each lead to HubSpot, Salesforce, GoHighLevel or any webhook on Pro — installed with one script tag at one flat price per workspace.
Try It Free