Remind the team to give a reason for a lost enquiry.

Overview

You can’t fix a leak you never wrote down. This template turns every lost lead with no reason into a small task for the person who owned it, so price, timing and “went elsewhere” end up on the record rather than in someone’s head.

Prerequisites

These are the pieces we suggest having ready before you switch this workflow on. Your clinic may set things up differently, so treat the list as a guide.

• A Leads pipeline that includes:
  • Lost stage for closed enquiries
  • Lost reason field with your usual answers

How to use this template

Once it opens, you’ll see the blocks joined up in order.

1. The Lead lost trigger is the first step. A run starts when anyone marks a lead as lost, on the pipeline board or on the record itself. Check that it points at the right pipeline and the right stage if you run more than one, for instance a separate pipeline for each of your locations.
2. The Condition block looks at the lost reason field and carries on only if it’s empty. Plenty of people fill it in as they close the lead, and those runs stop here, so nobody gets a task they don’t need. Keep the answers in that field short and fixed, so the report can count them later on.
3. The Delay block gives the owner a day to come back to it by themselves. Change the wait to suit your clinic, though a reason gets vaguer the longer it’s left.
4. The second Condition block reads the field again. It uses the latest value on the record, so a reason added during the wait ends the run and the owner hears nothing further about it.
5. The Create task block asks for the reason. Assign it to the lead’s owner, set it due the same day, and link it to the lead, so one click takes them to the field they need to fill in.