Reset success goals when service priorities change

A success plan built around one priority starts to mislead everyone the moment that priority changes. A contact center might shift from growing chat adoption to cutting repeat contacts, or from voice to digital support, or reassign a region to a new leader. When that happens, the goals on paper stop matching the goals in the room. A customer success manager who keeps reporting the old numbers as progress is measuring the wrong thing, and the customer notices before the CSM does. The fix is not a quiet edit to the plan. It is a direct reset conversation that puts current decisions and current evidence back at the center.

Why this conversation goes wrong

In a contact center this shows up constantly. Leadership moves budget from growth to cost control, shifts support from voice to digital channels, or reassigns a region to a new director, and the success plan doesn't move with any of it.

Most CSMs avoid this conversation because it feels like admitting the plan failed. It didn't fail, the business moved. But saying "the goal changed" out loud invites questions about why nobody flagged it sooner. So CSMs quietly keep reporting the old metric, hoping the new priority gets folded in later without anyone noticing the gap. That approach backfires. The customer's leadership already knows service priorities changed, since they made the decision. When a quarterly review still leads with adoption numbers nobody asked for anymore, it signals the CSM is out of step with the account, not careful with it.

The other common failure is the opposite problem. A CSM hears about the shift secondhand, panics, and proposes a brand new target in the same meeting before anyone agrees on what evidence should define success. A number picked without agreement on the source of truth gets disputed the next time it is reported, and the CSM spends the next quarter defending a target instead of tracking one.

How to prepare

Before you raise a reset, write down what you actually know. What changed in the account's operating plan, and who told you. Which current goal in the success plan depends on the old priority. Who owns the new priority on the customer's side, because that is rarely the same stakeholder who owned the last one. This is the same groundwork that matters when a routing change shifts how an account measures support quality, covered in Support adoption after a routing changeand it applies here too. A new priority needs a name attached to it before it becomes a real goal.

Also decide what you are not going to do in this meeting. You are not going to propose a new number on the spot. You are not going to let the old goal quietly disappear without a line in the plan explaining why. And you are not going to let this turn into a review of last quarter's performance, since a business decision to shift priorities is not the same as a missed target.

What to say

Nina, a customer experience leader, opens the call. "Last quarter we wanted more chat adoption. Now leadership wants to cut repeat contacts instead." CSM Oscar doesn't jump to a new metric. He asks, "Which team owns the repeat contact definition, and whose numbers do you trust when they disagree?" Nina admits quality and analytics already count repeats differently, and nobody has reconciled it. Oscar says, "Before we set a target, can they send us two recent reports and walk through how each one counts a repeat contact?" Nina agrees to ask both teams. Oscar closes the loop. "Once we see where those definitions overlap, we'll know whether the success plan needs a definition review, a workflow change, or an adoption goal we can actually measure. I'll draft that section and send it to you before we lock it in."

Notice what Oscar didn't do. He didn't accept "reduce repeat contacts" as a target on its own, since a goal with no agreed definition cannot be measured. He didn't guess at a number to fill the silence. He asked who owns the decision and what evidence they trust, then gave the conversation a next step with a date attached.

What a real reset changes in the plan

A reset is not just a new number, it changes three parts of the plan at once. First, it separates a business decision from a product assumption. Leadership decided to prioritize cutting repeat contacts, that is their call, not a hypothesis about which support channel works best. Your job is to represent that decision correctly, not to argue with it. Second, it replaces old evidence with evidence the customer already trusts. If quality and analytics disagree about what counts as a repeat, a chat adoption number from last quarter's dashboard is worthless. The plan needs a source both teams recognize, even if that means a short delay while they reconcile definitions. Third, it assigns ownership on both sides. The customer names who owns the new priority internally, and you name what you own, usually coordinating evidence and tracking progress against the agreed definition. Skip any one of these three and the reset is cosmetic, a new label on the same broken tracking.

Mistakes to avoid

Don't compare the new priority to the old one as if the customer's team failed to hit last quarter's number. The business changed direction, that is not a missed target, and treating it like one puts the stakeholder on the defensive for a decision that was probably made above them.

Don't let the reset conversation drift into a performance discussion about a specific person on the customer's team or your own. If a stakeholder tries to use the reset to raise concerns about how someone is graded or coached, that is a separate and more sensitive conversation, closer to the ground covered in Explaining coaching score limits in an HR request. Keep the plan reset about goals and evidence, not people.

Don't leave the old goal off the record without a note explaining the change. Six months from now, someone will ask why chat adoption disappeared from the plan, and "priorities changed" without a date or a name attached is not an answer anyone can act on.

Don't set a new target before the evidence source is settled. A target built on a disputed number gets renegotiated every time it is reported, which wastes more time than the extra week it takes to agree on a definition first.

How to practice and score it

Take a real or sample success plan and cross out one goal whose business context has changed. Write, next to it, a question for the business owner, a source of evidence, and a review date. That is the whole reset in three lines, and if you cannot fill in all three, you are not ready to have the conversation yet.

Then run the exchange as a roleplay. DealSpeak lets you rehearse this exact scenario against an AI counterpart playing a stakeholder like Nina, so you can practice asking about ownership and evidence before you are in front of the real customer. Score yourself, or have a manager score you, on three things. Did you ask who owns the new priority before proposing a target. Did you ask what evidence exists and where it disagrees. Did you leave the meeting with a name, a source, and a date attached to the next step, instead of a vague promise to follow up. If a manager wants more scenarios like this one, the full set of Contact Centers practice conversations covers other moments where a plan needs to catch up with a decision the business already made.

A goal reset is not a failure to record, it is a maintenance task every account needs on a regular basis. Do it before the old numbers go stale in a report, not after a customer asks why they're still there.