Feature · Forms and lead capture

Turn an enquiry into an owned record, not another unattended notification.

Approved forms and connected lead sources can create CRM work without manual retyping. The design still needs the right fields, consent context, duplicate rules, owner and failure path.

Subscribe to 121 CRM Seller, billing and cancellationSee customer management

Customer Thread

An enquiry enters with context

Illustrative example

Capture
Relevant fields submitted
Match
Existing record checked
Route
Owner and pipeline selected
Review
Need and permission checked
Human decision
Act
Next action recorded

Illustrative form journey. No channel, response-time or conversion claim is made.

Capture-to-owner view

Carry the enquiry context into the first action.

Relevant form fields, source, matching, ownership and review stay connected rather than becoming another isolated notification.

121 CRM · Customer thread

New enquiry09:12

Northstar Joinery

Website · Commercial enquiry

“We need a clearer way to coordinate enquiries between the office and site team.”

Owner

Amina K.

Next action

Discovery call

Enquiry
Website form
01
Conversation
Reply recorded
02
Owner
Amina assigned
03
Review
Suitability check
04
Next action
Call on Thursday
05

Illustrative exampleFictional customer and activity. Exact fields, channels and stages depend on configuration.

How it helps

See how the feature supports the work.

Each part has a clear job. It becomes useful when it fits the way customers already move through the business and your team knows when to step in.

Capability 01

Forms

Collects structured visitor details and maps supported responses into CRM records and workflows.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Turns an enquiry into usable data instead of an unstructured email.
Plan for: Generated or templated content is not automatically accurate, accessible, compliant or ready to publish.
Your team owns: A person must review content, test the journey and explicitly publish or change live assets.

Capability 02

Surveys

Collects multi-step responses with supported logic, styling and submission analysis.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Gathers more detailed requirements while keeping answers tied to the customer journey.
Plan for: Generated or templated content is not automatically accurate, accessible, compliant or ready to publish.
Your team owns: A person must review content, test the journey and explicitly publish or change live assets.

Capability 03

Chat widget

Adds supported live-chat or connected-channel entry points to a website.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Lets a visitor ask a question without hunting for a separate contact route.
Plan for: Generated or templated content is not automatically accurate, accessible, compliant or ready to publish.
Your team owns: A person must review content, test the journey and explicitly publish or change live assets.

Capability 04

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 05

Triggers

Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Lets follow-up begin from a business event instead of waiting for someone to remember.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Design the capture

Ask for enough to act — not everything you might ever want.

A useful enquiry form is short enough to complete and precise enough to route responsibly.

Purposeful fields

Collect the contact details, reason for enquiry and routing context the team genuinely needs.

Consent and notice

Provide appropriate privacy information and keep marketing choice separate from a service enquiry where required.

Boundary required

Sensitive information

Do not invite clinical, legal, financial or other sensitive detail into a general lead form without an approved need and handling route.

From submission to work

Create ownership, not simply a contact row.

The capture should establish source, duplicate handling and the first visible next action.

Match or create

Define how email, phone or another identifier is used to update an existing record or create a new one.

Source and context

Record the useful origin and campaign context without treating tracking data as proof of causation.

Owner and next action

Assign the enquiry to a person or queue with a due point and escalation route.

The record created

Make the useful context visible after submission.

The resulting record should show who the customer is, why they contacted the business and what happens next.

121 CRM · Contact workspace

Alex King

Northstar Joinery

alex@example.test

Preferred: email

Contact confirmed

Activity thread

Newest first

Today · 10:05

Suitability reviewed by Amina

Today · 09:18

Record assigned to Amina

Today · 09:13

Acknowledgement recorded

Today · 09:12

Website enquiry captured

Human decision

Confirm fit and priority

Review the request before changing the opportunity stage.

Next action

Discovery call

Thursday · 11:30

Illustrative exampleThe workspace demonstrates information hierarchy rather than a fixed field set.

Reliability

Test duplicates, missing data and failed delivery.

A confirmation screen does not prove the record arrived correctly or reached the right person.

Validation

Test required fields, formatting, spam controls and accessible error messages.

Failure visibility

Make rejected submissions, connection failures and routing gaps visible to an owner.

Set expectations

Acknowledgement

Where configured, confirm receipt without promising an outcome or response time that the team cannot meet.

Questions about this page

Useful answers, without the sales fog.

1. Can our website form create a CRM enquiry?

Potentially. The form, connection route, fields, consent wording, duplicate rules and owner need to be reviewed and tested for the specific website and account.

2. Will every lead source connect automatically?

No. Each form, advertisement or channel has its own connection, permissions, field mapping, limits and failure modes.

3. Does lead capture guarantee a faster response?

No. It can remove manual retyping and make ownership visible, but actual response depends on the team, operating hours, workflow and exceptions.

Read all CRM questions

Continue the journey

Customer management Sales pipelines CRM for trades

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing