Support guide · CRM workflow

Client Enquiry Workflow: Website Form → CRM → Automatic Follow-Up

A practical workflow for a 1–5 person service business that is manually copying website or email enquiries into a CRM and relying on memory for the next step. Connect the systems you already own before replacing them or adding another platform.

First decide whether you need a CRM Do you need a CRM first?

The target workflow

Make one enquiry travel from arrival to a clear next action without re-keying it.

For a small service business, the useful outcome is not “automation”. It is that a genuine client enquiry arrives, creates or updates the right CRM record, receives an appropriate acknowledgement, becomes visible to the right person and has a defined follow-up step.

If your current website form and CRM can already do that natively, use them. If you already pay for an automation layer such as Zapier or Make, test that next. Add another product only when a real connection gap remains.

First: is automation even justified?

A manual process can still be proportionate at very low volume.

Not every website form needs an automation platform. If you handle only a handful of enquiries each month, nobody is missing them and the process is reliable, keep the manual process until there is a real failure to fix.

Keep it manual

Three enquiries a month, one owner, one tracking place, no missed follow-ups. Keep the process simple.

Connect the intake

Enquiries arrive in a website form or inbox and somebody manually copies them into HubSpot or Pipedrive. The gap is the connection.

Decide on the lead system first

Enquiry volume or follow-up failures have outgrown the manual process and there is no central CRM/lead record yet. Solve that first, then connect the intake.

The simple model

One enquiry should have one predictable route.

1. Enquiry arrivesWebsite form, shared inbox or another agreed intake source.

2. CRM record is created or updatedUse a stable identifier such as email so repeat enquiries do not automatically become duplicate people.

3. Owner is clearOne person or queue is responsible for the next action.

4. Customer is acknowledgedConfirm receipt when appropriate; do not pretend a sales conversation has happened.

5. Follow-up is made visibleCreate/flag the next activity, notification or workflow step supported by the CRM and plan.

6. Outcome is recordedQualified, not a fit, booked, won, lost or another status your business actually uses.

Step 1

Map one real enquiry before changing any software

Take a recent enquiry and write down what really happened. Do not map the process you wish existed.

Where did it arrive?
Website form, contact email, shared inbox, referral form, advert lead form or somewhere else?
Where was it copied next?
CRM, spreadsheet, task list, notebook or another inbox?
Who decided who owned it?
If the answer is “whoever noticed it first”, ownership is part of the workflow problem.
How did the client know it had been received?
Automatic confirmation, personal reply, or no acknowledgement at all?
How was the next action remembered?
CRM activity, task, notification, calendar reminder, inbox flag or human memory?

The first version of the automated workflow should remove one or two fragile hand-offs from this real path. It does not need to redesign the whole sales process.

Step 2

Choose one CRM or lead system as the system of record

If the business is running two competing CRMs, review that duplication before connection work begins. Building automations around two CRMs usually makes ownership less clear, not more.

Existing CRM works

Keep it. The task is to connect the intake and make ownership/follow-up reliable, not to start a migration project.

No CRM yet

Do not add Zapier or Make merely to move data between ad-hoc places. First decide whether the enquiry volume/problems justify a structured CRM or lead system.

Step 3

Use the shortest connection path available

Test connection options in this order. Each extra layer creates another place that can fail, need permission or require maintenance.

Route	Use it when	Example
1. Native CRM form	The CRM can own the public form without damaging the website/customer experience.	HubSpot forms can capture visitor information into CRM records; Pipedrive Web Forms can send submissions into Pipedrive as leads/deals, but Web Forms are part of LeadBooster.
2. Native connector	Your existing website/form product already has a reliable supported CRM integration.	Keep the existing form and connect it directly rather than rebuilding it.
3. Existing automation layer	You already pay for Zapier or Make and the required trigger/actions are supported.	Form submission → create/update CRM record → notification/next action.
4. New automation product	No native/existing route can reliably handle the required connection.	Price only the smallest automation capability needed for the proven workflow.

Do not buy the automation layer first. A new Zapier/Make subscription should be considered only after the native and already-available routes have been ruled out.

Step 4

Keep the enquiry fields lean enough to maintain

The first workflow usually needs far fewer fields than a CRM makes available. Capture what is needed to identify, route and follow up the enquiry.

Usually useful

Name, email, company where relevant, phone only if the workflow actually uses it, enquiry/message, source and consent/communication information where applicable.

Workflow fields

Owner, status/stage, next action/date and perhaps service/type if that changes routing.

Avoid by default

Dozens of speculative qualification fields, duplicate notes and information nobody will actually use. More fields create more mapping and maintenance.

Use a stable identifier—commonly email—to check whether the person already exists before blindly creating another record. The exact de-duplication mechanism depends on the CRM/connector, so test it rather than assuming.

Step 5

Create or update the CRM record before you automate follow-up

HubSpot's current form tools can collect visitor information and create or update CRM records directly. Pipedrive's Web Forms can capture website visitors into Pipedrive as leads or deals, but the feature sits inside its LeadBooster add-on rather than every core plan.

If your form is external, test one submission through the chosen connector and confirm:

the contact/person record is correct;
the lead/deal is created only when your workflow actually needs one;
the source is recorded sensibly;
repeat submissions do not produce uncontrolled duplicates;
free-text enquiry content lands somewhere visible;
the correct owner/team can see the record.

Step 6

Automate acknowledgement and the next internal action—without pretending the sale is automated

A useful first follow-up automation is modest. It confirms that the enquiry has entered the process and makes the next human action difficult to forget.

Customer acknowledgement

HubSpot currently supports simple post-form workflows including follow-up emails. If your form platform already sends a good confirmation, do not create a second one just because the CRM can.

Internal follow-up

Use the CRM's available notification/activity/automation features to make ownership and next action visible. Pipedrive's Automations, currently available on Growth and higher, can respond to record events with actions such as creating activities or sending email from a synced account.

Keep the first message factual: “We have received your enquiry and will reply by…” is usually safer than an elaborate automated sales sequence before anybody has read the enquiry.

Step 7

If you use Zapier or Make, build one small flow and make failure visible

Both Zapier and Make currently expose connectors capable of creating/updating CRM records in HubSpot and Pipedrive. That does not mean you need either product; it means they are possible connection layers where native options do not cover the job.

Trigger:
Use one specific new-enquiry event from the form/inbox system.
Find before create:
Where the connector supports it, look for an existing person/contact before creating another.
Create/update the CRM record:
Map only fields needed for the workflow.
Set ownership/next action:
Use a CRM field, activity or notification supported by the selected plan.
Confirm success:
Make sure somebody can see whether the automation ran. Silent failures are worse than visible manual work.

If you already pay for both Zapier and Make, choose one automation layer for the pilot before adding a third connection product.

Step 8

Test the workflow with awkward cases, not only the perfect submission

New person

A completely new enquiry should create the intended CRM record, ownership and next action.

Existing person

A repeat enquiry should update or associate sensibly rather than silently creating duplicate contacts.

Missing optional field

The workflow should not fail merely because a non-essential field is blank.

Long/free-text message

Confirm the enquiry itself remains readable in the CRM rather than being truncated or mapped to the wrong field.

Connector failure

Switch off or deliberately break a test step where practical and confirm that failure is visible to somebody.

Out-of-hours enquiry

Check that acknowledgement wording and promised response time still make sense outside working hours.

A sensible first workflow

Example: a three-person consultancy already using a CRM

Website enquiry submittedExisting website form remains in place because clients already use it successfully.

Existing connector/automation receives submissionNo new form product is introduced unless necessary.

Find or create CRM contactEmail used as the primary lookup where supported.

Create/flag opportunityOnly if this type of enquiry belongs in the sales pipeline.

Assign owner / notify teamOne person is visibly accountable.

Send receipt acknowledgementPromise a realistic response window, not an automated sales pitch.

Create visible next actionCall, email, review or another concrete follow-up.

Practical answer: keep the CRM and intake source if they work; remove the repeated manual transfer.

When NOT to automate more

Stop when the workflow is reliable enough.

Do not add lead scoring simply because the CRM offers it.
Do not automate qualification decisions that still require human judgement.
Do not send a long email sequence to every enquiry before checking whether it is appropriate.
Do not connect every form field to every CRM field.
Do not add a second CRM to solve a connection problem.
Do not keep both Zapier and Make in the same simple workflow without a distinct reason.

The aim is a boring, dependable hand-off. Complexity earns its place only when a real workload demands it.

The implementation ladder

The free guide should be enough for a straightforward setup.

This page is intentionally not a teaser. A competent owner should be able to map, connect and test a basic enquiry workflow from the process above when their products already support the necessary connections.

A future paid Client Enquiry Workflow Pack would need to add genuine convenience—for example field-mapping worksheets, acknowledgement templates, owner/next-action templates, testing scripts, launch checklists and handover documentation.

A future done-for-you or specialist-referral offer would sell implementation time and tested configuration, not access to instructions hidden from this guide.

Before you call it finished

Run the workflow checklist

one CRM/system of record is clearly chosen;
one real intake path has been mapped;
native/existing connections were checked before new software;
fields are limited to information somebody uses;
duplicates have been tested;
ownership is visible;
the customer gets an appropriate acknowledgement;
the next internal action cannot quietly disappear;
automation failures are visible;
the workflow has been tested with real-world edge cases.

Run the decision first

If you are still unsure whether the business needs CRM software at all, start with our CRM decision guide before adding connections or automation.

Do I need a CRM?

Sources and scope

Published facts used on this page

The preferred connection order and implementation sequence are UK Software Stack editorial judgement. Current vendor sources support the specific form, CRM and automation capabilities described here.

Page reviewed: 30 August 2026. CRM plans, form features, automation limits, connector actions and permissions can change. Verify the current plan and test with non-critical data before depending on an automated workflow. This page is general workflow guidance, not a promise that a particular integration will suit every website, CRM or data-handling requirement.