Small business guides

A practical CRM lead follow-up workflow for small businesses

A useful CRM setup gives each enquiry a status, an owner and a next action. Before choosing software or adding automation, map what should happen from the first enquiry to a booked appointment or a closed conversation.

Use the workflow below as a planning checklist. It is an illustrative process to adapt during setup, not a claim that every step is included or already configured in every CRM plan.

Spireo · Updated October 15, 2026

Do I need a new CRM, or can my existing tools handle enquiry follow-up?

You may be able to use what you already have. Start with one recent enquiry and check whether your team can find its history, see who owns the next step and tell when follow-up is due. A new subscription is worth considering only after you identify the missing step.

  • Keep the current process if a shared inbox, task list or existing job system gives each enquiry an owner, a due date and a reliable way to record replies, bookings and contact preferences. A manual process can be a sensible starting point when the team can maintain it consistently.
  • Configure an existing feature if your current software already supports the missing reminder or status. Check your plan, settings and staff permissions before buying a second system.
  • Consider a scoped CRM setup if enquiries repeatedly lose their owner or next action, or if the team cannot see which conversations still need attention. Define the handoff first, then check whether the proposed setup can support it.

For example, Jobber documents scheduled quote follow-ups, subject to feature availability and settings. If your gap is following up on quotes already sent, review that option first. A website enquiry that has not yet become a quote is an earlier step; check that separately rather than assuming a quote reminder covers it.

Write the decision in one sentence: “Our existing tools handle ___, but ___ needs a named owner and a clear next action.” If you cannot fill in the second blank, pause the purchase and review the process with your team. Spireo’s CRM service scope does not automatically replace dispatch or accounting software; external integrations require feasibility and written scope confirmation.

Start with one enquiry path

Choose one common source, such as the contact form on your website. List the information your team needs to respond. For a cleaning business, that might include the requested service, general service area and preferred way to be contacted. Collect only what the enquiry needs.

A form submission, a phone callback request and a calendar booking may need different handling. Agree on how each enters your process and which connections require additional work. Spireo’s CRM setup and lead follow-up service scopes forms, pipelines, calendars and workflows around the business process.

Give every stage a clear meaning

Keep the first pipeline simple enough that staff can use it consistently. For example:

  1. New enquiry: received and awaiting review.
  2. Contact in progress: a named team member is handling the conversation.
  3. Appointment booked: the agreed next step is on the calendar.
  4. Closed: the enquiry is completed or no further follow-up is appropriate.

Decide who moves a record and what evidence is needed. A customer asking about availability should not be treated as booked until the agreed booking step is complete.

Specify when follow-up starts and stops

For each proposed message, agree on its trigger, audience, timing, wording and stopping rule. Start with one website-enquiry path and one responsible staff member. An acknowledgement and an internal task may be sufficient; confirm the permitted communication channel and included workflow scope before adding more. SMS registration, credits and other usage costs are separate where disclosed in the service scope.

Use the checks below as a proposed acceptance checklist. They are not completed test results or proof that a particular integration is supported.

  1. A new enquiry arrives. Submit a fictional enquiry through the agreed test form. Check that the correct record and stage appear, the responsible person can see it, and the next action has a due time. Record whether each step was automatic or completed by staff.
  2. The person replies. Reply to the test follow-up before its next scheduled message. Check that the remaining enquiry-chasing messages stop and a person takes over. Repeat with a reply received outside that sequence, such as a staff-handled call. Specify who updates the record when the system cannot detect the conversation.
  3. An appointment is booked. Complete a test booking in the agreed calendar, then check that the enquiry-chasing sequence stops. An availability question or a clicked booking link is not a confirmed appointment. Test staff-created bookings too if they are part of the process. Keep any separately agreed appointment reminders distinct from sales follow-up.
  4. The person opts out. Use the agreed unsubscribe method or record a request to stop. Check the relevant channel preference and any pending follow-ups. Staff need a way to record requests received in conversation as well. Do not restart follow-up simply because the contact is imported again or its stage changes.
  5. Something needs review. Try a duplicate submission, an incomplete enquiry and a cancelled booking. Check that staff can identify what happened and decide the next action without duplicate chasing or an unsupported booking promise.

A setting name alone is not an acceptance test. For example, HighLevel’s Stop on Response setting applies to a response to a message from that specific workflow. Booking events and opt-outs need their own agreed handling. Its documentation separately describes appointment-status triggers, removal from selected workflows and channel-specific Do Not Disturb settings. Those product features do not establish that a Spireo setup or an external booking connection has passed these checks.

For every test, keep the input, expected result, observed result, time and evidence together. Check the record and scheduled actions, and observe what happens when the next message would have been due. Mark untested items as untested. Agree on a staff fallback and resolve failures before activation. Use synthetic data and only approved test inboxes, numbers and calendars.

Keep a human responsible for exceptions

Assign a person to review incomplete enquiries, conflicting information, requests outside the normal service and situations the workflow cannot resolve. Automation should leave that person with enough context to decide what happens next.

For a cleaning company, a request outside the usual service area might need a manual decision before any appointment is offered. For a home-service company, a callback request might need staff review before a job is scheduled. These examples describe decisions to scope, not verified customer implementations.

Check scope before importing contacts

Spireo’s listed CRM Essentials scope includes one pipeline, one form, one calendar, up to three standard workflows and a clean import of up to 500 contacts. It also has email-send and service-work limits. More workflows, larger imports or external integrations need the appropriate scope review.

Prepare a small test set before a full import. Check field mapping, duplicates and which records are eligible for the intended messages. Keeping a contact in a database does not by itself establish permission for a campaign.

Questions buyers ask

Should I replace my dispatch or accounting software?

Start by identifying the problem you want the CRM to solve. Spireo’s listed CRM setup does not automatically replace field-service dispatch or accounting software. Confirm any required integration in writing.

Can phone enquiries enter the same process?

That is a useful requirement to discuss. Spireo’s AI phone Growth scope lists a simple CRM handoff. Confirm the fields, destination and next action for your particular setup.

How many workflows do I need?

List the distinct triggers and outcomes first. Ask the provider how those requirements map to its workflow allowance. Adding more automation is useful only when it solves a defined step in your process.

How will I know the setup is working?

Use the reply, booking and opt-out checks above, record the observed results and resolve failures before activation. Review real enquiries after activation and request changes within the agreed service scope.

Bring your process to a fit review

Write down your lead sources, pipeline stages, responsible staff, message rules and existing tools. Then compare Spireo’s CRM service scope and use the service planner to prepare for a fit review. Final scope and integration feasibility need confirmation before payment or activation.