Website forms that create CRM records, not just email

A contact form that sends an email to a shared inbox is not a lead system. It is a notification. Nobody owns it, nobody can count it, and the moment the inbox gets busy it becomes the place where good inquiries wait three days for an answer.

AERVIO wires website forms so that a submission creates a record in the CRM — a contact, usually a company, often a deal or a task — with the context a salesperson needs to reply well. This is the practical core of treating the site and the CRM as one system.

What a form submission should become

Every form on a site maps to a specific outcome. Before we build, we write that mapping down:

If you cannot fill in the right-hand columns, the form is not ready to publish. "It goes to info@" is not a routing rule.

The fields that carry the weight

A short form converts better than a long one, but a form with no context creates more work than it saves. Our approach is to keep the visible fields to what the first reply needs, and capture the rest silently:

• Visible: name, email or phone, and the request in the visitor's own words. Add company only if you sell to businesses and the answer changes who replies.
• Hidden, captured automatically: the page the form was on, the language of that page, the referrer, and UTM parameters if a campaign sent them.
• Consent: a clear, unticked statement where the follow-up will include commercial messages. See CASL and first touches in Canada for how we think about what a form can and cannot authorize.

The hidden fields are where reporting comes from. If every record carries its source page and language, you can answer "which pages produce real inquiries?" from the CRM instead of guessing from sessions.

Records, not rows in a spreadsheet

The failure mode we see most often is the glue layer: a form plugin sends to a spreadsheet, a person copies rows into the CRM on Fridays, and duplicates multiply. The better pattern is a direct write with a few safeguards:

• De-duplication by email (and phone where available), so a returning visitor updates the contact rather than creating a second one.
• Company matching by domain, so three people from the same firm land on one account.
• Idempotent submission, so a double-click or a retry does not create two deals.
• A visible failure path. If the CRM is unreachable, the submission is stored and retried, and someone is alerted. Silent failure is the worst case: the visitor sees "thank you" and the lead is gone.

None of this requires a specific vendor. HubSpot, Zoho, Pipedrive and a custom CRM can all receive a webhook or API call. What matters is that the contract between form and CRM is written down and tested. Our view on choosing the tool is in a CRM built around how you sell.

Language is a field

For a Quebec audience, the form is a French page first. The labels, validation errors, confirmation message and the automatic reply should exist in French, and the language of the page is stored on the record. That one field decides who follows up and in which language, and it prevents the awkward case where a French-speaking prospect gets an English reply from a rep who never saw the form.

We do not give legal advice on language requirements; that belongs with your counsel. What we do is make the fields, the routing and the templates follow whatever line you decide on.

Test it like a buyer, then like a saboteur

Before launch, every form gets two kinds of tests.

Buyer tests. Submit it on a phone, on slow mobile data, in French and in English, with an accent in the name, with a long message. Confirm the record appears with the right owner, source and language, and that the confirmation arrives. Staging is the right place for this — see staging your sales team can preview — with submissions tagged as test data so they can be deleted.

Saboteur tests. Submit empty required fields, paste a script tag, submit twice, submit from a blocked-script browser. Spam protection matters here. We prefer invisible measures — a honeypot field, server-side validation, rate limiting — over puzzle-style challenges that cost real prospects. We do not buy or import rented lists to fill a pipeline; the records that matter come from people who chose to write to you.

What to measure

Once forms create records, the numbers become honest:

• Submissions by form, page and language
• Time from submission to first human reply
• Share of submissions that become qualified conversations
• Records with a missing owner, which should be zero

Those four figures say more about your website's commercial health than session counts. If you only watch traffic, you are measuring the door, not the room. We will not promise a conversion rate — it depends on your offer, your price and your follow-up speed — but we will promise that you can see it.

A short checklist before you ship a form

1. Does it create or update a CRM record, and not only send an email?
2. Is there a named owner or a clear routing rule?
3. Are page, language and campaign source captured?
4. Is consent stated where messages will be commercial?
5. Is the failure path visible to a human?
6. Have you tested it in both languages on a phone?

If your current forms still end in a shared inbox, that is usually a one-to-two-week fix, not a rebuild. Write to hello@aervio.io or call +1 438-498-3913, weekdays 9–17 ET, and we will walk through your forms and tell you what each one should create.

Questions

Why not just send form submissions to a shared inbox?

A shared inbox has no owner, no status and no history. Leads get answered late or twice, and nobody can count them. A CRM record has an owner, a stage, a source and a timestamp, which is what a sales team needs to follow up and measure.

What fields should a lead form capture?

Only what your first reply needs: name, a way to reply, the request in their own words, and consent where the message is commercial. Hidden fields capture page, language and campaign source. Every extra visible field costs completions, so each one has to earn its place.

Do forms need to be bilingual in Quebec?

For Quebec-facing pages, plan the form, its errors, its confirmation and the follow-up in French first, and store the language on the record so the right person answers in the right language. Your counsel decides the legal line; we build the fields and routing.