A completion message can reassure a customer—or create confusion—depending on how precisely it describes the work. “It’s fixed” may sound final even when only one setting, document, or account detail was changed. A useful update names the requested change, says what you actually completed, and makes clear what has not been done or independently checked. It should also give the customer an easy, specific way to point out a mismatch. This approach keeps the message helpful without promising more than you know.
The useful bits
- Name the exact requested change and its scope.
- Separate completed work from remaining steps or checks.
- Invite the customer to identify any specific mismatch.
Anchor the message to the request
Start by identifying the request in terms the customer will recognize: the item, setting, record, or part of a process they asked you to change. If several changes were discussed, name the one you are reporting on rather than implying that every request is complete.
Use concrete wording such as “I updated the delivery contact on the order” instead of “Your account has been taken care of.” The broader statement could suggest that unrelated details were reviewed or changed. If there is a reference number or date that helps distinguish the request, include it only when it is accurate and appropriate to share.
Describe the action, not an assumed outcome
Say what you did and, where useful, what value or destination it now shows. Match the level of detail to what the customer needs to recognize the change. For example, name the revised contact address rather than saying only that “the information was updated.” Avoid exposing information the customer does not need in the message.
Keep the statement within what you can confirm. Completing an edit does not necessarily prove that a separate system, another person, or an outside provider has acted on it. Do not turn “I changed the notification address” into “you will now receive every notification” unless that broader result has actually been confirmed.
Draw a clear boundary around completion
If part of the request remains open, say so in the same message as the completed work. Identify the remaining step and who is expected to take it, if known. If timing is uncertain, do not invent a deadline; explain what is pending and say when you can provide another update only if you can commit to doing that.
Distinguish completion from verification. You might have saved a change without checking how it appears to the customer, or you may have confirmed one screen without checking other records. State that limit plainly. “I updated the contact on this order; I have not checked other orders” is more useful than implying a wider review.
Use a quick scope check before sending
Before writing, compare the original request with the work you completed. Check the relevant record or confirmation available to you, then note any part you did not change or verify. This helps prevent a familiar shorthand—“all set”—from overstating the result.
A short checklist can keep the update precise:
- What exact change did the customer request?
- What specific item or value did I change?
- What remains pending, or has not been checked?
- What detail would help the customer spot a mismatch?
Invite correction without shifting the burden
End with a low-friction invitation to flag a mismatch. Ask the customer to identify what looks different, or to reply with the relevant item or screen if that would help clarify the issue. Keep the request proportionate: do not ask them to repeat information you already have or imply that they must prove the change was made.
A useful invitation is specific and open-ended: “If the contact shown on this order is not the one you requested, please reply with the correct detail.” This gives the customer a clear next step while avoiding a claim that every related detail has been checked.
Example: report one completed detail
Suppose a customer asked for the contact address on one order to be changed. You updated that order but did not review other orders or test whether messages will reach the new address. The note should report exactly that scope, distinguish it from those unchecked outcomes, and make it easy to correct an error.
Subject: Contact address updated for [order reference] Hi [customer name], I changed the contact address on order [order reference] to [new address]. This update applies to that order; I have not checked other orders or confirmed message delivery to the new address. If the address shown for this order is not the one you requested, please reply with the correct detail and I’ll review this change. Regards, [Your name]
Confirm the message is accurate
Read the draft once as the customer: can they tell what changed, where it changed, and what is still unknown? Then check that the message contains no promise of a wider fix, future result, or review that did not occur. If the change has not actually been completed, send a progress update instead and label it as pending.
After sending, your confirmation is the clear, scoped update itself—not proof that every related process succeeded. If the customer flags a mismatch, compare their detail with the original request and the item you changed before replying. Correct the record if appropriate, or explain what still needs attention.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction