Stop tag
Automation mechanicsAlso called: exit tag, kill tag, suppression tag
A stop tag is a tag that cancels a contact's active runs in an automation as soon as it is applied — the emergency brake that stops a sequence for someone who has unsubscribed, complained, bought, or otherwise stopped being the right audience.
Stop tags exist because the alternative is editing every sequence whenever a new reason to stop appears. One tag named unsubscribed, honoured across every automation, is a policy you can actually keep.
They are also the cleanest way to give sales a lever. A rep who tags a contact as in-conversation should be able to silence the marketing sequence immediately, without filing a ticket or knowing which flows the contact is in.
The discipline they require is naming. Stop tags are matched by name, so a tag applied as Unsubscribed and configured as unsubscribed is a bug waiting for its first complaint — pick one casing convention and keep it.
How it works in FrazzleCRM
- ✓Stop tags are an automation setting, listed per automation, and they cancel active runs rather than merely blocking new entries.
- ✓The unsubscribe link is a system trigger link with its own protected behaviour, so honouring opt-outs does not depend on remembering to build it.
- ✓The cross-automation audit flags a self-cancelling stop tag — a flow that adds a tag which is also one of its own stop tags, so the run kills itself at the next step.
- ✓Because they are tags, anything that can apply a tag can stop a sequence: a step, a rep, an import, a webhook.
Where teams get this wrong
A flow that adds its own stop tag terminates every run at the next step, quietly and completely. It looks exactly like a sequence with a broken sending credential, and it is the first thing worth checking when a sequence stops mid-flight for everyone at once.
Common questions
What is the difference between a stop tag and unsubscribing?
Unsubscribing is the contact's choice and should suppress all marketing sending. A stop tag is your control — it can encode unsubscribes, but also purchased, in-conversation or bad-fit.
Does a stop tag remove the contact from the CRM?
No. It cancels their runs. The contact, their history and their tags all remain.
See it on a real map
Free templates where this shows up as an actual node. Clone one and the diagram runs as the automation.
Win-Back / Re-Engagement
Wake up dormant contacts with a miss-you note, an offer, and a clean breakup.
E-commerceAbandoned Cart Recovery
A 3-email rescue sequence with escalating urgency and a discount closer.
SaaSFailed Payment Dunning
Recover the churn nobody chose — three retries, one text, and a dated deadline.
Related terms
Tag
A tag is a simple label attached to a contact that records a fact about them — a source, an interest, a state — and which automations can react to, branch on, and use as an exit condition.
Goal
A goal is a step that represents the outcome an automation is trying to produce. Contacts anywhere upstream jump straight to it the moment the goal's event happens, skipping whatever remained in between.
Enrollment
Enrollment is a single contact's active run through one automation. Each enrollment holds its own position in the flow, its own timers and its own state, which is why two contacts in the same sequence can be at completely different steps.
Do Not Disturb (DND)
Do Not Disturb is a per-contact, per-channel mute that suppresses outbound email, SMS or calls to that contact without deleting them or removing them from your CRM.
Or browse all 24 terms — grouped by what part of the funnel they belong to.
Draw it once, and it runs
In FrazzleCRM the funnel map IS the automation — every node you draw is a real step, and every step you edit redraws the map. Free plan, no credit card.
Start free