Choose an example by its decision structure, not its colors. An approval process needs a return loop, order handling needs terminal success and cancellation paths, and support escalation needs a handoff when the first owner cannot resolve the request.
Approval with revision
The illustrated campaign flow begins with a brief and asset creation. Brand review can approve the work or request changes. Requested changes go to revision, then back to asset work and review. Approved work moves through scheduling and launch to measurement.
This is useful when rework is expected. It makes the difference between “try again” and “finish” visible. See the full approval workflow for a closer reading of the loop.
Order handling with cancellation
An order flow adds conditions that can end the process. Out-of-stock items might become a backorder if the customer accepts the delay. A failed payment might be retried or canceled. These branches should not quietly merge into fulfillment before their conditions are satisfied.
Use separate end states for shipped and canceled orders. If you track refunds, describe whether payment was captured before cancellation; the agent should not invent that rule.
Support escalation with a new owner
A support flow starts with issue classification and an initial response. If the first team cannot resolve it, the request moves to the appropriate specialist. The customer should still receive an outcome, so show what returns after escalation.
Use a swimlane diagram when the changing owner is as important as the decision. Use the flowchart generator for a compact view of the logic.
Make it about your work
Edit this starting prompt, then send it when you are ready.