Author: AILesson4 min setupTested with:ChatGPTReviewed: 2026-08-28
Quick answer
Convert an email into a scannable chat message while preserving facts, boundaries, decisions, and response expectations. Provide: Formal email, Chat channel and relationship, Meaning and action invariants. Expected result: A channel-ready message with preserved-meaning audit and thread or attachment handling.
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Adapt the formal email into an instant message for the specified channel and relationship.
Email, subject, recipients, quoted context, links, attachments, and signature:
[email]
Channel, visibility, relationship, time zone, notification norms, and tone:
[channel]
Facts, dates, numbers, conditions, decisions, requests, refusals, deadlines, links/attachments, confidentiality, and fixed wording:
[invariants]
Remove email-only ceremony, signatures, duplicated subject context, and long transitions, but do not remove qualifications, scope, authority, or an inconvenient request. Lead with why the recipient is being messaged, use short paragraphs or bullets only where chat readability improves, and put the requested action with its exact timing in a visible final line. Clarify attachment or thread location rather than saying attached when the channel has no file. Do not turn a conditional date into a commitment, make silence equal consent, overuse urgency, mention people unnecessarily in a group, or split one coherent request into notification-heavy fragments. Return: one-message version; optional two-message version only if channel norms support it; preserved-meaning audit; removed email conventions; visibility/privacy warning; and reply options if a simple acknowledgement would help.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Formal email
Subject: Review required — supplier comparison before 4 September
Dear Mina, Following our procurement discussion, I have completed the first comparison of the three shortlisted translation suppliers. The workbook is available in the Procurement channel under Files > FY26 > Translation comparison.xlsx. Prices exclude VAT and two suppliers have not confirmed data-hosting location, so the sheet is not ready for selection. Could you please review the scoring weights and add comments in column N by 16:00 London time on 4 September? If that timing is not possible, please tell me by 2 September so we can move the review; silence should not be treated as approval. Please do not forward the workbook outside the procurement group. Kind regards, Arun
Chat channel and relationship
Microsoft Teams direct message from Arun to Mina. They work together regularly. Calm, concise, professional but conversational. Mina is in London; Arun is in Singapore. One message preferred, no @mention needed in direct chat.
Meaning and action invariants
Keep: three suppliers; first comparison only; workbook path; prices exclude VAT; two hosting locations unconfirmed; not ready for selection; review scoring weights and comment in column N by 4 Sep 16:00 London; if unavailable tell Arun by 2 Sep; silence not approval; procurement-group confidentiality. Do not imply Mina approved suppliers or that Arun will choose.
Example output
Hi Mina — the first comparison of the three shortlisted translation suppliers is ready in Procurement > Files > FY26 > Translation comparison.xlsx.
A couple of limits before review: prices exclude VAT, and two suppliers have not confirmed their data-hosting location, so this is not ready for a selection decision.
Could you review the scoring weights and add comments in column N by 4 September, 16:00 London time? If that timing won’t work, please let me know by 2 September so we can move the review. No reply won’t be treated as approval. Please keep the workbook within the procurement group.
Meaning audit: all three-supplier scope, file path, VAT and hosting caveats, no-selection boundary, requested review, two dates/time zone, no-silence approval, and confidentiality remain. Removed: subject line, formal salutation, closing, signature, and “following our discussion.” Privacy: suitable for direct chat; do not paste into a broader channel. Suggested quick replies: “I can review by 4 Sep” or “I need another review time.”
Why this works
1
Meaning invariants keep channel compression from weakening conditions or changing commitments.
2
One visible action line fits chat scanning while preserving an explicit response expectation.
Check the result
Are every material fact, condition, refusal, date, number, and action unchanged?
Does the message fit channel visibility and notification norms without exposing unnecessary information?
Can the recipient see exactly what response or action is requested and by when?
Evidence behind the method
Sources and quotations
Primary sources that support specific design choices in this recipe. They do not guarantee a particular AI result.
The instruction to remove ceremony and use short, precise sentences follows Microsoft guidance that concise language supports scanning while precise words reduce ambiguity.
Concise, clear sentences save space, are easy to understand, and facilitate scanning.
Practical answers about when to use this recipe, what to provide, and where human review still matters
What should I prepare before using “Adapt a formal email for instant messaging”?
For “Adapt a formal email for instant messaging,” prepare Formal email, Chat channel and relationship, and Meaning and action invariants. 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 “Adapt a formal email for instant messaging” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A channel-ready message with preserved-meaning audit and thread or attachment handling—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 “Adapt a formal email for instant messaging”?
The published test record for “Adapt a formal email for instant messaging” 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.
ChatGPT