Audit email tone for harshness, ambiguity, and passive aggression

المؤلف: AILesson5 دقائق للإعدادتم اختباره مع:ChatGPTتمت المراجعة: 2026-08-28

إجابة سريعة

Identify wording risks in context and revise tone without weakening facts or boundaries. قدّم: Draft email, Relationship and history, Required intent and boundaries. النتيجة المتوقعة: A phrase-level tone audit, risk explanation, and meaning-preserving revision.

أضف سياقك

يبقى نصك في هذا المتصفح. لا يرسله AILesson Prompts إلى نموذج أو خادم.

Draft emailRelationship and historyRequired intent and boundaries

الأمر الخاص بك

تبقى الحقول غير المعبأة ظاهرة كعناصر نائبة، لذا يمكنك نسخ الأمر وتحريرها

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.

جرّب في المختبر

خاص افتراضيًايتم تجميع الأمر محليًا في متصفحك. تجنب وضع معلومات سرية في أي خدمة ذكاء اصطناعي ما لم تسمح مؤسستك بذلك.

من المدخلات إلى النتيجة

مثال عملي

شاهد كيف يحول السياق الملموس هذه الوصفة إلى نتيجة قابلة للاستخدام

المدخل الفعلي

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.

مثال على المخرجات

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]

لماذا يعمل هذا

1
Phrase-level review distinguishes real tone risk from necessary directness.
2
Explicit invariants keep a friendlier revision from weakening accountability or scope.

تحقق من النتيجة

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?

استخدمها بثقة

الأسئلة الشائعة

إجابات عملية حول متى تستخدم هذه الوصفة، وما الذي تقدمه، وأين لا تزال المراجعة البشرية مهمة

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.

المزيد من طرق الاستكشاف