Skip to content
Lines open
Map my coverage

Call operations

Write a call script for a scheduled price increase

A practical script structure for telling existing customers about a price change without hiding the reason, rushing the reaction, or promising exceptions.

Write a call script for a scheduled price increase
Table of contents

A price increase call is not a sales pitch and it is not an apology tour. The caller needs three facts: what changes, when, and what remains the same. A script helps the agent deliver those facts in the same order every time while leaving room for a real reaction. The goal is a clear, respectful conversation that ends with a recorded decision, not a debate about company strategy.

Key takeaways

  • Name the change, the effective date, and the reason in the first minute.
  • Give the agent approved wording and a short list of questions they cannot answer alone.
  • Let the customer react before offering any option or exception.
  • Record the outcome, the reason, and the next step in the customer record.
  • Review the first week of calls for missing facts and inconsistent promises.

Decide who can announce the change

The script should state whether every agent can announce the increase or only a named team. A small company may want the owner to call its largest accounts first, while routine accounts follow the standard script. Write that split into the call list so the agent does not improvise. The customer should hear the same basic message whether the call comes from an owner or a virtual assistant.

Give the agent a short description of the reason that customers are allowed to hear. A sentence about rising delivery costs is different from a full breakdown of supplier contracts and margins. Approve one plain explanation and keep the internal detail out of the call. An agent who invents a reason creates a promise the business cannot keep.

Decide in advance which exceptions exist and who can approve them. A short grace period, a revised service tier, or a payment plan may be available, but the agent should not guess. List the eligible customer groups and the exact words to use. Anything outside the list goes to a named owner with a callback time.

Open with the reason and the date

The opening should identify the company, the agent, and the purpose in one breath. A useful pattern is to say that the call is about a change to the service price shown in the customer's notice. Then stop and let the customer respond. Do not begin with a long list of economic conditions, because the customer has not yet agreed that this is a price call.

Confirm that the agent is speaking with the right person before sharing account details. Ask for a name and one approved identifier, then continue only when the match is clear. If the customer is not available, leave a neutral message that does not disclose the amount. The caller identity check guide explains how to keep that step short.

Say whether a written notice was already sent and when. If the notice went out last week, the customer may have it open; if it is going out today, say that plainly. A mismatch between the call and the notice creates confusion that the agent cannot repair later. The script should match the actual mailing or email date.

Mention the effective date before the amount. The date gives the customer a frame for the change and reduces the chance that they hear only the largest number. Then state the new price and the current price together. End the opening with a simple question about what the customer would like to know first.

Handle the first reaction without arguing

The first reaction may be silence, a question, or anger. Give the customer time to finish before responding, and do not correct their tone. The agent should acknowledge what was heard in one sentence, then return to the approved facts. A calm reply is more useful than a fast defense of the company.

Use a short empathy line that does not admit fault or promise a reversal. The phrase "I understand this is unwelcome news" is safer than an apology that suggests the company made an error. The first acknowledges the reaction, while the second creates a service failure record that may not be true. The agent should stay on the approved facts.

If the customer asks for a discount, follow the exception list rather than negotiating. The agent can say what is available and what requires review. Do not invent a loyalty rate or imply that another department will probably approve it. A false hope turns one difficult call into two.

If the customer becomes abusive, use the standard warning and ending rule. The agent does not have to absorb threats or repeated personal insults. State that the call will end if the behavior continues, then close the call and record what happened. Escalate the account to the owner with the facts, not a summary of the emotion.

Record the outcome and the next step

Every call needs a disposition that separates acceptance, a request for review, a cancellation request, and no contact. Add the reason the customer gave in their own terms, without guessing at motive. A note about a question on visit frequency is more useful than a note that says the customer was upset about price. The next agent should be able to continue without replaying the recording.

Assign an owner and a due date for every open item. If the customer wants a payment plan, the owner is the billing contact and the due date is the next business day. If the customer wants to cancel, the owner is the account manager and the due date follows the contract notice rule. A call that ends with a vague review has no accountable next step.

Do not close the customer record until the written summary or follow-up call is complete. The price change is not finished when the phone hangs up. The agent should mark the task open and leave the customer's preferred contact method in the record. This is especially important when the customer asked for a callback outside their working hours.

Review the calls after the first week

Listen to a small sample of the first week's calls and check four things: the date, the amount, the reason, and the next step. Mark any call where the agent skipped one of those facts or added an unapproved promise. Fix the script before the next block of calls rather than coaching each agent separately. A repeated gap usually means the script is unclear.

Compare the outcomes with the call list. Count how many customers accepted, asked for review, or requested cancellation. Look for groups where the agent needed extra time or where the same question appeared repeatedly. Those patterns point to missing preparation, not necessarily poor agent performance.

Keep the approved version under version control and record the change date. When the next price change arrives, the team can reuse the structure without copying the old numbers. The research review of price-increase call outcomes offers a way to measure whether the conversations are producing useful evidence. Listening to the calls is still necessary.

Sources

Map the first queue

GIVE MISSED CALLS A WAY BACK IN.

Share your call types, hours, tools, and escalation rules. We will turn them into a practical coverage plan with a clear first week.

Book a free consultation ↗See the call lanes