Email Prompt Builder Guide

Define the action before the tone

This tutorial prepares a room availability inquiry. The page returns a drafting prompt, not a finished email, and has no sending function. Decide what answer you need from the recipient before choosing how formal the message should sound.

Step 1: separate inquiry from commitment

Before: “Book a room.” After: “Ask whether a quiet meeting room is available; do not confirm a booking.” Enter the revised purpose and “Facilities team” as recipient. This wording gives the eventual assistant a useful boundary: request information without promising a reservation.

Step 2: generate the drafting brief

Use the English field values below, select Request and Formal, then generate. Read the exact prompt, especially the purpose and signature placeholder requirement. No actual email body has been written yet. Add a subject-line requirement to the purpose if your workflow needs one.

Input and selections
Recipient: Facilities team
Purpose: Ask whether a quiet meeting room is available; do not confirm a booking.
Type: Request
Tone: Formal

Exact tool output
Write a request email.

Recipient: Facilities team
Topic/Purpose: Ask whether a quiet meeting room is available; do not confirm a booking.

Use formal, professional language appropriate for business communication.

Include:
- Appropriate greeting
- Clear body with the main message
- Professional closing
- Signature placeholder

Step 3: evaluate a draft elsewhere

After using the prompt with an assistant, compare the draft with a simple editorial benchmark: “Could you confirm whether a quiet meeting room is available? Please do not reserve it yet.” This hand-written example is not tool output. It makes the desired distinction visible.

Step 4: perform the sending review

Check the recipient, requested action, and any claims about availability. Replace the signature placeholder yourself. If you need to include scheduling details, provide only confirmed information before sending through your own email application.

Mistake 1: copying the instructions as the email

The output begins by telling an assistant what to write. It is an intermediate request; sending it to the intended recipient would expose your drafting instructions instead of communicating the inquiry.

Mistake 2: relying on tone to set boundaries

Formal wording does not prevent an invented promise. Put the boundary in the purpose and verify that the eventual draft preserves it.

Worked example: follow up without assuming a date

The timetable example uses Follow-up and Friendly, with a named recipient role. Notice the exact Topic/Purpose line: the instruction not to assume a date is preserved alongside the request. The builder does not consult a calendar or check whether a timetable exists. A later draft should ask for information rather than announce an invented schedule.

Input and selections
emailType: followup
recipient: Workshop coordinator
topic: Ask whether the revised timetable is available. Do not assume a date.
tone: friendly

Exact tool output
Write a follow-up email.

Recipient: Workshop coordinator
Topic/Purpose: Ask whether the revised timetable is available. Do not assume a date.

Use a warm, friendly but still professional tone.

Include:
- Appropriate greeting
- Clear body with the main message
- Professional closing
- Signature placeholder

Worked example: leave the recipient unspecified

For a volunteer thank-you, leave Recipient empty and choose Casual. The recipient line disappears, but the fixed checklist still asks for a professional closing and a signature placeholder. Casual therefore changes one tone sentence, not the whole structure. Supply the greeting and sender details when reviewing a draft from another service; this output is only its writing request.

Input and selections
emailType: thankyou
recipient: (empty)
topic: Thank the volunteers for sorting donated books on Saturday.
tone: casual

Exact tool output
Write a thank you email.

Topic/Purpose: Thank the volunteers for sorting donated books on Saturday.

Use a relaxed, conversational tone while remaining respectful.

Include:
- Appropriate greeting
- Clear body with the main message
- Professional closing
- Signature placeholder

Mistake 3: expecting delivery or attachments

The page has no sending or attachment workflow. Mentioning a file in Topic/Purpose only places that statement in the request; verify the actual attachment when composing your email.

Mistake 4: treating whitespace as an empty recipient

Recipient uses a simple truthiness check, unlike the trimmed topic check. Spaces can still produce a recipient line. Clear the field completely when you want to omit it.

Mistake 5: expecting automatic cultural adaptation

The presets contain generic English instructions. They do not infer titles, hierarchy, or regional email conventions from a recipient name; add necessary context yourself.

Tips for better results

• Put the request and any prohibited commitments together in Topic/Purpose.
• Inspect the type and tone sentences as well as your own input.
• Review every requested checklist item in the eventual draft, particularly the signature placeholder, before sending it through your email application.