Somebody lands on your shipping page with one question. The chat opens and asks for their name, their email, their phone number and the size of their company.
They close it. You did not get the lead, and they did not get the answer, which is the part that would have made them want to give you the lead.
The order matters more than the form does.
Ask after you have been useful
A visitor who has just been told something true and specific will hand over an email. A visitor who has been told nothing will not. That is the whole strategy, and it is why lead capture inside a chat beats a form in a sidebar: the chat knows whether it has been useful yet, and a sidebar does not.
So the sequence is: answer the question, cite where the answer came from, then ask for one thing you actually need, and say what it is for.
Three ways to ask, and what each one costs
A form here is a set of fields plus a decision about how to ask for them. You build the fields once under Leads, then each widget picks its own layout under Lead capture, so the same form can be a panel on one site and a conversation on another.
Only the third one keeps the thread intact. The assistant asks one or two questions at a time, in between answering, and it does not ask twice for something it already has.
Two details that are easy to miss. The consent text is spoken before the assistant asks for contact details, not buried under a checkbox. And when an answer fails validation, a dropdown value outside its options or an address that is not an address, the assistant is told to ask for that item again rather than storing something broken.
Half a lead is still a lead
The conversation above could have ended after the email, and in real traffic a lot of them do. Each answer is stored as it is given, so an incomplete lead is kept and marked Partial with a Chat trigger. It becomes an ordinary lead the moment the last required field arrives.
This is worth knowing before you design the form, because it changes what "required" means. A field marked required does not block the email you already have. It only decides when the record stops being partial.
It also tells you where to look. A pile of partial leads on one page is not a CRM problem, it is a sign that the assistant is asking for the third field before the visitor has a reason to give the second.
What actually reaches your CRM
More than the visitor typed. Alongside your own fields, the values that came with the visit can be mapped: UTM tags, click IDs, the referrer, and the landing page they arrived on. Mapped under Destinations, each one can land in its own CRM column, so utm_campaign is a column rather than a note somebody has to read.
Phone numbers are stored in E.164, which is the detail that saves you a week later: every destination receives one dialable shape instead of five local ones.
On the HubSpot side, a route decides where the lead goes. The object is usually a contact, and a route can also land on a deal or a ticket if you grant those scopes. Auto-map fills in what it is confident about and you fix the rest by hand, which takes a few minutes once.
Contacts are matched by email. When the same person writes again, the existing record is updated instead of a duplicate appearing, and fields you left empty are not sent at all, so a blank in the chat cannot overwrite something a salesperson typed into HubSpot last month.
The three ways it fails
- A required HubSpot property with no value. The lead fails on arrival. If your CRM insists on a lifecycle stage or an owner, give the route a value for it.
- A missing scope. HubSpot associates a new contact with a company by itself, and without the company scope that association can take the whole write down with it.
- An outage, which is the forgivable one. Network problems and HubSpot outages are retried five times over roughly two hours. A request that HubSpot rejects is not retried, because retrying a rejection just produces the same rejection.
Before you trust any of it, send a sample lead. It creates one invented contact, is not stored as a lead, and does not count against your plan, so you can watch the record appear with your own eyes rather than hoping.
Where leads can go today
Five destinations ship right now: HubSpot, ClickUp, Mailchimp, CallRail and Slack. Slack is the one people underrate, because a lead that lands in a channel within a minute gets answered the same day, and a lead that waits in a CRM queue does not.
Salesforce, Pipedrive, Zoho, monday CRM and Attio have pages on this site and are not connected yet. If your process depends on one of them, plan for the five above and ask us where the other one stands before you build on it.
The configuration itself is in the lead forms guide and the HubSpot guide, and the shape of the whole thing is on the lead generation page. What those pages cannot tell you is the only part that is actually hard: answer first, ask for one thing, and say what you need it for.
