Business process optimization, for a company that already runs on automation, is mostly about tuning what was built last year. Workflows pile up, triggers overlap, contacts receive two messages for the same event, and nobody is sure which version is live. This article answers one question: how do you audit the workflows already running in your account and cut them back to a set that is fast, consistent and owned? If you have not built anything yet, start with redesigning the process on paper instead.
Why built automation drifts
Every workflow was sensible on the day it was built. Then a campaign added a second follow-up, a new hire copied a workflow to test something and never deleted it, and a change in the sales process left an old stage-based trigger firing on a stage nobody uses. Within a year, a typical account has more workflows than processes.
Drift costs you in three ways. Contacts get duplicate or contradictory messages, which looks careless. Staff stop trusting automation and start doing steps by hand again. And every change takes longer, because no one knows what else it will affect.
Before you start
- Make sure you have permission to view and edit every workflow in Automation.
- List your real processes on one page: lead response, booking, onboarding, invoicing, review requests, and so on.
- Tell process owners that an audit is running and that some workflows will be paused for review.
- Set aside half a day for the first pass. Later passes take an hour.
The audit in five passes
The audit is a business exercise first and a platform task second. Work through the list of live workflows in this order:
- Write down every published workflow with its trigger, owner and the process it belongs to.
- Use Stats view to mark every workflow whose trigger has matched nobody in the last thirty days as a retirement candidate.
- Group the rest by shared trigger and circle any trigger that starts more than one workflow.
- For each circled trigger, merge into one branched workflow or decide which single workflow wins.
- Check the settings on every survivor, so contacts cannot enter twice or keep receiving messages after replying.
How to find workflows nobody enters with Stats view
Stats view shows, for each trigger, how many contacts were attempted, matched and unmatched over the last thirty days, and for each action how many contacts reached it. A trigger with zero matches in a month is either seasonal or dead.
- Open a workflow.
- Turn on Stats View from the top-left corner.
- Select a trigger or action to review its available statistics.
You cannot edit while Stats view is on, so switch it off before you change anything. A high unmatched count is also worth reading: it usually means the trigger's filters are too broad and another workflow is catching the contacts it was built for.
How to see what changed with History
When a workflow suddenly starts behaving differently, the cause is nearly always a recent edit. History shows the earlier versions so you can compare.
- Click the History icon in the top-right corner.
- View previous versions.
- Use the Back to Builder button to return to editing the workflow.
How to stop duplicate messages in workflow settings
Two settings cause most duplicate and unwanted messages. Allow Re-entry decides whether a contact who finished the workflow can go through it again; when it is off, each contact completes it only once. Stop on Response removes a contact from the workflow as soon as they reply to one of its messages, on any channel it uses. Appointment and invoice triggers always allow a new run for each new appointment or invoice, whatever the setting.
- Navigate to the Automation section.
- Open an existing workflow.
- Inside the workflow builder, click on the Settings tab at the top of the page.
On a welcome or nurture sequence, switch Allow Re-entry off unless you have a reason to repeat it, and switch Stop on Response on so a lead who answers is handled by a person rather than the next scheduled email. While you are in Settings, check the Time Window: messages outside it pause and resume at the next allowed slot, which is often the real reason a team thinks a workflow is "late".
What tuning gives a firm with flat revenue
Tuned automation means every enquiry gets exactly one fast, correct reply and every client gets the right message at the right stage. That consistency is what lets a 60-person company handle more clients without adding coordinators. It also restores trust, so staff stop shadowing the automation with manual follow-ups that duplicate it.
The audit replaces the usual pattern of adding a new workflow every time something goes wrong. Each addition fixes one symptom and adds one more thing that can conflict.
Imagine an audit that finds 64 published workflows covering 11 real processes. Say Stats view shows 23 with no matched contacts in thirty days. Of the rest, 9 fire on the same form submission and 4 of those send a welcome email. Merging and pausing on that basis could leave around 19 workflows. A new enquiry would then get one welcome message instead of up to four, and the operations lead could explain each live workflow in a minute. The counts are invented.
How much time it takes to keep tuned
After the first audit, set a monthly thirty-minute review. Turn on Stats view for workflows created or edited that month, and check History for anything that changed without a reason and check they follow the naming pattern, have Stop on Response set where it should be and do not share a trigger with anything else.
Deleting workflows on the first pass. A workflow that looks dead may run once a year, such as a renewal reminder. Pause first, wait thirty days, and only then delete.
When not to tune
If the underlying process is wrong, tuning the automation polishes the wrong thing. If staff complain that the process itself makes no sense, go back to the design and read business process automation software first, which deals with designing for exceptions.
Signs your workflows need an audit
You need an audit if a contact has ever complained about duplicate messages, if staff ask "is this automated?" and nobody knows, or if a simple change to a stage name breaks something unrelated. Our list of workflow automation examples shows what a clean set of workflows looks like for a services firm. For the visual builder itself, see the visual workflow designer guide. And if you are rebuilding a large part of the set, the workflow process automation article covers structure.
Troubleshooting
A paused workflow turns out to be essential
Someone will tell you within days. Republish it, rename it to the standard pattern, record its owner, and add it to the process list so it is not mistaken for dead again.
Contacts still get two messages
A trigger outside Automation is sending one of them, such as a form's own confirmation or a calendar's booking notice. Check the form and calendar settings and switch off whichever duplicates the workflow.
Merged workflows are too long to read
Split by stage, not by channel. One workflow per stage of the process, each handing off to the next, is easier to follow than one workflow covering everything.
A contact goes through the same sequence twice
Allow Re-entry is on, or two workflows share the trigger. Switch the setting off in the Settings tab and check Stats view on the other workflows for the same trigger.
Stats look lower than expected
Trigger stats cover the last thirty days only. A yearly renewal workflow can show zero and still be essential, which is why you pause before you delete.
Frequently asked questions
How many workflows should a company of our size have?
There is no right number, but you should be able to map every live workflow to a named process. If you cannot, you have too many.
Should we audit before adding new automation?
Yes. Adding to an untidy account multiplies the conflicts. A short audit first makes the new work faster.
Who should own the audit?
The person who owns operations or process improvement. Department heads should review their own workflows, but one person needs to see the whole set.
What is the quickest exit condition to add?
Stop on Response in the workflow's Settings tab. It removes a contact the moment they reply, so a person can take over. Booking and paying need their own goal or branch inside the workflow. For more on building those, see the workflow creator guide.