Data-driven flowchart template (customer churn-risk review)
A data-driven flowchart template: a customer churn-risk review whose branches are settled by numbers, with an intervention threshold, a commercial-or-product driver split and a measured recovery threshold.
How it works
Put your own number on the intervention threshold
Read it from the score at which your own historical churn rate rises sharply, then trim it until the queue is a week of real capacity. Write the value and the date it was last recalibrated onto the decision step. Order the queue by renewal date and contract value as well as by score, or a week's capacity goes to accounts that are at risk but not up for renewal for eight months.
Fix the cadence and name the sources
Rewrite the first step to list the sources you actually have — usage events, ticket reopen rate, invoice history, renewal date — and state the cadence. Weekly is the common choice. If yours is monthly, both thresholds have to move, because a monthly window absorbs the drop that a weekly one would have caught in time to act on it.
Rename the lanes to your teams
Replace Data and analytics, Customer success, Account manager and Product with whichever four functions a score actually passes through in your company. If one person does both the outreach and the renewal, merge those two lanes but keep the escalation decision, because it is a different judgement. If support owns the ticket signals, give support its own lane instead of hiding the handoff inside analytics.
Define recovery before you need it
Set the recovery threshold and the post-intervention window while nothing is at stake. Four to six weeks suits most subscription products, and the movement that counts should be sustained — two consecutive refreshes below the intervention threshold, not one good week. Agreeing this in advance is what stops the recovery test being negotiated by whoever ran the intervention.
Write down your driver routing rules
List which ranked drivers route commercially (seat reductions, failed payments, discount expiry, a sponsor change) and which route to product (falling feature use, error rates, unresolved tickets). If your product team does not act on churn signals, do not delete that branch: point it at a single step that logs the feature and continues, so the reason is still captured rather than recorded as commercial.
Cap the second attempt
The recoverable branch loops back to the customer conversation, which is honest but can run forever. Set the days-to-renewal figure that makes a second attempt worth funding, cap the loop at one repeat, and require the intervention to be different from the first. If you sell on rolling monthly terms, replace the renewal-date test with whatever deadline actually exists.
Frequently asked questions
What is a data-driven flowchart?
It is a flowchart whose structure is held as data rather than as drawn objects. Each step is a row, a column records which row it leads to, and a decision's branches carry the condition attached to each outcome. The diagram is generated from those rows, so editing the table edits the picture. The practical difference from a hand-drawn chart is not appearance but truth over time: a drawn diagram is accurate on the day someone drew it, while a generated one is accurate whenever the rows are. That matters most where branches turn on figures, because figures get revised and drawings do not.
What are the stages of a churn-risk review?
Five, and this chart uses them as its phases. Signal is the scheduled refresh and scoring run. Review is the triage that checks the model's drivers against what the account record actually says, and decides whether the leading cause is commercial or product-related. Contact is the conversation where an action plan is agreed with the customer. Action is delivery of whatever was agreed. Outcome is the measurement window afterwards, which either confirms re-engagement or sends the account to a recoverability judgement before renewal. The stages matter because each one has a different owner, and most churn processes fail in the gaps between them rather than inside them.
Who owns a churn-risk process?
It is split, which is why the chart has four lanes. Analytics owns the model, the refresh and the score. Customer success owns the queue, the triage and the customer conversation. The account manager owns the commercial position and the escalation before renewal. Product owns the churn reason logged at the end and whatever it changes as a result. The one thing that has to be owned jointly is the intervention threshold, because it sets both the analytics team's queue length and the customer success team's workload. In practice a named end-to-end owner, usually customer success, is what keeps the handoffs from stalling.
Can a flowchart stay in sync with the data it was built from?
It can, and in Visio it depends which mechanism you used. The Data Visualizer templates in the Visio desktop app, which Microsoft documents as Visio Plan 2 only, keep a two-way link to an Excel table: Refresh Diagram pulls workbook changes into the diagram, and Update Source Data writes diagram changes back. One caveat Microsoft states plainly is that formulas in the source workbook do not survive that write-back, because Visio converts a formula to its result — which bites on a chart like this one, where a threshold is usually the output of a calculation rather than a typed number. The separate Link Data to Shapes route runs one way only — Microsoft's wording is "You cannot update the data source to which a Visio diagram is linked by making changes in the Visio diagram" — and it draws no connectors at all, so it populates shapes without building the flow between them. Here the question does not arise, because the rows are the diagram.