Sending Website Leads Straight Into Your CRM
By CodexierPublished 7 min read
Every form, chat and booking tool on your website produces leads, and most of them land in an email inbox where they wait for someone to copy them into the CRM, or forget to. Connecting the website directly to the CRM removes that step. This guide covers the five pieces that make the connection reliable rather than just technically present.
Mapping form fields to CRM fields
Start from the CRM's side: which fields does a salesperson need to act on a lead? Name, company, email, phone, what they want, where they came from. Then design the form to collect exactly those and nothing more. A form field with no CRM home is a question you should not be asking. Free-text 'message' fields map to a note or a description field; dropdowns map to CRM picklists with identical values, so reports can group on them.
| Form field | CRM field | Note |
|---|---|---|
| Name | First name, Last name | Split at the form, not in the CRM |
| Email (matching key) | Lowercase and trim before matching | |
| Company | Company name, matched or created | Org number if you sell B2B; it prevents duplicates better than names |
| Interest dropdown | Picklist with the same values | Drives routing and reporting |
| Message | Note on the contact or deal | Never the only place the errand is recorded |
| Hidden fields | Source, campaign, page, form name | Filled by the page, invisible to the visitor |
Both HubSpot and Pipedrive support hidden fields and custom properties; our comparison of the two covers how their forms differ.
Source and campaign tracking
A lead without a source is a lead you cannot learn from. The mechanism is simple: when a visitor arrives from an ad or a newsletter, the link carries UTM parameters; a small script stores them for the session; the form writes them into hidden fields; the hidden fields map to CRM properties. Later, a report on 'deals won by original source' tells you which channel produces customers rather than clicks.
- Store the first source the visitor arrived with, and optionally the last, on the contact.
- Record the page and the form name so you can see which pages actually generate enquiries.
- Use a fixed UTM naming convention; free-form campaign names make reports useless within a quarter.
- For phone leads, a call-tracking number or simply asking 'how did you hear about us' in the CRM keeps the picture complete.
Deduplication rules
The same person fills in a form twice, books a call and later downloads a guide. Without a rule you now have four records and four owners. The rule is: match on email first; if there is a match, update the existing contact and add a new activity or deal; if not, create the contact. For companies, match on org number where you have it, otherwise on a normalised name. Decide what wins on conflict (newer phone number replaces older, but never blank out a filled field).
Contact exists
Add a note or activity with the new enquiry, update changed fields, notify the existing owner rather than assigning a new one.
Contact is new
Create the contact, the company if needed, and a deal or lead in the first pipeline stage.
Uncertain match
Same name, different email: create a new contact and flag it for a human to merge. Never auto-merge on name alone.
Instant alerts to the right person
Speed of first response is the single biggest lever in lead conversion, and the alert is what creates speed. Route by the interest field or by region, assign an owner, and send the alert where that person actually looks: a Slack or Teams channel, an SMS for high-value enquiries, an email as the fallback. Include the contact's name, what they asked for and a direct link to the CRM record, so the reply starts from the record and gets logged.
- Assign an owner automatically by a rule (round robin, region, product) so no lead sits unowned.
- Send the alert within a minute of submission; a webhook-driven connection does this, a nightly sync does not.
- Create a follow-up task with a due time, so the lead appears in the owner's queue even if the alert is missed.
- Escalate: if the task is not completed within a set time, alert a manager or reassign.
Consent and GDPR records
A form submission is personal data, and the CRM must record why you hold it. For a sales enquiry the lawful basis is usually legitimate interest or steps before a contract, and no consent box is needed for replying. Marketing emails are different: they need either consent or an existing customer relationship, and the CRM has to store which one applies, the exact wording the person saw, and when. Write those into the contact from the form, and make the privacy notice link visible next to the submit button.
When you do not need help: a single contact form and a CRM with a native form builder can be connected by you in an hour with the mapping table above. Buy the implementation when there are several forms, chat and booking tools, a deduplication problem already in the data, or routing rules across a team; it is a fixed price on the pricing page, and a short call will tell you which of those situations you are in.
- CRM ImplementationPipeline design, website and booking connections with source tracking and deduplication, alerts and training.
- Automation & Integration OptimizationFor a CRM already connected: fix the mapping, the duplicates and the alerts that stopped working.
- Book a free 15-minute callTell us which forms and tools you have and where leads land today; we say what the connection needs and what it costs.
Frequently asked questions
Do I need Zapier or Make to connect a form to the CRM?
Not if the CRM has its own form builder or a native integration with your form tool; native is simpler and more reliable. An integration platform earns its place when several tools feed the CRM, when you need transformation (splitting names, normalising phone numbers) or when a booking tool has no native connector. Prefer webhooks over scheduled syncs so alerts arrive within a minute.
What about leads from chat and booking tools?
The same rules apply: map the fields, carry the source, match on email, notify the owner. Booking tools typically create a meeting plus a contact; make sure the meeting is attached to the existing contact rather than a new one. Chat transcripts belong in a note, not in a contact field.
Can the website write directly to Fortnox instead?
It can, but it should not. Fortnox is the ledger, and a lead is not a customer yet. Keep leads in the CRM and create the Fortnox customer when a deal is won, with the org number and VAT number checked, so the accounts only contain real customers.
How do I stop spam submissions polluting the CRM?
Use a modern invisible captcha or a honeypot field on the form, reject submissions with no valid email format, and quarantine entries from known disposable domains into a review list rather than creating contacts. Spam that reaches the CRM is expensive because someone has to delete it and it skews the source reports.
Do your leads still land in an inbox?
In fifteen minutes we look at your forms, chat and booking tools and tell you what a direct CRM connection would need: field mapping, source tracking, deduplication, alerts and consent, and what it would cost.
Book a free 15-minute call