Global options: stop on agent reply and once per contact
Configure the two trigger settings that stop a workflow from repeating per contact and hand off to a human when the agent replies.
Watch this step in the video · Stop when an agent replies, and trigger variables
What they are and why they matter
In a workflow editor, when you select the trigger (the start node), two settings appear that change how the whole automation behaves, not just one node:
- Run only once per contact — stops the same contact from re-entering the workflow.
- Stop this workflow when the agent replies (under the Behavior section) — hands control to a human as soon as they respond.
Set correctly, these are the difference between a helpful automation and one that spams customers or talks over your agents.
Run only once per contact
When enabled, after the first run for a contact, subsequent matching events for that contact are skipped. The workflow won't fire again for that person even if they meet the condition once more.
When to use it:
- A welcome message that should only send once.
- A survey or a "first contact" coupon.
- Any onboarding sequence you don't want to repeat.
When not to use it: recurring reminders, support replies, or any flow that should react every time.
This setting only appears on triggers that support it. If you don't see it, that event type can't be limited per contact.
Steps
- Open the workflow and click the trigger.
- Tick Run only once per contact.
- Save.
Stop this workflow when the agent replies
This is off by default. With it off, the workflow keeps running even when an agent types; to cut it manually, the agent must click Stop workflow in the chat.
If you turn it on, a single message from the agent in that conversation interrupts the workflow and the human takes over.
When to turn it on:
- Follow-up or nurturing sequences where, if an agent is already talking to the customer, the automated messages are redundant.
- Bot flows that should "step aside" the moment a person joins.
Steps
- Open the workflow and click the trigger.
- In the Behavior section, enable Stop this workflow when the agent replies.
- Save.
Verify
- For "once per contact": fire the event twice with the same contact and confirm the second run is skipped.
- For "stop on reply": start the flow, reply as an agent, and check that the following automated steps don't run.
If it doesn't work
- "Run only once per contact" isn't shown: the chosen trigger doesn't support it; switch triggers or restructure the flow.
- The workflow keeps sending after I replied: confirm Stop... when the agent replies is enabled and saved; remember that, when off, you must click Stop workflow manually.
- It repeats for the same contact: make sure the checkbox stayed ticked before you saved.
Tips
- Combine both in welcome flows: once per contact + hand off to the agent = a clean experience.
- These settings are per workflow; if you duplicate the automation, re-check them in the copy.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.