A customer update is due, but the investigation has not produced an answer. Waiting until everything is resolved can leave the customer wondering whether anyone is working on it; guessing can create a promise you cannot keep. A useful interim note does neither. It separates confirmed facts from open questions, explains what is happening next, and makes clear who will contact the customer again. Use the workflow below to send a timely, honest update, even when the most accurate answer is still: we are investigating.
The useful bits
- Share confirmed facts and label unresolved points clearly.
- Describe the next investigation step without predicting its result.
- Name the person or role responsible for the next customer update.
Start with the customer's question
Before drafting, reread the customer's latest message and identify the specific question they need answered. They may want to know whether an issue is acknowledged, what it affects, or when they will hear from you again. If you answer only with a generic statement such as “we are looking into it,” you may miss the part they actually need.
Write down the question in plain language. Then check the case notes or ask the people investigating for information that is confirmed and relevant to it. Do not treat an early theory, an unverified report, or a likely cause as established fact. If the team has not confirmed the impact, say that the impact is still being assessed rather than describing a scope you cannot support.
Separate facts from open questions
A short status note can still be specific. State what has been observed or confirmed, then identify what remains unknown. For example, you might confirm that the customer reported a problem with a particular process, while clarifying that the cause and the extent of the issue have not yet been determined.
Use wording that makes the boundary obvious: “We have confirmed…” for verified information and “We are still checking…” for unresolved points. Avoid language that quietly turns a possibility into a conclusion, such as “the issue is caused by…” when the investigation has not established that. If there is no new finding, say so directly and explain the work that continues.
Explain the next step without promising the outcome
Give the customer a useful picture of what happens next. Name the investigation action at the level you can accurately describe: reviewing the relevant records, checking a reported example, or asking the appropriate team to assess the issue. Include only steps that are actually planned, not actions that merely sound reassuring.
A next step is not a prediction. Avoid promising that the issue will be fixed by a particular time, that a suspected cause will be confirmed, or that the next update will contain a resolution unless you have a sound basis and authority to make that commitment. If you cannot responsibly estimate when the investigation will finish, do not invent a deadline. Instead, set a realistic time to provide another status note, if your team can commit to one, even if the investigation remains open.
Put a person on the next update
The customer should not have to guess who owns the follow-up. Name the person responsible, or identify their role if that is the clearest accurate option. For instance: “I will send your next update,” or “Jordan on our support team will contact you.” Confirm internally that the named person knows they own it and can access the case.
Separate the next update from the final answer. You can commit to another check-in without claiming the investigation will be complete by then. If you do not yet know when a meaningful finding will be available, say when the customer can expect to hear from you again only if that timing is approved and feasible. Otherwise, make the next internal check and ownership clear before sending, so the customer is not left with an unowned promise.
Keep the note brief, direct, and relevant
A useful order is: acknowledge the question, state confirmed information, name what remains under investigation, describe the next action, and identify who will provide the next update. Use ordinary language and avoid internal team labels or technical details the customer does not need.
Do not bury uncertainty under a long apology or repeated reassurance. If you need something from the customer, ask for one specific item and explain why it matters. Before sending, check that the recipient is correct and that the message does not expose internal-only notes or another customer's information.
Example and send check
Adapt this example to the case. Replace every bracketed field with information you have verified; remove any sentence that does not apply. The follow-up timing shown is a placeholder, not a recommended deadline.
- Are confirmed facts clearly distinguished from possibilities?
- Is the next action real, and is the named update owner aware?
- Can you meet the stated check-in time? If not, revise it before sending.
- After sending, record the commitment in the case and arrange the follow-up. Confirm it worked by checking that the note was sent to the intended customer and that an owner and reminder exist for the next update.
To: [customer contact] <customer@example.com> Subject: Update on [issue] Hello [customer name], We have confirmed [specific fact from the report]. We have not yet confirmed [open question], so I do not want to guess at the cause or outcome. Our next step is to [verified investigation action]. [Name or role] will send you another status update by [agreed check-in time], even if the investigation is still open. If you can share [specific information, if needed], it may help us assess [reason]. Regards, [Your name]
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