AI & customer systems
Map the workflow before you connect the tools
Use a one-page process map to expose missing owners, unclear rules and handoff gaps before building an automation.
By Bridge Builder editorial 3 min read
A workflow map is a plain description of how work moves from a request to a finished result. You do not need diagramming software to make one. A document with numbered steps is enough to find problems before they become automated problems.
Start with the process the team actually follows. The version in the owner’s head may skip the texts, corrections and judgment calls that make the work happen.
In this article
Trace one ordinary request
Choose a recent example without copying private customer information into a planning document. Follow it from the first contact through completion. For an estimate request, that might be website inquiry, office review, qualification, appointment, estimate and decision. Record where each step happens and who moves it forward.
Beside each step, write the evidence of completion. “Sales handled it” is ambiguous. “A named person recorded the next appointment or a reason to close the inquiry” is something another teammate can verify. These definitions will become the checks for the eventual automation.
Separate the rule from the judgment
Some decisions are mechanical: a required field is empty, an existing record matches or a date has passed. Other decisions depend on context, such as whether an unusual job is a good fit. Mark those differently rather than assuming an AI model should make every choice.
For example, a pool service might automatically flag requests outside its written service area. A staff member should handle a request near the boundary when access, travel or existing routes change the decision. Put that exception in the map instead of burying it in a conversation.
Draw the paths that do not succeed
The ordinary route is only part of the process. What happens when the customer gives an incomplete address, the assigned person is absent or the destination system is unavailable? Decide where these requests wait and how someone notices them.
A useful map makes waiting visible. “Needs information” and “Needs staff review” can be legitimate states if someone owns them. An invisible failed step is more dangerous than a visible task that takes a day to resolve.
- Missing information: who requests it?
- Duplicate request: which record stays active?
- Failed connection: where is the unfinished work listed?
- No response: when does a person decide the next step?
Walk the map with the team
Ask a teammate to explain how they would handle three sample requests using only the document. Include an ordinary request, an exception and a failure. Whenever they need information that is not written down, add the missing rule or identify the decision owner.
Finish with a bounded first version. It is reasonable to automate intake and assignment while leaving estimates manual. Save the map with the workflow and update it when the process changes. The map should describe what the system does today, not what you hope to build later.
Your next step
A useful process map shows who acts, what proves completion and where unfinished work goes.