Professional email polisher prompt

A formal communication prompt that makes email drafts clearer, more polite, professional, and reviewable before sending.

April 27, 2026

Ready prompt

You are a communication editor who makes email drafts clearer, more polite, and more professional. Using the general details below, improve the existing email draft and make it reviewable before sending.

Email context: 
Current draft text: 
Recipient type: 
Desired tone: 
Main goal: 

Rules:
- Work with a general and safe business communication context.
- Do not add events, decisions, dates, prices, commitments, or approvals that were not provided.
- Adjust the text to the recipient type, main goal, and desired tone.
- Separate unclear points or items the user should review as short notes.
- Do not create fixed expectations about acceptance, replies, or positive outcomes.
- Prepare the output as an editable email draft before sending.

Output format:
1. Short communication goal summary
2. Improved main email draft
3. Shorter email alternative
4. Warmer and more polite alternative
5. More formal alternative
6. Subject line suggestions
7. Points to review before sending
8. Missing information notes if needed
9. Final checklist

ChatGPT Claude Gemini

How to use this prompt

This section helps you understand when and how to use this prompt more clearly.

What is this prompt used for?

This prompt helps make existing email drafts clearer, more polite, professional, and reviewable before sending. It prepares different email alternatives based on the message goal, recipient type, and desired tone.

Who is it for?

It is useful for teams communicating with customers, employees writing to managers, users replying to colleagues, supplier communication, and anyone who wants to make formal messages more organized.

When should you use it?

It can be used before sending an email when you want the message to sound clearer, more polite, or more professional. It can be adapted for follow-ups, information requests, customer replies, clarification requests, or polite declines.

Example use case

A user may want to explain a delayed response to a customer and share a new update. By adding the current draft, recipient type, and desired tone, they can get a more organized email draft.

Tips for better results

When polishing an email draft, clearly describe the context, recipient type, and main goal. Before sending, review real dates, decisions, links, attachments, and process details separately.

Additional usage questions

Can this prompt be used for customer emails?

Yes. It can be adapted for customer updates, follow-ups, thank-you messages, clarification notes, or polite replies.

Can this prompt create a shorter email alternative?

Yes. It can prepare a shorter, more formal, or warmer alternative alongside the main draft.

Preview

Example output

This example shows how the prompt can make an email draft more professional.

Example variables

Email context: Customer update after a delayed response
Current draft text: Hello, sorry for the late reply. We checked the issue and will update you tomorrow.
Recipient type: Customer
Desired tone: Polite, professional, and clear
Main goal: Explain the delay politely and share follow-up information

Short communication goal summary

The goal of this email is to acknowledge the delayed response politely, confirm that the topic is being reviewed, and set a clear expectation for the next update.

Improved main email draft

Hello, Thank you for your patience, and please accept our apologies for the delayed response. We have reviewed the topic you shared and are continuing the necessary evaluation. Our team is currently checking the relevant details. We will share a clearer update with you by tomorrow. Thank you for your understanding. Best regards,

Shorter email alternative

Hello, Thank you for your patience. We apologize for the delayed response. We have reviewed the topic and are continuing our evaluation. We will share an update with you by tomorrow. Thank you.

Subject line suggestions

1. Update Regarding Your Request 2. Follow-up on the Topic You Shared 3. Status Update on Your Message

Points to review before sending

Is the timeline for tomorrow accurate? Is the customer request understood correctly? Are any attachments or links needed? Does the follow-up message match the internal process?

This example is an editable draft before sending. Real dates, process details, customer context, and company tone should be reviewed separately.

Usage tips

1
A clear email context helps adjust the message in a more suitable tone.
2
Adding the recipient type helps improve greeting, closing, and formality level.
3
Before sending, you can review the email against real event, date, attachment, link, and decision details.