Write the message's purpose in one sentence

Before opening the chat, finish this sentence: “After reading this, I want the recipient to…” The ending might be confirm a time, supply a missing file, or understand a delay. If you cannot name the purpose, a polished draft may still be confusing.

Next, list the facts that must survive the rewrite. Include names, dates, amounts, and whether a proposal has been agreed. A model should not turn “Could we meet Thursday?” into “Our Thursday meeting is confirmed.” These small changes can create real misunderstandings.

Give tone a practical definition

Tone labels alone are vague. Instead of asking for “professional,” say that you want direct language, a polite request, and no exaggerated enthusiasm. Include whether the reader already knows the background. This prevents the model from adding an unnecessary introduction or repeating familiar details.

For a fictional example, imagine a designer who needs a client's logo file before Friday. The email should name the missing item, explain the effect on the work, and ask for a clear next step. It should not invent a late fee, a contractual deadline, or a promise that delivery is guaranteed.

Example prompt
Draft an email to [recipient]. Purpose: request the final logo file. Confirmed facts: the layout uses a placeholder; I need the file before Friday to continue. Tone: polite and direct, not salesy. Keep it under 120 words. Ask them to confirm when they can send it. Add no fees or promises.

Review the facts before the style

Read the draft once for correctness and once for tone. On the first pass, compare every date, named item, and commitment with your brief. On the second, remove phrases you would never naturally use. A shorter message can still be warm if the request is considerate and clear.

If the model adds an explanation you did not provide, remove it or mark it as a question to resolve. Do not keep invented detail merely because it makes the email sound complete.

Make the final version yours

Replace placeholders, check the subject line, and verify the recipient before sending in your email application. GPT0 drafts text; it does not send the email or confirm that a person received it.

Save a reusable brief for common situations, such as a gentle reminder or a meeting request. Reuse the structure, not the facts. The next email may need a different deadline or level of formality, and those choices should come from you.

About this guide

Original examples are illustrative. This is AI-assisted content maintained for GPT0, not an independent product benchmark. Read our editorial approach.

Try a small task in GPT0

Start with a short prompt. Your device runs the model; WebGPU support and an initial download are required.

Open free chat