The short answer
A good enquiry pipeline is a short set of stages that every enquiry passes through, such as new, contacted, quoted, booked, then won or lost. Each stage has one owner, a clear next action and a time limit. Workflows do the remembering: they create the record, send the acknowledgement, set the task and prompt someone when nothing has happened.
We build these as part of our CRM automation service, so this comes from doing the work. The examples below are patterns for a service business, not a template to copy line for line.
How to read each example
A CRM (customer relationship management system) is the one place where enquiries, contacts and their history are kept. A workflow is a rule inside it: when this happens, do these things. Each example here has four parts.
- Trigger: the event that starts it.
- Steps: what the system does, in order.
- Owner: the one person responsible for the outcome.
- Human control: the point where a person decides, not the system.
If you are still deciding whether you need a CRM at all, read CRM vs spreadsheet first.
The seven workflows at a glance
| Workflow | Trigger | Owner | Where a person decides |
|---|---|---|---|
| New enquiry intake | Form, email or call logged | Enquiry handler | The first real reply |
| Quote follow-up | Quote marked as sent | The person who quoted | Whether and how to chase |
| Missed call | Unanswered call | Whoever covers the phones | The call back |
| Appointment reminder | Appointment booked | The person attending | Rearranging |
| Won job handover | Enquiry marked won | Delivery lead | Accepting the handover |
| Lost reason | Enquiry marked lost | The person who owned it | Choosing the reason |
| Review request | Job marked complete | Whoever managed the job | Pausing for a complaint |
From first contact to quote
New enquiry intake
Trigger: a website form is submitted, or an email or call is logged. Steps: the CRM creates or updates the contact, records the source and the service asked about, sends a short acknowledgement saying when to expect a reply, and gives the owner a task with a deadline. If the task is not done in time, a manager is alerted. Human control: the acknowledgement is automatic, but the real reply is written by a person. All of this depends on the form feeding the CRM directly, which is the subject of connecting your website, CRM and sales process.
Missed call
Trigger: a call goes unanswered in working hours. Steps: the phone system passes the number to the CRM, which creates a call-back task and can send a short text saying you will ring back. Owner: whoever covers the phones that day. Human control: a person makes the call. The text is a holding message, not a replacement for speaking to someone.
Quote sent and follow-up
Trigger: the enquiry is moved to quoted. Steps: the CRM records the quote date and value, sets a follow-up task a few days later and, if it suits your customers, sends one polite check-in. Any second reminder goes to the owner, not the customer. Human control: the owner decides whether to call, email or leave it, because they know the conversation. Our guide on how to automate lead follow-up covers timing and wording.

From booking to finished job
Booked appointment and reminder
Trigger: a survey, visit or call is booked. Steps: a confirmation goes out with the date, time, address and who is coming. A reminder follows the day before, with a simple way to rearrange. Human control: a request to rearrange goes to a person, who agrees the new time. A missed appointment creates a task for the owner.
Won job handover
Trigger: the enquiry is marked won. Steps: the CRM checks that the required fields are filled in (scope, price agreed, address, access notes, promised dates), creates the job record, notifies the delivery lead and sends the customer a short message on what happens next. Human control: the delivery lead accepts the handover or sends it back with questions. Nothing promised during the sale should live only in someone's head.
After the outcome
Lost enquiry reason
Trigger: the enquiry is marked lost. Steps: the CRM requires a reason from a short fixed list, such as price, timing, went elsewhere, no response or not a fit. All open tasks and messages for that enquiry stop. Human control: the owner picks the reason and decides whether a check-in later in the year would be welcome. Reviewed each month, the reasons show where enquiries are being lost.
Review request after completion
Trigger: the job is marked complete and any snags are closed. Steps: after a short delay the customer receives a thank-you and a request for a review, with one reminder at most. Owner: the person who managed the job. Human control: the owner can pause the request while a complaint is open, and resolves that first. Do not ask only the customers you expect to be happy, never offer a reward for a positive review, and check the rules of the review platform you use.
The principles behind them
One owner per stage
Every stage has one named person. 'The office' is not an owner. When two people share a stage, each assumes the other has it.
Stop the sequence when someone replies
Any reply, call or booking from the customer should end the automatic messages for that enquiry straight away. A chasing email that arrives an hour after the customer said yes makes the business look careless.
Handle failures
Messages bounce, forms break and connections between systems drop. Each workflow needs a fallback: an alert to a person when a step fails, and a weekly look at enquiries with no next action.
Keep it simple enough to use
A pipeline with a handful of stages that everyone keeps up to date beats a detailed one that nobody trusts.
- Does every stage have one name against it?
- Does every automatic message stop when the customer responds?
- Does someone hear about it when a step fails?
Follow-up emails and texts can fall under UK rules on electronic marketing and personal data. Say who you are, make it easy to opt out and check your own situation. This is not legal advice.
Common mistakes
- Automating the first real reply so it reads as if a machine wrote it.
- Letting follow-ups continue after the customer has replied or booked.
- Leaving the lost reason as a free-text box that people skip.
- Having no alert when a form, message or connection fails.
- Building the workflows before agreeing who owns each stage.
Common questions
Which workflow should we set up first?
New enquiry intake. Until every enquiry lands in one place with an owner and a deadline, the others have nothing reliable to work from. Quote follow-up is usually second.
Will customers mind that messages are automatic?
Confirmations and reminders are expected to be automatic. Keep them short, plain and signed by a real person. Anything that needs judgement should come from a person.
Which CRM do we need?
Most established CRMs, including HubSpot and similar tools, can run workflows like these, sometimes with a connecting tool such as Zapier, Make or n8n. Choose on what your team will use every day, not on the longest feature list.
What does it cost to have this built?
Our automation work starts from £999 per workflow. The CRM software itself is a separate cost, paid to its provider.
What to do next
Write your stages on one sheet of paper, put a name against each and note where enquiries currently go quiet. That page is the brief for your first workflow.
If your enquiries start on your website, our free 24-hour audit is a sensible first step. A founder records a personal video walkthrough of your website within 24 hours, including what happens to an enquiry once the form is sent. No call is needed.
Want this applied to your website?
George or Nicholas will record a personal walkthrough of your site within 24 hours.
Not ready for an audit? See CRM automation.
