How to use the Email Politeness Checker.
Politeness depends on the relationship and purpose. Make requests specific and respectful without weakening a necessary deadline or boundary.
Make the workflow fit your task.
Identify the relationship, request and non-negotiable deadline. Replace accusation or unnecessary pressure with respectful wording while preserving the action the recipient needs to take and the reason it matters.
- What you provide
- Draft and relationship context.
- What you get
- Abrupt or ambiguous language with suggested edits.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
You still haven't sent it. I need the report by 15:00.
Completed example
Could you send the report by 15:00 today? I need it for the review meeting.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can a polite email still set a firm boundary?
Yes. State the boundary plainly and courteously. Respectful language does not require making a necessary condition optional.
Why did the revised request become too weak?
Restore the concrete action and deadline. Avoid adding vague phrases that change an instruction into an uncertain suggestion.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑