Reviewing multilingual use before renewal

A customer asks why they are paying for a multilingual feature almost nobody touches, and the renewal conversation tips toward a discount fight before you have said a word. The usage number alone tells you nothing about access, training, or fit. Your job is to slow the conversation down and separate what actually happened from what the contract promised.

Why this conversation goes wrong

Low usage numbers feel like proof. A customer sees one dashboard figure, say three percent of tickets routed through a Spanish language workflow, and concludes the feature failed. But usage is a downstream number. It reflects three upstream conditions, whether the feature was turned on in a given country, whether agents were trained to use it, and whether customers in that region had a reason to contact support in another language at all. Collapse those three into one line and you get a debate about price instead of a diagnosis.

Once a customer says something is unused and should be cut, the meeting is already framed as a discount negotiation. Argue the number and you lose, because you are defending a metric you do not fully understand yet either. Stay silent and agree too quickly, and you set a precedent that any low adoption figure earns a price cut regardless of cause. Neither outcome serves you, and both are avoidable if you do the homework before the meeting starts.

How to prepare before the renewal meeting

Build a region by region record before you sit down with the customer. Pull three pieces of information for every country named in the contract.

1. Activation status, meaning whether the feature is technically enabled in that country, since local requirements sometimes delay or block activation entirely.
2. Training history, meaning which regional teams received routing training and when they received it.
3. Usage evidence, meaning actual contact volume by language and region, checked against the rollout timeline rather than against the contract signing date.

Put this in one table with a named owner for each region, whether that is a regional operations lead or the customer's own system administrator. This table becomes the spine of the conversation. Without it, you are reacting to whatever number the customer brings to the meeting instead of controlling what the discussion is built on. This scenario sits alongside other situations covered under Contact Centers practice conversations, including what to check before a rollout even starts. The same discipline, confirming configuration and readiness before assuming a problem exists, applies well before renewal season. Run a readiness review before a new service site launches walks through that same idea from the launch side, and it is worth reading if your team tends to skip these checks until a customer forces the issue.

What to say in the room

Open by naming the concern directly, then move to facts. Skip the acknowledgment and jump straight to your table, and you sound defensive. Acknowledge the concern but produce no plan for getting facts, and the customer assumes you are stalling.

Luis said, "Why are we paying for a feature that almost nobody uses." Hana said, "That is a fair question, and I want to answer it with facts you can check yourself. Can you tell me which regions went through training on the routing workflow, and which contracted countries actually have the feature turned on today." Luis said only one region had completed training, and two of the contracted countries never had the feature activated at all. Hana said, "That gives us two separate problems, not one. Where the feature is active and usage is still low, we look at training gaps. Where it was never activated, we look at what the local requirements are and build a realistic timeline. Can we bring your regional operations lead and your administrator into the next call so we are all working from the same information."

Notice what Hana did not do. She did not defend the usage number, and she did not promise she could fix everything by the next call. She split one vague complaint into two specific, checkable questions, and she invited the people who could verify the answer instead of asking Luis to take her word for it.

Mistakes that make this worse

A few habits turn a fixable configuration gap into a lost renewal.

Promising universal activation. Some countries restrict how a routing feature can be configured, and telling a customer you will turn it on everywhere by next quarter sets up a promise you cannot keep. Say plainly what depends on local review and what does not.

Treating one blended usage number as the whole story. A total across ten countries hides the fact that two of them never had the feature switched on. Break the number apart before you respond to it, or you end up negotiating against a figure that misrepresents the actual gap.

Turning the meeting into you against the customer. The regional operations owner and the customer's own administrator hold information you do not have sitting in your own dashboard. Bring them into the conversation rather than trying to answer every question yourself in the room.

Skipping the acknowledgment entirely. Leading with a spreadsheet before recognizing that the customer has a legitimate commercial concern makes you sound like you are hiding behind process instead of solving a problem with them.

Practicing this before it counts

Reading a framework once does not prepare you for the moment a customer accuses you of selling something nobody wants. Practice the exchange out loud, against pushback that does not follow the script above, since real customers rarely stick to it. A manager can score three things after a practice run. Did the person acknowledge the commercial concern before moving to data. Did they separate activation, training, and usage into distinct questions instead of treating them as one issue. Did they close with a next step that names actual owners instead of leaving the resolution vague.

DealSpeak lets you rehearse this exact conversation against an AI counterpart that pushes back the way a frustrated customer would, then scores the exchange against those same three points. Running it more than once matters, because the first attempt usually reveals which of the three questions you forget to ask once someone is actually pressing you on price.

If several of your renewal conversations this quarter are shaped by a recent change in what leadership expects from the account, it is worth reading about how to reset success goals when service priorities change, so the standard you are scoring against still matches what the business wants right now.

Closing the gap before the next renewal

A low usage number is a starting point, not a verdict. Do the regional homework, ask the three separate questions in the room, and bring in the people who can confirm the answer instead of guessing at it yourself. That turns a tense renewal into a problem you are solving with the customer instead of a price argument you are losing to them.

You can rehearse this exact conversation in the Contact Centers practice conversations library before it happens for real. When you have this one down, read Run a readiness review before a new service site launches next.