How do I tell customers about a change to the way a service works?
Quick answer
Tell customers plainly what is changing, when it takes effect, who is affected, and what action they need to take. Put the most important details first, explain what stays the same if that prevents confusion, and provide a way to ask questions. Before sending, verify dates, eligibility, and instructions with the people responsible for the service; use placeholders until those details are confirmed.
The question, the details, the next step.
How do I tell customers about a change to the way a service works without making the announcement confusing or alarming?
Lead with the change itself, then explain its timing and effect on the customer. Avoid vague openings like “We’re updating our service” unless you immediately say what that means in practice.
A useful order is:
- What is changing?
- When does it start?
- Who is affected?
- What should the customer do, if anything?
- Where can they get help?
Keep confirmed facts separate from internal reasons or hopes. If an important detail is still being decided, don’t present it as settled; confirm it before sending or clearly mark it as forthcoming.
What information should I gather before I start writing?
Make a small fact sheet first. Ask the service owner to confirm the old process, the new process, the effective date and time, the affected customer groups, any transition period, and whether customers must take action. Confirm what remains unchanged if customers might otherwise assume more is changing than actually is.
Also check whether the announcement needs different instructions for different groups. If so, state who each instruction applies to rather than putting several possibilities in one paragraph. Use placeholders such as [effective date] and [support channel] until the responsible team verifies them. Don’t guess at dates, eligibility, fees, or consequences.
Can you show me a draft structure? Assume a booking service is changing how customers confirm appointments, but I don’t know the actual date or exact steps yet.
Those details are assumptions for this example, not facts to send as written. Here is a copyable draft with gaps to verify:
Subject: A change to how you confirm appointments
Starting [effective date], customers who use [affected booking service or customer group] will confirm appointments through [new confirmation method]. This replaces [old confirmation method].
To confirm an appointment, [verified step-by-step instruction]. Please complete this by [deadline, if applicable]. [State clearly whether customers need to do anything before the change takes effect.]
Your [unchanged service feature, if verified] will continue as usual. If you need help or have questions, contact [approved support channel].
Thank you, [Service team]
Before sending, replace every bracket with a confirmed detail or remove the sentence. Don’t say a feature is unchanged, or that a customer must act, unless the service owner has verified it.
How can I make the announcement reassuring without hiding the impact?
Be calm by being precise, not by minimizing the change. Name any real customer effort or limitation clearly, then explain the next step in plain language. If the reason for the change is confirmed and useful to customers, give a short explanation; otherwise, don’t invent a rationale or promise benefits you can’t substantiate.
For example, replace “Nothing major is changing” with a specific statement such as “[Verified part of the service] will stay the same; you will need to use [new method] to complete [specific task].” If customers could be affected differently, say which group should follow which instruction. Ask a colleague who knows the service to check the facts and a customer-facing colleague to check that the steps are understandable.
What should I check in the final version?
Read it from the customer’s point of view: Can they tell whether the change applies to them, when it begins, and what to do next? Check that the subject line describes the change, the date and instructions match the approved details, and any action deadline is unmistakable. Remove internal shorthand and unsupported claims.
A final practical test is to ask someone unfamiliar with the change to explain, in their own words, what they would do and by when. If they cannot, revise the relevant sentence. Keep a record of who verified the operational details and which customer groups received the message, following your organization’s normal process.
A practical checklist
Confirm the old and new process with the service owner.
Verify the effective date, affected customers, deadlines, and required actions.
Separate different customer groups’ instructions so they cannot be confused.
Use placeholders for details that are not confirmed; remove or verify each before sending.
Check that the announcement says what stays the same only when that is confirmed.
Ask a colleague to verify the facts and another reader to test whether the next step is clear.
A few more useful answers
Should I explain why the service is changing?
Include a brief reason when it is confirmed and helps customers understand the change. If the reason is uncertain or not useful to the reader, focus on the practical impact instead.
What if customers need to take different actions?
Divide the instructions by customer group and label each group plainly. If you cannot identify who belongs in each group, get that detail confirmed before sending the announcement.
What if the date or process is not final?
Do not state an unconfirmed date or instruction as fact. Wait for verification, or send a clearly labeled update only when you can explain what is confirmed and when customers will receive the remaining details.