From first enquiry to booked appointment: the workflow, step by step

Between someone deciding to contact you and an appointment appearing in your calendar there are usually five or six steps. Most enquiries that get lost fall through the gaps between those steps, not inside them. This guide lays out the workflow, marks where it breaks, and ends with a checklist for the moment a person takes over.

The workflow at a glance

Stage by stage

1. Arrive

Enquiries come in through several doors at once. Before automating anything, list them all: main phone line, mobile, website form, booking widget, social messages, email. A workflow that covers three doors but not the fourth trains customers to use the fourth, and those enquiries go quiet.

2. Acknowledge

The first reply has one job: confirm the message arrived and say what happens next. Include your business name so the customer recognises you, and avoid promising an exact callback time you cannot keep. If the first reply is a text, check how the rules on commercial electronic messages apply to it; in Canada that is CASL, which covers text messages.

3. Qualify

Ask the questions your team asks every time, one at a time, in plain words. Three to five questions is plenty. Only ask for what you will use: Canadian privacy principles include limiting collection to what you need for the purpose you have identified.

4. Decide

This is where most automations overreach. Turn your rules into a short list the system can apply: services you offer, postcodes or towns you cover, jobs you never take. Anything outside the list goes to a person rather than receiving a guessed answer.

5. Book

Offer two or three real openings, not a link to a full calendar, and confirm the chosen time back in writing with the address and what to expect. Build in the buffers your crews actually need, such as travel time between jobs.

6. Record and hand over

Update the contact record with what was collected, add the appointment, and notify the person who will do the job or make the call. The guide on connecting AI conversations to a CRM covers the record-keeping side in detail.

Failure states to plan for

Every stage can fail. Decide in advance what the system does in each case, because "nothing" is the default.

Handoff checklist

When a person takes over, they should have everything needed to continue without asking the customer to repeat themselves:

• Name and the best way to reach them, with the channel they used.
• A two- or three-line summary of what they want, in plain words.
• The answers already collected, and which questions are still open.
• Why the handover happened: rule triggered, unclear answer, customer request or urgency.
• What the customer was told would happen next, and by when.
• A link to the full conversation or call recording, where recording was disclosed.
• A named owner and a due time, visible to the rest of the team.
• Automation paused on that conversation, so the system does not reply over the person.

Measuring whether it works

Pick two or three numbers you can pull from your own records and compare four weeks before and after: time from enquiry to first reply, share of enquiries that reach a booking, and how many handovers were picked up by their due time. Read a sample of conversations each week as well. The numbers tell you whether something changed; the conversations tell you why.

Limits

• This is a general pattern. Emergency trades, clinics and regulated services need their own rules for urgency and records, which this guide does not cover.
• Booking automatically only works when your calendar reflects reality. If crews keep their real schedule elsewhere, fix that first.
• Consent and privacy rules differ by province and state. Treat the references here as pointers, not legal advice.