Your customer champion is leaving: a practical continuity guide

Your most engaged customer contact announces that they are leaving. They knew why earlier decisions were made, helped users move forward and explained what mattered inside the company. The next meeting may already be on the calendar, with nobody sure who will take over their responsibilities.

For the CSM, the immediate task is to make ownership clear: who can confirm priorities, who will continue the work and which decisions still need an owner? This guide proposes a practical way to arrange that transition with the customer. Adapt it to the account’s structure and actual deadlines.

Français · English · 한국어

Confirm what is changing

Record the known fact, its source and the date. A direct announcement from the customer, an automated email reply and a professional profile update provide different levels of confirmation. If the departure is unconfirmed, record the contact as needing confirmation and ask your usual contact a straightforward question: “Who is currently coordinating this project on your side?”

Once the change is confirmed, collect only what the project needs: the transition date if known, affected responsibilities and the interim point of contact. You do not need to investigate personal reasons for the departure or the person’s next employer.

Gainsight’s sponsor-change playbook recommends verifying the change with the customer and asking for an introduction to the new owner. It is a practitioner account published in 2014, rather than an effectiveness study or a universal response deadline. Gainsight sponsor-change playbook

Next, check the nearest real milestone: a workshop, an approval, a renewal decision or an operation requiring an administrator. If a planned action no longer has an owner, flag that specific dependency to your account team. Use the customer’s schedule to assess urgency.

Separate the roles before looking for a replacement

The word “champion” can cover several responsibilities. Here, it means an internal advocate who supports adoption and helps the project progress. The person replacing them in the organization chart may not inherit every part of that role.

• Champion or user advocate. Who understands users’ work and actively supports the project?
• Executive sponsor. Who supports the business priority and can resolve cross-team trade-offs?
• Economic buyer. Who can authorize the spend under the customer’s purchasing process?
• Administrator or operational owner. Who manages access and keeps day-to-day operations running?

One person may hold several roles. A job title or attendance at a meeting is not enough to confirm them. For each role, record the known contact, the confirmation received and any open questions.

GitLab explicitly distinguishes the champion from the economic buyer, whose approval is required for the purchase decision. Its CSM guidance also treats relationships with administrators, champions and executives separately. These distinctions help frame your questions; verify how the roles work at this customer. GitLab commercial roles and executive relationships.

Prepare a short continuity brief

Create a page the new contact can correct. Choose the context needed for the next decision instead of forwarding the complete conversation history.

• Customer objective. What outcome was agreed, with whom and in which document? Include the date it was last confirmed.
• Observed evidence. What usage or results have been documented? Include the source and observation period. Usage alone does not demonstrate a business outcome.
• Work in progress. What remains to be done, by whom and by which agreed date? Distinguish requests, proposals and accepted commitments.
• Roles to confirm. Who will coordinate the work, who makes decisions and who covers the transition? Keep unknowns visible.
• Documents and access. Where is the shared reference document? Who is authorized to check the access people need? Do not include passwords or transfer the departing person’s account.
• Next decision. What must be confirmed with the customer, and by which known deadline? If no date has been agreed, mark it as to be agreed.

GitLab’s success-planning guidance calls for explicit objectives, success criteria, owners and a timeline. The brief above is an editorial adaptation for a change of customer contact. GitLab success plans

Keep commercial assumptions and internal commentary out of the customer-facing version. Check authorized recipients and document permissions before sharing. A new name appearing in a conversation does not justify opening the entire account record to them.

Choose an appropriate way to make contact

The champion is still available. Ask which introduction would help and who is authorized to receive the brief. Suggest a transition conversation focused on open work. A recommendation can help you make contact, but the person introduced must still confirm their responsibilities.

The departure has happened and a new contact is known. Use the professional channel agreed with the customer. Explain your role, the project context and the decision that needs attention next. Ask what the new contact would find most useful to understand first.

No new contact has been named. Coordinate with your account team and approach an existing customer contact to ask who can cover the work in the meantime. Keep ownership marked as unconfirmed. A lack of response is not evidence of dissatisfaction or a decision to stop using the product.

Avoid having several colleagues contact the customer at once. Agree on one sender and a clear purpose. Building relationships with multiple stakeholders, as recommended in Gainsight’s documentation, can support continuity; each relationship should remain relevant to that person’s responsibilities. Gainsight stakeholder relationship guidance

Make the first message easy to answer

Adapt this example after the change has been confirmed and you have been introduced to the new contact:

Subject: Next steps and priorities for [project]

Hi [name],

[Contact’s name] introduced us to discuss the next steps for [project]. I’m your Customer Success contact at [company].

The objective agreed with your team was [objective]. The next item to confirm is [decision], before [previously agreed date, if applicable]. I’ve prepared a short summary of what has been confirmed and what remains open.

Are you the right person to coordinate this work? If so, what would you like to clarify first? If someone else is taking it on, could you point me to them?

Thanks, [Signature]

Remove any sentence that does not match the facts. Do not imply an introduction happened if it did not. If the person’s responsibilities are uncertain, confirm them before attaching customer documents. A written reply may be enough; suggest a conversation if the issue needs one.

Agree on the next step with the new owner

Use the brief as a starting point for the first conversation. Ask which objectives still apply, what has changed and who needs to be involved in upcoming decisions. Explain the available evidence and its limits, then confirm the next action and its owner.

Fictional example. Mina leads a team’s use of a tool and announces her departure. Alex takes over daily coordination. The CSM has meeting notes confirming the objective, but no evidence that Alex can commit the budget. During their first conversation, Alex confirms that a workshop should go ahead and explains that budget approval remains with their leadership. The CSM keeps the two roles separate. The recap identifies who will prepare the workshop and who will confirm the approval process. This meeting alone does not establish the renewal outcome.

If the new contact challenges the earlier objective, record what needs to be reconsidered with the customer. Preserve useful history without presenting the previous agreement as a personal obligation for the person arriving.

Check that the transition works in practice

Treat operational continuity as established when the customer has confirmed who coordinates the work, that person has the context and access appropriate to their role, and an owner has accepted the next action. Keep any unresolved roles or decisions visible.

Before closing your transition follow-up, check that:

• The change is confirmed and its source is dated.
• Known roles are separated from responsibilities still awaiting confirmation.
• The brief reflects confirmed information and current uncertainties.
• The right contact has confirmed their responsibilities and next steps.
• Useful documents are accessible only to authorized people.
• Each open item has a follow-up owner and a date agreed or still to be agreed.

Operational continuity does not guarantee renewal. It gives you a concrete basis for continuing the work with the customer and addressing the questions that remain.

To get started, choose an account affected by a contact change and fill in the continuity brief. The first unanswered question will tell you which conversation would be useful next.

What does this look like for your team?

Preparing for a change of contact at a customer account? Contact Lidia for a demo of Scalyo and a conversation about how your team manages its accounts. Mention the topic you would like to discuss, without including confidential customer information.

Request a demo with Lidia

About the sources

Sources checked on October 14, 2026. The cited GitLab and Gainsight pages describe their practices and recommendations. They are not a causal study of this method’s effect on retention. The brief, message and example are editorial proposals; no numerical performance result is claimed.