Automations
Step criteria that route a lead by its data, tag rules that pause, move or remove a lead, duplicate detection, handing a returning person to the right flow, and the flow's messaging switches when you use FoxFlow Messaging.
Flow Settings → Automations holds the rules that fire on their own when something happens to a lead.
Step Criteria
A step criterion watches a lead while it sits in a step you choose. When every condition is true, FoxFlow moves it to a step on this flow or another flow in the same organisation.
| Setting | What it means |
|---|---|
| When a lead is in step | The column that is checked |
| Match all of | iMessage, a phone number, an email, the email agent's Approved or Sent mark, or a form answer. Every condition you add has to be true |
| To flow | Where to move it. This flow, or another flow in the organisation |
| Into step | The column it lands in |
| Also remove this person from all other flows after the move | Cleans up duplicates elsewhere |
Rules on the same step run from top to bottom. The first one that matches moves the lead. A second rule is how you say "or".
An iMessage condition waits until the number is confirmed as iMessage or not. A form answer that was never captured waits too, so a blank lead is not treated as "not Location A". Phone and email are read from the lead, including answers that arrived on a Meta, FlowForm, or public form.
Leads already sitting in the column stay there when you save the rule. Sort Leads Already Here moves the ones that already match. It checks up to 500 leads per click. The next click continues where this one stopped. Editing a rule starts the sort over.
Leave auto-send off on a step whose only job is to sort. That step can still text in the moment before a move.
Tag Rules
A tag rule watches for a lead gaining a tag and then does one thing:
| Setting | What it means |
|---|---|
| When a lead gains tag | The tag to watch for |
| Do this | Pause automation, move the lead, or remove it from the flow |
| To flow | Where to move it. Blank means this flow |
| Into step | Which column. Blank means the first step |
| Also remove this person from all other flows after the move | Cleans up duplicates elsewhere |
The three actions in plain terms:
- Pause automation — the lead stays where it is, but no more automatic texts or timers. Use this as your emergency brake.
- Move lead — send it to a flow and step of your choosing.
- Remove from flow — take it off this board entirely.
Tags can come from a person tagging by hand, from tags on entry on a step, or from an integration like Blackbaud that tags people it recognises.
Duplicate Detection
On by default, and worth leaving on.
When the same person comes in twice — they filled out a form in March and again in September, or they answered two of your Facebook ads — FoxFlow notices and pauses the duplicate with a warning instead of letting it run.
The duplicate is never dropped. You still see the person and can decide what to do. What doesn't happen is a second automated sequence landing on someone who's already in a conversation with you.
Context Handoff
Related to duplicates, but a decision rather than a pause. With context handoff on, a person who's already known gets redirected into a different flow and step that you pick.
That's the difference between "stop, a human should look at this" and "we know exactly where returning people should go."
There's an option to remove the person from all other flows after the redirect, so they exist in exactly one place.
Remove from Other Flows on Move
A tidiness setting. When a lead moves into this flow — by handoff, by a step timer, by a tag rule — this also removes them from every other flow.
Turn it on when a person should only ever be on one board at a time. Leave it off when your flows track genuinely separate things and someone can legitimately be in two.
Keep Same Assignee on Auto-Move
On unless you turn it off. When a lead moves to another flow on its own — a step timer, a tag rule, or move on reply — FoxFlow keeps them with the same teammate if that person is also on the destination flow's team. If they aren't, the destination flow assigns the lead the way it normally would.
Leave it on when the same person should stay with the family. Turn it off when the receiving flow should pick someone itself.
Messaging
Three more cards appear on this tab only when your organisation uses FoxFlow Messaging. They are the flow-level half of texting. Per-step scripts and timers stay on Steps. Numbers, the sending window, and the daily cap stay in Organisation Settings → Messaging.
- Auto-Send Scripts — the master switch. A step still has to opt in. Turning it on does not text leads already sitting in a column.
- Move on Reply — when a lead replies, move them to a flow and step you choose.
- Assignee SMS Alerts — text the assignee when they get a new lead or when their lead replies. The teammate needs a phone number on their profile, and org-level alerts have to be on too.
Which one do you want?
| You want | Use |
|---|---|
| Route by iMessage, phone, email, agent email, or a form answer | Step criteria |
| Stop everything for one lead | Tag rule → pause automation |
| Route people carrying a tag somewhere specific | Tag rule → move lead |
| Get someone off a board | Tag rule → remove from flow |
| Not re-sequence people who came back | Duplicate detection (already on) |
| Send returning people somewhere on purpose | Context handoff |
| Guarantee one board per person | Remove from other flows on move |
| Keep a handed-off lead with the same teammate | Keep same assignee on auto-move |
| Text a step's script without pressing send | Auto-send (FoxFlow Messaging) |
| Move a lead the moment they reply | Move on reply (FoxFlow Messaging) |
Next: Contacts.