Toybird Labs BlogThis is a fictional training case. The email, internal notes and completed replies below were written for this guide; they are not a real customer conversation or a recorded AI output.
Start with two different times
The CSV export button has stopped producing a file. I need the data for an internal meeting at 17:00 today. Will it be fixed in time? Please tell me what is happening.
The customer's 17:00 deadline describes their need. Your team's 15:00 commitment describes when you will send an update. Neither establishes when service will be restored.
| Information type | What the team knows |
|---|---|
| Confirmed | The report has been received and passed to the technical team for investigation. |
| Unknown | Cause, affected users, recovery time and a working alternative. |
| Approved commitment | Send a status update by 15:00, even if there is no progress. |
| Information to request | Time of the failure, browser and version, and any error message. |
| Not approved | Refunds, compensation, manual data delivery or a recovery deadline. |
Give the AI the reply materials, not permission to fill the gaps
Use an AI environment approved for this information. Removing a customer's name does not necessarily remove confidential details.
Draft an initial customer reply using only the customer email and internal notes below.
Acknowledge that the data is needed by 17:00.
Say that the report has been passed to the technical team for investigation.
Do not promise recovery by 17:00: the recovery time is unknown.
Promise a status update by 15:00, whether or not there is progress.
Ask for the failure time, browser and version, and any error message.
Do not add causes, troubleshooting instructions, workarounds, refunds or other commitments.
Return a subject and email body. In a separate internal section, list each commitment and the note that authorizes it.
[Paste the customer email and the table above.]
The separate commitment check is more useful here than a generic request to make the reply polite. It makes a specific error visible: changing a communication deadline into a repair deadline.
A reply that fits the notes
Subject: Update on the CSV export issue
Thank you for reporting this. I understand that you need the data for your 17:00 meeting.
We have passed your report to the technical team for investigation. The cause and recovery time are not yet confirmed, so I cannot promise that the export will be restored before your meeting. I will send you a status update by 15:00, even if there is no further progress.
Could you share when the issue occurred, your browser and version, and any error message shown? Please leave out personal information or business data that is not needed for the investigation.
I am sorry for the disruption.
This is an edited example of an acceptable reply, not a promise that every AI will produce this wording. The authorized promise is an update, not a repair.
Repair a specific mistake without rewriting everything
| Draft wording | Why it is wrong here | Correction |
|---|---|---|
| “High system load caused the problem.” | The cause is unknown. | Say the report has been passed for investigation. |
| “The issue will be fixed by 15:00.” | 15:00 is the update deadline. | “I will send a status update by 15:00.” |
| “Please reinstall the application.” | No such troubleshooting step has been approved. | Request the known investigation details instead. |
A useful follow-up instruction is: “Change only the recovery promise in paragraph two. The 15:00 commitment is to communicate, not to restore service. Keep the other facts unchanged.”
At 15:00, no progress is still an update
If the team confirms that investigation is continuing but still cannot estimate recovery, the next message can be short:
As promised, here is the current status. The investigation is continuing, but the cause and recovery time remain unconfirmed.
Add another contact time only after agreeing it internally. Do not ask the AI to invent a reassuring deadline. The reader should finish this workflow with a draft that can be checked against a short, explicit list of facts and promises.
Prepare the request in Prompt Ready
In Prompt Ready, choose the writing/reply task and enter the received message together with the facts you may communicate. Include “15:00 is a status update, not a recovery deadline” in the material or conditions. Check the resulting request before copying it into your usual AI service.
Prompt Ready prepares the request. The AI you paste it into writes the reply, and you decide whether it can be sent. For repeated customer work, keeping those stages separate makes the same checks reusable without treating different customers as the same case.