Audit email tone for harshness, ambiguity, and passive aggression

Autor: AILesson5 min de configuraçãoTestado com:ChatGPTRevisado em: 2026-08-28

Resposta rápida

Identify wording risks in context and revise tone without weakening facts or boundaries. Forneça: Draft email, Relationship and history, Required intent and boundaries. Resultado esperado: A phrase-level tone audit, risk explanation, and meaning-preserving revision.

1

Adicione seu contexto

Seu texto permanece neste navegador. O AILesson Prompts não o envia para um modelo ou servidor.

2

Seu prompt

Campos não preenchidos permanecem visíveis como marcadores de posição, para que você ainda possa copiar e editar o prompt

Audit the draft email for harsh, ambiguous, or passive-aggressive language.

Draft:
[draft]

Relationship, power dynamics, history, and sensitivities:
[context]

Required action, firmness, facts, and boundaries:
[intent]

Evaluate wording in context rather than assuming any direct sentence is rude. Identify exact phrases that may imply blame, sarcasm, threat, false consensus, hidden accusation, vague urgency, or unclear ownership. For each, explain the likely reading, severity, and a meaning-preserving alternative. Also flag ambiguity unrelated to tone. Then provide a revised email that keeps every required fact, deadline, refusal, escalation, and request. Do not erase legitimate accountability, add excessive apology, diagnose the sender, or claim how the recipient will feel.
Experimente no Playground
Privado por padrãoA montagem do prompt acontece localmente no seu navegador. Evite colocar informações confidenciais em qualquer serviço de IA, a menos que sua organização permita.

Da entrada ao resultado

Um exemplo prático

Veja como um contexto concreto transforma esta receita em um resultado útil

Entrada real

Draft email
As I already explained twice, the figures were due yesterday. I’m sure you understand how this makes the whole team look. Please send the correct file ASAP, or I’ll have no choice but to take this further. Thanks in advance for finally sorting it out.
Relationship and history
A project lead writing to a peer team lead. Two prior reminders were sent, but neither confirmed a deadline. The received file has March rather than April figures. Escalation to both managers is allowed if the corrected file is not received by 15:00 today.
Required intent and boundaries
State that the file contains March data, request April data by 15:00 today, and say both managers will be included after that time. Keep the message firm and brief.

Exemplo de saída

Tone risks: “already explained twice” assigns blame without helping identify the error; medium risk. “Makes the whole team look” uses shame and is unrelated to the requested correction; high risk. “No choice but to take this further” is a vague threat; replace it with the authorized escalation and exact trigger. “Finally sorting it out” is sarcastic; high risk. Clarity issue: “correct file” does not say that April figures are required, and “ASAP” conflicts with the available exact deadline. The claim that figures were due yesterday is unsupported by the history and should be removed.

Revised email: Subject: April figures needed by 15:00 today

Hi—The file received contains March figures. Please send the version containing April figures by 15:00 today. If it is not available by then, I will include both of our managers so we can agree the next step. Please let me know before 15:00 if there is a blocker or if I have referenced the wrong file.

Thanks, [Name]

Por que isso funciona

  1. 1

    Phrase-level review distinguishes real tone risk from necessary directness.

  2. 2

    Explicit invariants keep a friendlier revision from weakening accountability or scope.

Verifique o resultado

  • Are tone findings tied to exact phrases and the supplied context?

  • Does the revision preserve every required fact, boundary, and action?

  • Were clarity problems separated from interpersonal tone?

Use com confiança

Perguntas frequentes

Respostas práticas sobre quando usar esta receita, o que fornecer e onde a revisão humana ainda é importante

What should I prepare before using “Audit email tone for harshness, ambiguity, and passive aggression”?

For “Audit email tone for harshness, ambiguity, and passive aggression,” prepare Draft email, Relationship and history, and Required intent and boundaries. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Audit email tone for harshness, ambiguity, and passive aggression” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A phrase-level tone audit, risk explanation, and meaning-preserving revision—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Audit email tone for harshness, ambiguity, and passive aggression”?

The published test record for “Audit email tone for harshness, ambiguity, and passive aggression” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Mantenha o trabalho em andamento