How to write an email prompt that keeps the facts and conditions
Build and check an email prompt with fictional delivery facts, deadlines and explicit limits on commitments.
Article language: English

In this article
“Write a professional email” leaves almost every decision to the model. Who is it for? What response do you need? Which commitments already exist? The result can sound polished while offering a discount nobody approved.
Let's set a clear boundary. The company, situation and all details below are fictional. A furniture maker is waiting for a supplier to confirm a delivery so it can plan the installation team's work.
Write an email to the supplier's order contact.
Goal: obtain confirmation of the delivery date for order M-204.
Facts: 12 worktops were ordered; the offer says delivery on 20 November;
we have not received dispatch confirmation; installation is planned for 23 November.
Request a reply by 17 November at 12:00.
If delivery on 20 November is impossible, ask for the nearest realistic date.
Tone: calm and factual, without blame. Maximum 140 words.
Include a subject line. Do not promise extra payment, a discount or an order change.
Do not invent the recipient's name or a legal basis.
A prompt is an instruction given to a model. This one is detailed because each sentence settles a question the model should not settle for you.
Separate the goal from the subject
“Delivery of worktops” is the subject. The goal is a reply within a specified time. If you give only the subject, the model may write a polite reminder with no actual question. The recipient can read it and still not know what you need.
Microsoft's prompt guidance describes goal, context, source and expected result. This is useful beyond Copilot: it describes a person's task rather than a secret syntax for one product.
Here the source is the supplied facts, the context is the planned installation, and the output is a short email with a subject line. The desired response is confirmation or an alternative date. “Professional” alone does not convey that.
Read a version you could actually use
A suitable illustrative answer might be:
Subject: Please confirm delivery of order M-204 Hello, Could you please confirm whether the 12 worktops in order M-204 will be delivered on 20 November, as stated in the offer? We have not yet received dispatch confirmation, and installation is planned for 23 November. Please reply by 12:00 on 17 November. If delivery on 20 November is not possible, please let us know the nearest realistic date. Thank you.
This is an author-written example, not a model test. It keeps the uncertainty: the date appears in the offer but delivery has not been confirmed. It does not turn the planned installation into a contractual penalty.
Now consider an intentionally incorrect fictional draft: “We confirm delivery of M-204 on 20 November. We can pay extra for urgent shipping. Please contact us at a convenient time.” It sounds like an email, but changes the status of the agreement and removes the response deadline.
Compare the flawed draft with the M-204 facts at the start of this article.
Separate statements into: supported by the material, new commitment,
unconfirmed fact, and important condition omitted.
For each error, point to the relevant source fact.
Then correct only the incorrect parts.
Keep the request for a reply by 12:00 on 17 November.
Do not agree to extra payment or confirm delivery for the sender.
The result should remove the proposed payment and turn delivery confirmation into a request for confirmation. Check each change separately: a correct reply deadline does not cancel out an invented financial commitment. The guide to checking AI answers (in Polish) explores the difference between source and conclusion.
Cross out three kinds of additions
First look for new facts. Phone numbers, names, dates of earlier conversations and reasons for delay need support in the material. If you did not provide them, remove or independently confirm them.
Next check new commitments. “We can accept a higher price” sounds accommodating but changes the negotiation. “We confirm the new date” would be worse when the supplier has yet to provide it. Politeness does not need its own budget.
Finally assess tone for the relationship. A long-standing contact does not need a ceremonial opening about an “exceptionally fruitful partnership” every time. Ask for inflated language to be removed while retaining facts. OpenAI recommends specifying tone and refining instructions; identifying a passage to change helps more than simply asking for “better”.
Edit an existing email under control
For your own message, try a shorter instruction:
Improve the readability of the email below.
Keep its meaning, numbers, dates, conditions and scope of commitments.
First show the revised version. Then list proposed changes of meaning
for separate approval; do not introduce them into the email.
If a sentence is ambiguous, identify it and ask one question.
[Paste the message after removing information you may not share.]
Read the result line by line before sending. An instruction to preserve meaning is not proof that it did. For confidential correspondence start with the rules for safe AI data use at work (in Polish). If the email follows a meeting, first separate decisions from proposals in the notes (in Polish).
Sometimes uncertainty appears only in the supplier's answer. Add this fictional message: “Dispatch may take place on 19 November. We will confirm after receiving the goods from the manufacturer. The delivery date depends on the carrier.” It does not establish that the worktops will arrive for installation on 23 November.
Write a reply to the supplier using the new fictional message.
We need to establish delivery before installation planned for 23 November.
Separate the possible dispatch date from the delivery date.
Ask for confirmation of a realistic delivery date and the date
when the supplier can determine it with binding certainty.
Do not accept an installation schedule change or invent a delivery date.
After the email, identify which information remains conditional.
Read the draft as the recipient would. They should know what they have not yet confirmed. “Thank you for arranging the date” would imply the matter is settled; replace that polite sentence with a more accurate one.
If an automated process will handle messages, establish human approval for actions (in Polish). Approval of a good template does not replace checking the recipient, current agreement and each message. A sent email cannot be turned back into an unsent draft.
You can also mark exactly three things in the draft: the action requested from the supplier, their reply deadline and the delivery condition. Ask someone unfamiliar with the case to explain them in their own words. If they confuse dispatch with delivery, change the sentence before sending. The recipient may not know your organisation's internal abbreviations either. This readability check complements the comparison with source facts and requires no extra app.
For a first exercise without company accounts or real messages, see how to start using AI for free (in Polish). The AI course (in Polish) teaches through practical tasks (in Polish), and Aeneia describes the wider project. Before sending today's message, underline its most important request: the recipient should find it without searching.
*The original says the prompt sources were checked on 30 October 2026. The example and model email are fictional training material, not a model-test result.*










