Turning an automation off stops it for your whole book. The block list is the other tool: it stops Pulse reaching one person, or one property, while everything else keeps running for everyone else.
Watch Mandric walk you through this topic
8:43The Block List Outranks Every Trigger
A blocked client is skipped no matter which automation would have reached them. This holds whether the trigger sends automatically or drafts for your review, so blocking somebody clears them out of the queue too, not just future sends. There is no separate list per trigger to keep in sync; one block covers what you told it to cover.
Block Somebody From All of Pulse
Press Block list at the top of Pulse, on any tab. Search your book and pick a client to block them from every trigger at once. This is the right call for someone who has asked not to be contacted at all, or a client you know is between properties and does not need equity, anniversary or renewal outreach right now.
Block Them From One Trigger Only
Every blocked client shows a scope you can narrow. Open the dropdown beside their name and check only the triggers that should skip them, such as birthday outreach, while leaving equity alerts or renewal reminders running. You can also block someone from a single trigger directly, from the Next Up card in the queue, without opening the settings screen at all.
Blocking One Property Rather Than the Person
A block set from a deal card only mutes that property. If the same client holds a second mortgage with you, outreach on that file keeps running untouched. The block list shows a property-scoped block as its own row, named by the address, sitting under the client's name, so you can tell at a glance which of their files is muted and which is not.
Undoing a Block
Press Remove beside a blocked client to lift it. Removing a client-wide block also clears any narrower blocks nested under it, so nothing stays muted with no visible reason once you have let someone back in. Removing a single property's block only affects that property; the rest of the client's blocks, if any, stay as they were.
What to Do Next
- Review the Pulse Queue to see what an automation would have sent before you decide to block anyone.
- Read Your Automation History to check whether a client was already reached before you blocked them.