A better enquiry process gives every suitable opportunity an owner, a current status and a defined next action. It confirms receipt to the prospect, preserves the source and consent evidence, supports timely human follow-up and makes failures visible.
The process starts before a form is submitted and ends only when the enquiry is qualified, won, lost or deliberately closed. A contact form, shared inbox or CRM subscription is only one component. None of them creates an operating process by itself.
For an established service business, the design objective is not maximum form volume. It is consistent progression of relevant enquiries without relying on memory.
Define the complete enquiry boundary
Begin by stating what counts as an enquiry and where it can arrive. The list may include website forms, direct email, telephone calls, referral introductions, event conversations and selected social channels.
Then define the end states. A practical process normally closes an enquiry as one of the following:
- Qualified and progressing.
- Not suitable now, with a documented reason.
- Nurture with a justified future review date and appropriate permission.
- Won and handed into onboarding.
- Lost to another option or no decision.
- Do not contact.
Without these boundaries, reporting becomes misleading. A website team may count a form completion while the commercial team counts only booked calls. Both figures can be correct, yet neither explains the full route.
If the business does not yet know where opportunities disappear, first trace the points where leads are being lost. Process design should follow evidence rather than assumptions.
Create one minimum viable enquiry record
Every channel should create or update one controlled record. The minimum useful fields are usually:
- Contact and organisation identity.
- Enquiry date and channel.
- Original source and campaign information where available.
- Service or problem area.
- Assigned owner.
- Current stage.
- Last meaningful activity.
- Next action and due date.
- Qualification decision and reason.
- Consent and suppression status where relevant.
Collect only information that supports a defined purpose. The UK Information Commissioner’s Office describes the data-minimisation principle as keeping personal data adequate, relevant and limited to what is necessary. A longer form is not automatically a better qualification tool.
This record must have a nominated system of record. If a spreadsheet is used during an early controlled phase, state that clearly. If the CRM is authoritative, private notes in personal inboxes must not become an invisible competing record.
Use stages that describe decisions, not vague activity
Pipeline stages should tell the team what has happened and what must happen next. “Open” and “In progress” are too ambiguous to control work.
A service-business enquiry route could use:
- Received — the record exists and the prospect has confirmation.
- Review required — an owner must inspect fit and completeness.
- Contact due — the next human action and deadline are recorded.
- Discovery arranged — a date is booked and preparation is defined.
- Qualified — the problem, fit, timing and decision route justify progression.
- Proposal or recommendation issued — the commercial next step is with the prospect.
- Decision pending — follow-up has a date and a reason.
- Closed — won, lost, deferred or suppressed with an accurate outcome.
For each stage, specify its entry condition, owner, permitted actions, expected evidence and exit condition. That stops different team members interpreting the same stage differently.
The objective is operational clarity, not an elaborate pipeline. If two stages do not change ownership, evidence or the next decision, they may not need to be separate.
Assign ownership before automating acknowledgements
An automatic confirmation is useful because it tells the prospect that the submission was received. It is not evidence that somebody inside the business owns the opportunity.
Every new record needs an assignment rule. That rule may depend on service, geography, account type, existing relationship or team availability. It also needs a fallback owner when the normal route fails.
Define what happens when:
- The named owner is absent.
- The enquiry contains incomplete information.
- The same person submits twice.
- A notification email fails.
- The integration cannot create the CRM record.
- The enquiry reaches the wrong team.
- The due time passes without activity.
A good process makes exceptions visible. Sending another notification into an unattended inbox is not a recovery mechanism.
Make the form easy to complete and safe to operate
The form should collect enough information to route the enquiry, not attempt to conduct the entire sales conversation.
The W3C’s Web Accessibility Initiative recommends clear labels, instructions, validation and user notifications. Its forms guidance also notes that people generally prefer simple, short forms and may abandon forms that request irrelevant or excessive information.
Test the form with keyboard navigation, realistic error states and mobile input. Required fields must be identifiable without relying on colour alone. Error messages should explain what needs correction, and a successful submission should produce an unmistakable confirmation.
Form QA must include more than its appearance. Submit controlled examples and verify:
- The public success state.
- The stored record.
- The owner assignment.
- The customer acknowledgement.
- The internal alert.
- The source and consent fields.
- Duplicate behaviour.
- Failure logging.
This is especially important before increasing acquisition activity. Sending paid traffic into an unverified journey simply increases the number of opportunities exposed to the same defect. Use the wider pre-advertising readiness review when the weakness may extend beyond enquiry handling.
Separate acknowledgement, qualification and sales response
These are three different actions.
Acknowledgement confirms that information was received and sets an honest expectation. It should not pretend that a person has reviewed the enquiry when nobody has.
Qualification determines whether the problem, service fit, authority, timing and practical constraints justify progression. The rules should be written down so unsuitable work is not advanced merely because one person is optimistic.
Sales response is the meaningful human action that advances the decision. It may be a clarifying question, a discovery invitation, a relevant resource or a clear decline.
Automation can support all three, but it should not hide the difference between them. A fast generic email is not the same as a useful response.
Write follow-up rules as operating instructions
“Follow up regularly” is not a process. Define the trigger, channel, owner, purpose and stop condition for each step.
For example:
- When a qualified enquiry has no discovery booking, create a dated owner task.
- When a requested document is issued, record the asset and next review date.
- When a prospect declines or opts out, stop sales and marketing activity and preserve suppression.
- When an opportunity is deferred, record why and what future event would justify contact.
Do not build sequences simply to increase message volume. Each follow-up needs new relevance: a decision question, requested evidence, implementation detail or useful clarification.
This is where disconnected websites, inboxes and CRMs often create revenue leaks across the customer journey. The process should expose the handoff, not assume it worked.
Measure progression, not just submissions
Google Analytics documents `generate_lead` as the recommended event for measuring a generated lead, such as a form submission. That provides a useful website event, but the commercial measurement must continue beyond it.
Track a compact set of operational measures:
- Valid enquiries received by source.
- Duplicate, spam and unsuitable submissions.
- Enquiries with an assigned owner.
- Time to first meaningful human action.
- Percentage reaching each defined stage.
- Overdue next actions.
- Qualified opportunities by source and service.
- Closed outcomes and recorded reasons.
- Notification, integration and delivery failures.
Do not turn every measure into a target immediately. First establish whether the data is complete and consistently defined. The GOV.UK Service Manual advises measuring the user journey across the transactions that solve the whole problem, and combining performance metrics with other evidence where necessary.
Choose technology after the operating rules
A CRM can centralise records, ownership, stages, tasks and reporting. Automation can create records, preserve attribution, send acknowledgements and raise exceptions. Neither can decide the process on behalf of the business.
Map the manual route first, then specify the technology requirements. The difference between a focused marketing review and a wider business audit matters here: a form optimisation project will not repair undefined ownership, inconsistent qualification or an absent follow-up rule.
Before selecting software, require evidence that the chosen system can support:
- The agreed stages and mandatory fields.
- Role-appropriate access.
- Duplicate handling.
- Source preservation.
- Consent and suppression controls.
- Task and escalation rules.
- Export and recovery needs.
- Tested website and mailbox connections.
- Useful reporting without manual reconstruction.
The smallest system that can run the governed process reliably is usually preferable to a feature-heavy platform the team cannot maintain.
Implement the process as a controlled release
Do not replace every channel and workflow at once. Use representative enquiries and a limited operating group.
Start with one primary route. Document the current behaviour, configure the minimum record and stages, assign ownership, connect the form, test acknowledgement and alerts, then run success and failure scenarios. Review the resulting records with the people who will actually use them.
Only expand when the process can answer five questions without guesswork:
- Where did this enquiry come from?
- Who owns it now?
- What has happened?
- What happens next, and when?
- How will we know when it is complete?
That is the standard for an enquiry process that can support growth without depending on one person’s memory.
Diagnose the journey before buying more software
If enquiries are arriving but ownership, qualification, follow-up or measurement is unreliable, the first step is to identify the earliest commercially important failure.
The £297 Acquisition Audit reviews the website-to-enquiry journey, lead handling, CRM and relevant workflows. Within five working days, Acquisition Works provides prioritised actions and an implementation roadmap. The audit does not require you to proceed into a larger implementation project.