Most client retention strategies fail for a simple reason: the firm learns a client is unhappy when the cancellation arrives. This article answers how to find out earlier. The method is a three-question check-in survey sent after the moments that shape a client's view of you, with the answers routed automatically on the levelpartner.ai platform: a low score becomes a task for the account owner within the hour, and a high score becomes a thank-you with a referral ask. It all runs from one workflow built on the Survey Submitted trigger with an If/Else branch.
Why the cancellation is the first signal most firms get
In a 60-person firm, a client's view of you forms in a handful of moments: the first month of delivery, the first report, a missed deadline, a change of account manager, the run-up to renewal. Most firms ask nothing at those moments. They ask once a year, in a long satisfaction survey nobody senior reads, or not at all.
By the time a client says they are leaving, the decision is usually weeks old. They have spoken to a competitor, briefed their finance team and stopped raising problems because they no longer expect them to be fixed. A retention conversation at that point is a negotiation on price, from a weak position.
A short check-in at each milestone moves the signal forward by months. A score of five out of ten after the first report is a problem you can fix in a phone call. The same dissatisfaction found at renewal is a lost account.
Retention strategies for clients built on milestones
Pick three to five milestones that every client passes. For most service firms the list looks like this.
- Thirty days after onboarding, when first impressions have formed.
- After the first major deliverable or report.
- Within a week of a change of account manager.
- Ninety days before renewal, while there is still time to act.
Each check-in asks the same three questions, so scores can be compared over time: how likely are you to recommend us, on a scale of nought to ten; what is one thing we should change; and may we contact you about your answer. Three questions take a client under a minute. A ten-question form takes several, and fewer people finish it with every question you add.
Suppose the firm sends a check-in at day 30, after the first quarterly report and 90 days before renewal: roughly 140 surveys a year. If about four in ten come back, that is around 56 answers. Say 9 of them score six or lower. Each one would be a same-day task, and the call might find something fixable: a report the client's board cannot read, a contact who left, a deadline the client thought was agreed. Nine early calls a year is a small cost against even one renewal saved.
Before you start
- A survey built under Sites with the three questions, where the score question writes its answer to a contact field.
- A tag or field that marks each client's account owner, so tasks land with the right person.
- A short thank-you message with a referral ask, for clients who score high.
- A decision on the threshold: six or lower is a typical cut-off for an owner call.
How to route answers with the Survey Submitted trigger
The trigger starts the workflow whenever a client submits the survey. It does not read individual answers itself, which is why the score must be saved to a contact field, and why the If/Else action does the routing.
- In the workflow builder, choose Survey Submitted from the list of triggers.
- Enter a clear name in the Workflow Trigger Name field, such as "Client check-in submitted".
- Set the filters: Disqualified set to is false, and Survey is set to your client check-in survey.
Then add the routing.
- Click the + icon below the trigger and add the If / Else action.
- Choose Build My Own.
- In the first branch, pick the score field, choose the operator for "less than or equal to" and enter your threshold.
- Click Add Branch for the high scores, using the same field with nine or above.
- Rename the None branch "Middle scores" and give it its own actions.
- Save and publish the workflow.
On the low branch, add a task for the account owner due the same day and an internal notification, with the client's comment in the task description. On the high branch, send a thank-you and ask whether they know anyone who needs the same help. On the middle branch, send a thank-you and log the score; a seven or eight is a client who is content, not one who will advocate for you.
What the owner does with a low score
The task is only useful if the call happens quickly and goes a particular way. Call within one working day. Thank them for the answer, read their comment back to them and ask one question: what would need to change for this to be a nine? Then agree one action with a date and write it on the record.
Do not offer a discount on the call. A client who scored you low on service has not asked for a lower price, and offering one tells them the problem will not be fixed. Fix the thing they named.
Putting the public review request on the high branch. Asking only the clients who scored you well is review gating, and Google's review policy forbids selectively soliciting positive reviews. Ask every client for a review at a fixed point, from a separate workflow that ignores the score, and keep the check-in for finding problems.
Which clients get the check-in
Not every client needs every milestone. If your book has a small group of high-value accounts with a senior owner and quarterly reviews, the survey adds little for them; the owner already knows. The check-in earns its keep across the middle of the book, the profitable clients who get a standard service and are rarely asked anything. That is where dissatisfaction builds unseen.
For larger clients where several people have a say in the renewal, see account retention strategies on mapping and widening those relationships. For the CRM set-up behind renewal dates and owner tags, read CRM retention strategies.
What most retention advice gets wrong
It treats the survey as research. The firm collects scores, averages them into a quarterly figure and presents it at a board meeting. Nobody calls the client who scored four. The average looks fine, because one unhappy client is hidden among thirty content ones.
A check-in is an alert, not a statistic. Its value is in the individual answer reaching the right person the same day. The second error is the opposite one: treating the score as the goal. Teams start asking clients for a high score, the numbers rise and the cancellations do not change. Measure revenue retained and the share of low scores that get a call within a day, as set out in customer retention measures.
How the four industries use it
Agencies get the most from the after-first-report milestone, because scope disagreements surface there. Consultants should weight the change-of-consultant check-in, because relationships are personal. Mortgage brokers have long gaps between transactions, so the useful milestone is shortly after completion, when a high score is a natural moment to ask for a referral. Real estate firms should run the check-in with landlords, whose management fees recur, more often than with one-off buyers.
The trade-off
A milestone survey commits the firm to acting on every low score, quickly. That is senior time at unpredictable moments, and some weeks two or three calls will land on one owner. If owners cannot make those calls within a day, do not send the survey; a client who flags a problem and hears nothing is more likely to leave than one who was never asked.
You also give up the comfort of not knowing. The first few months will surface problems that were always there. That is the point, but the owner needs to back the account managers when the news is uncomfortable.
Troubleshooting
Every response lands on the None branch
The score is not being saved to the field the If/Else reads, or the operator is wrong. Submit a test survey and check the contact field.
The workflow does not start
The Survey is filter points at a different survey, or Disqualified is set to is true. Check both filters.
Owners miss the task
The task is assigned to a fixed user. Assign it to the account owner and add an internal notification.
Few clients complete the survey
It is too long or arrives at the wrong moment. Cut it to three questions and send it within a day of the milestone.
Frequently asked questions
How often should a client get a check-in survey?
Three or four times a year at most, tied to milestones rather than the calendar. More often and response rates fall.
Should the survey be anonymous?
No. The aim is to call the client who is unhappy, which needs their name. Say so in the survey so nobody feels misled.
What score should trigger an owner call?
Six or lower out of ten is a common cut-off. Start there and adjust once you see how your clients score.
Can the same workflow handle several surveys?
Leave Survey is blank and it fires on any survey. Separate workflows per milestone are easier to report on and adjust.