Price increase customer communication does not end with the email; support work starts there. Within days the same questions arrive: why, from when, can I cancel, can I switch plans, are there exceptions, and will existing customers keep the old price? This guide covers the support plan, not the letter itself.
The plan has five parts: a help article published before the email, approved replies to six typical questions, one tag to count reactions, written exception rules with a named decision maker, and a path for customers who threaten to leave. The examples use Rostrly, a fictional staff scheduling app sold by subscription. Replace bracketed amounts and dates with your own.
What must be ready before you announce the increase
The most common mistake is sending the email before the support team has seen it. Questions arrive within hours, and an agent who lacks the details starts guessing. Send on a day followed by a fully staffed working day, and share the final email with the team a day in advance.
- Final email text and recipient list: which customers, which plans, from which date.
- A published help article with the same amounts and dates as the email.
- An updated pricing page, or a clear note on when it will show the new prices.
- Team macros answering the six typical questions, checked by the decision maker.
- A tag for price increase conversations, created before the first message arrives.
- The name of the person who approves exceptions, and how quickly they respond.
Check the pricing page separately: a customer who still sees old amounts there will ask which version is true. Our pricing page guide shows how to test a new table.
A help article before the email, not after it
The help article is the single source that both the email and the team refer to. Publish it before sending and link to it in the email. Customers check details without waiting; agents paste the link instead of retyping terms. The article answers the questions the email only hints at.
Price change from [date]. What changes: new amounts for the [names] plans. Who is affected: [customer groups], from the first billing period after [date]. Why: [one specific sentence about the reason]. Your options: stay on your current plan, move to [plan], or cancel in your account settings before [date]. Have a question about your situation? Message us in the chat.
In Meetlead customer support, an article published in the Help Center is available in the website widget and, with Meet AI active, also becomes a source for its answers. Meet AI explains dates and amounts but never changes a plan or price; a person handles those requests. For structuring tips, see our guide to a knowledge base and FAQ on your website.
Six questions and approved replies
These questions are predictable. Write replies before sending and have the pricing owner approve each one. An approved reply is not a script; it sets limits within which agents use their own words.
Scroll the table sideways to see all columns.
| Customer question | What they want to know | Approved reply |
|---|---|---|
| Why is it more expensive? | Whether the change is justified | One specific reason from the article, no vague market talk |
| From when? | When they first pay more | Date of the first charge at the new price for their plan |
| Can I cancel? | That they will not be charged against their will | Yes: where to cancel and the last day before the new price |
| Can I change plans? | Whether there is a cheaper route | A plan that fits their usage and the difference in scope |
| Are there exceptions? | Whether their case is special | Written rules; other requests go to the decision maker |
| Will I keep the old price? | Whether loyalty counts | Only if such a rule exists; never promise it in chat |
Save each reply as a team macro in one category, such as "Price change [month]", with variables for the customer's name and plan. Our guide to reply templates in customer service shows how to avoid sounding automated. Fix unclear replies in macro and article together.
One tag to count reactions
Without tagging, you will not know how many people wrote or what they asked. Create one tag before sending, such as "price change [month]", and add it to every related conversation, whatever the channel. Record the question type in an internal note instead. The same works during outages; see our guide to consistent incident updates.
- Tag every conversation.Agents add the tag to each price change conversation, including Messenger and Instagram Direct if connected.
- Note the question type.One word in an internal note: reason, timing, cancellation, plan, exception or old price.
- Review daily for a week.Filtering the inbox by the tag shows all these conversations; the tag usage counter shows how many.
- Fix the source of questions.If one question dominates, move its answer to the top of the help article and update the macro.
The tagged count does not show how customers received the increase; many never write, and some cancel silently. Treat it as a measure of team workload and article quality, not a verdict on the pricing decision. Our guide to tagging conversations and tickets covers consistent tagging rules.
Exceptions: rules, a decision maker and a note
Exception requests will come: an annual plan bought last week, a charity, a customer with an open service problem. Decide in advance which cases have a set answer and which need a decision. Agents neither grant exceptions themselves nor refuse upfront; they record the case and tell the customer when to expect an answer.
Name one decision maker and a response time, for example one working day. The agent writes the customer's plan, the reason for the request and a recommendation in an internal note, and tags the decision maker with an @mention. Record the decision there too. After a week, review the notes: turn a recurring request into a rule or clearly exclude it.
Apple's App Store Connect documentation describes two options when raising a subscription price: keep the current price for existing subscribers or apply the change to them, and in some cases subscribers must consent. Apple Developer. These are one platform's in-app rules, not a model for every business, but they show the old price question is settled before announcing.
When a customer threatens to cancel
"Then I am cancelling" comes in two forms. The first is a decision: the customer wants to know how to end the contract before the new price applies. Help without obstacles, as in our guide on how to handle subscription cancellations. The second is a signal: the customer is weighing options. Then suggest, once, a plan that fits their usage.
"I understand the new price does not fit how you use the app. If you want to end your subscription before [date], you can do it in your account settings under Subscription, and I will confirm when your access ends. If you would rather stay, the [name] plan includes [scope] and costs [amount]. Let me know which option you prefer."
An individual discount request follows the escalation path: assign the conversation to the decision maker, raise the ticket priority and give the customer a response date. Our guide on what to do when a customer asks for a discount covers that conversation. Never promise a reduction just to close the chat.
Directive 93/13/EEC of 5 April 1993 on unfair terms in consumer contracts lists in its annex, as a term that may be regarded as unfair, one allowing a supplier to increase the price without giving the consumer a right to cancel if the final price is too high compared with the agreed price. EUR-Lex, Directive 93/13/EEC. It covers consumer contracts in the EU and applies through national law; the list is indicative and does not decide your contract; review its terms, as this text is not legal advice.
Questions about support after a price increase
How far ahead should support be ready? The help article, macros and tag should be ready before the email goes out, and the team should know the announcement at least a day in advance. Customer notice periods depend on your contracts and the law.
Can an AI assistant answer price increase questions? It can explain what the published article says: amounts, dates and how to cancel. It should not promise exceptions, the old price or a plan change; in Meetlead an agent takes those over, and Meet AI does not change prices or subscriptions.
