Start with: “Thank you for telling us. Would you be willing to explain what led to the decision, so we can understand what needs to change?” Your client exit interview questions should establish the client’s reasons before you make an offer. If they agree to talk, listen first and check whether the decision is open for discussion.
My view is that an exit conversation should be useful even when the client leaves. You can learn about an unresolved service problem and arrange a proper handover. Neither outcome requires turning the call into a last attempt to sell the client something.
Ask for Permission Before Trying to Retain Them
Say: “Is your decision final, or would you like us to discuss whether there’s a workable way forward?” If the decision is final, respect the answer and ask whether they’re willing to share feedback. Don’t make that feedback a condition of arranging the transition.
Check who should lead the conversation. A technician shouldn’t have to defend the agreement while trying to resolve a user’s ticket. Erick Simpson recommends bringing potentially difficult client discussions to leadership, leaving the technician focused on helping the user. Treat that as his suggested operating approach.
Before the call, read the relevant account record with the service lead. Check for open work and promises that still need an answer. You shouldn’t ask the client to rebuild a history your MSP already holds, but you should give them room to correct it.
Use Questions That Find a Specific Reason
Use these questions as a proposed talk track. Ask the relevant follow-up and let the client finish. The goal is their account of the decision, not a set of answers that supports your preferred explanation.
| Question to Ask | What to Listen For | Useful Follow-Up |
|---|---|---|
| “What led you to decide that the current arrangement should end?” | The reason the client gives in their own words. | “Which part mattered most to that decision?” |
| “Can you give me an example of where the service did not match what you needed?” | A case your team can investigate rather than a general label. | “What should have happened instead?” |
| “Has the business or the way you want IT handled changed?” | A different requirement or decision structure. | “What does the next arrangement need to do differently?” |
| “Was there a point when you expected us to respond differently?” | A missed expectation or unresolved commitment. | “What response would have been useful then?” |
| “If you’re open to an alternative, what would it need to address?” | The condition that would make a revised proposal worth considering. | “Would you like us to assess that and come back with a specific answer?” |
Distinguish the stated reason from your internal hypothesis. If the client says price, record that. Don’t rewrite it as poor service because the ticket report concerns you, or as price sensitivity because that’s easier to accept. Investigate the supporting evidence separately.
A cheaper competing offer also needs clarification. Ask what service the client expects from it without demanding confidential details of the competitor’s proposal. You can compare your own scope honestly without claiming to know what another MSP will deliver.
Answer the Objection Without Cutting the Fee
If the client says, “You only called because we’re leaving,” reply: “I understand why the timing looks that way. I want to hear what we missed and agree what happens next. You don’t have to reconsider for us to do that.” Then give them room to answer.
If they say, “We’ve already explained the problem,” reply: “I’ll review the existing record with our service lead. Can I confirm that the unresolved issue is this?” State the specific issue you found and let them correct it. Don’t ask for another general account of everything that went wrong.
What do you say when the client asks for a lower price to stay? Say: “We can’t offer the same service for less. We can check whether the service you need has changed, and whether a different scope would fit.” Get approval for any changed offer before promising it.
The model doesn’t discount monthly recurring revenue to win a client. Keep that discipline when considering a retention offer too. A different scope needs a genuine service change with clear responsibilities, rather than the same promise relabeled to conceal a discount.
I don’t buy generic advice to “save the account at any cost.” An MSP still has to staff the service after the conversation ends. A lower fee with the same unresolved delivery problem can leave both sides paying for an arrangement that still doesn’t work.
Offer a Repair You Can Actually Deliver
If the issue is work the MSP already owes, arrange the correction on its own merits. Don’t make completing that work conditional on renewal. Say: “This is part of the service we agreed. Our service lead will confirm the corrective action and the next update.”
If the client is willing to consider a new arrangement, have the delivery lead test its feasibility. Keep an extra commitment explicit, with the person authorized to approve it. A discretionary benefit still consumes resources even when it doesn’t reduce the monthly fee.
Use a proposed reply such as: “We can assess that change. I’ll come back with the scope and the person responsible, and we can decide whether it addresses your concern.” Don’t promise a result merely because the call is uncomfortable.
When the gap is a service your MSP can’t support, say so. A clear explanation can be more useful than a retention offer built around a capability you still need to invent. If there’s a suitable alternative, explain it without implying that the client must choose it.
Let a Final Decision Become an Orderly Transition
If the client confirms they’re leaving, say: “Understood. Let’s confirm the transition contact and the work that needs to move, then send you a written plan for review.” Keep that conversation separate from your request for feedback.
Paul Green recommends a calm explanation focused on fit, written confirmation of notice and an orderly transition when an MSP ends a poor-fit relationship. That practitioner suggestion applies to the tone of the handover here. Use the actual agreement and authorized process to establish the dates and responsibilities.
Name the person coordinating the transition on each side. Confirm what support continues while it’s underway, and record how an unresolved issue will be handled. The client’s decision to leave doesn’t make the remaining service work ownerless.
The model calls for replacing bad revenue with good while protecting the total. Give the owner the expected revenue change so they can plan. That commercial concern shouldn’t become a demand that the client wait for you to win a replacement before you cooperate with an agreed transition.
Keep the Learning Specific
Record the client’s stated reason and any corrections to your account history. Keep the service lead’s findings distinct from what the client said. If they decline an interview, mark the reason as unconfirmed rather than guessing.
Assign a change only after the relevant owner has checked the issue. Repeated complaints may show a process worth reviewing, but the pattern alone doesn’t establish its cause. Nor does a client agreeing to stay prove that a particular script retained them.
Before the next exit call, read the open commitments and choose the questions that fit what is known. Ask permission to discuss an alternative, give a specific answer if you can deliver one, and leave with an owned next step. If the decision remains final, send the transition plan for agreement.
mspoutpost.com/articles/client-exit-interview-questions-that-keep-the-talk-useful
Written by Natalie Brandt
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.