Automations That Fire When a Deal Moves

Most pipelines are used as a record of what happened rather than a mechanism that makes things happen. That is a waste, because a stage change is the highest-quality signal in a CRM: unlike an incoming message or a date passing, it means a person looked at a situation and formed a judgement — which only holds if the stages mean something, as designing pipeline stages that match how you sell sets out. Our guide to pipelines, stages and the deals you are actually going to close treats that moment as the best trigger you have.

What is worth firing

• Moving to Quoted sends the quote itself, or a message telling the customer it is on its way and when to expect it.
• Moving to Quoted also starts a follow-up sequence — a nudge after three days, another after a week, then stop.
• Moving to Committed sends the confirmation, requests the deposit and books the work into the calendar.
• Moving to Won notifies whoever fulfils it and starts the onboarding or delivery sequence.
• Moving to Lost stops every active sequence for that contact, which is the one nobody remembers to build.

That last item prevents the single most damaging automation failure: a customer who has already said no continuing to receive cheerful nudges for a fortnight.

The follow-up sequence is the one that pays

Most quotes are not lost to a competitor; they are lost to silence. The customer meant to reply, got busy, and the moment passed. Two well-timed messages recover a meaningful share of those, and they cost nothing to send.

Keep it short and specific. "Just checking whether the Thursday slot still works for you" gets a reply; "following up on my previous message" does not. And cap the sequence at two or three attempts — beyond that you are not following up, you are pestering, and the customer's silence is itself an answer.

“

Most quotes are lost to silence, not to a competitor. Two messages recover more of them than any discount.

— be digital ai team

Use wait-for-reply, not fixed delays

A plain delay sends the next message whether or not the customer has already answered, which is how people end up receiving a nudge ten minutes after they replied. A wait-for-reply step listens: if they respond, the sequence follows one path; if a timeout passes in silence, it follows another.

This is what makes automated follow-up feel like a person rather than a machine, and it is worth building properly the first time. The general mechanics are covered in from manual tasks to workflows.

Not everything should message the customer

Some of the most useful stage automations are internal. A high-value deal reaching Quoted can notify the owner. A deal sitting in one stage for two weeks can flag itself for review, which is most of the work in cleaning a pipeline that has gone stale done automatically. A deal moving backwards — from Committed back to Quoted — should almost always get a human's attention, because it usually means something went wrong that nobody has written down.

Internal automations carry none of the reputational risk of customer-facing ones and are therefore a good place to start while you build confidence in the setup.

The ones that annoy people

Three patterns reliably irritate customers. Messages triggered by a stage change the customer cannot perceive — they get a notification because someone tidied the board. Sequences that continue after the customer has answered. And multiple automations firing at once, so a single stage move produces three messages in a minute.

Before switching anything on, ask what the customer sees, in order, if everything fires. If the answer is more than two messages, something needs to be removed or delayed. The audience-level version of this problem — several campaigns hitting the same person — is covered in segmenting your audience for better WhatsApp campaigns.

Build one, watch it, then build the next

Start with the quote follow-up, because it is the one with the clearest return, and watch it for two weeks with the run log open. You will find at least one case you did not anticipate — a deal moved to Quoted by mistake, a customer who replied by phone so the sequence never stopped — and fixing those before adding the next automation is how you end up with a system your team trusts rather than one they quietly work around. Three well-tested automations do more for a small business than a dozen half-watched ones.