← Nexus resources Contractor enquiry workflow guide

Follow up every lead without losing the human touch. A clearer handover.

A practical system for acknowledging, qualifying and routing contractor enquiries while keeping quotes, advice and important decisions with real people.

7 stage workflowUpdated 15 August 2026By Alex Player
Illuminated glass workflow nodes carrying an enquiry through a follow-up sequence
Evidence-led resource7 stage workflow
The principle

Automate the handover, not the judgement.

A useful contractor follow-up system confirms that an enquiry arrived, collects only the missing details, routes the job to the right person and makes ownership visible. It should not invent a quote, promise a call time nobody can meet or pretend an automated reply is a tradesperson.

The workflow should fit the team’s actual capacity. A fast acknowledgement helps only when the next human task is clear and someone is responsible for it.

The seven-stage workflow

One enquiry, one accountable path.

  1. 01
    Capture

    Receive the call, form, Local Services Ad or referral with source and consent recorded.

  2. 02
    Acknowledge

    Confirm receipt and set a truthful expectation for what happens next.

  3. 03
    Complete the brief

    Ask only for missing essentials such as postcode, service, timescale or supporting photos.

  4. 04
    Route

    Send the enquiry to the correct person, inbox, CRM or job system with a fallback.

  5. 05
    Review

    A person assesses fit, safety, availability and the information needed for a quote or visit.

  6. 06
    Progress

    Record the next action and keep the customer updated when the status meaningfully changes.

  7. 07
    Learn

    Close the loop with outcome, lead quality and sales feedback—not just a “form submitted” count.

A useful acknowledgement

Say what is true, then make the next step easy.

Example structure

Thanks—your enquiry has reached [Business].

We’ll review the service, location and details you sent. A member of the team will respond during our published working hours. If the issue presents an immediate risk, use the emergency guidance provided by the appropriate service.

Reference: [enquiry ID] · You can add photos or missing details here: [secure link]

Adapt the wording to the real operating model. Do not promise a response time unless it is monitored and consistently achievable.

Safeguards before software

Design for the exception as well as the happy path.

01

Consent and purpose

Explain why the data is collected, who receives it and how the person can change their communication preferences.

02

Human ownership

Every alert and stage needs a named role, a deadline and a fallback when that person is unavailable.

03

Data minimisation

Collect what the next decision needs. Avoid sensitive or excessive information in general enquiry tools.

04

Failure visibility

Test undelivered messages, expired credentials, duplicate enquiries and system downtime—not only the successful route.

05

Manual override

Let the team pause automation, correct a record and handle unusual work without fighting the workflow.

06

Outcome reporting

Separate enquiries, qualified opportunities, quotes and won work so automation is judged on useful outcomes.

15-minute workflow audit

Can the current system answer these questions?

Follow-up readinessUse this before choosing another platform.
0of 7

Lead follow-up questions

What should contractor lead follow-up automate?+

Automation is most useful for receipt confirmations, missing-detail requests, source recording, routing, task creation and status reminders. Quotes, technical advice and important customer decisions should remain under human review.

Does faster automated follow-up guarantee more jobs?+

No. Results also depend on demand, service fit, availability, pricing, trust, human response quality and the sales process. The workflow should be measured using qualified and won work, not message speed alone.

What information should an enquiry form collect?+

Collect only what the next decision needs, such as service, location, timescale, contact details and optional supporting information. Avoid unnecessary or sensitive data in a general enquiry flow.

What happens when an automation fails?+

A production workflow needs visible error alerts, a named owner, retry or fallback routes and a manual override so the team can continue without losing the enquiry.

Turn the map into a real systemNexus can document the current process and prototype the smallest useful workflow.
Explore workflow automation