Ask AI to distinguish a sender’s request from background detail

Define the two labels before you paste anything

Use “direct ask” for the action the sender wants from you, including a decision, answer, approval, or task. Use “background” for information that explains the situation but does not itself ask you to act. A detail can be important without being a request: a project deadline, for example, may explain urgency while the actual ask is to confirm a meeting time.

Be precise about whose request you mean. An email may quote a customer, summarize a colleague’s suggestion, and then ask you to review a draft. The sender’s request to you is not automatically the same as every request mentioned inside the message.

Give AI a narrow, neutral instruction

If AI assistance is available in your account and plan, ask it to extract and label information rather than infer intent or recommend a decision. Request the sender’s exact action in plain language, relevant supporting context, and any missing detail that makes the ask uncertain. Ask it to say “unclear” when the email does not establish something.

For a message with several actions, ask for each one separately and identify who is expected to act, if the email says. Avoid prompting with a preferred interpretation, such as “Explain why they want me to approve this.” That wording can steer the summary toward approval even if the sender only asked for feedback.

Prompt: Separate the sender’s direct request from background information. List each action the sender asks me to take, if any. Do not treat quoted requests or possible next steps as requests to me unless the sender says so. Mark anything uncertain and do not infer a deadline or commitment.

Try it on a mixed-purpose message

Suppose a sender describes a postponed launch, notes that a supplier has not confirmed delivery, and asks whether you can review a revised schedule by Thursday. The postponement and supplier update are context. Reviewing the schedule is the direct ask. Thursday is a deadline for that review, not necessarily a promise that the launch will happen then.

If the message also says, “We may need to move the launch again,” that is a possibility, not a confirmed change or an instruction to notify anyone. Ask AI to preserve those distinctions. A useful output should not turn “may,” “could,” or a quoted proposal into a settled fact.

Sender: Jordan Lee <jordan.lee@example.com>
To: Casey Morgan <casey.morgan@example.com>
Subject: Revised launch schedule

The launch moved after the supplier delayed its delivery. We still do not have a confirmed arrival date. Could you review the revised schedule by Thursday? We may need to move the launch again if delivery slips.

Check the labels against the source

Return to the original email, not just the AI output. Find the words that support each listed action. Check who is speaking, who is being addressed, whether the sentence is quoted, and whether a question is actually directed to you. A summary can omit a qualifier or attach a deadline to the wrong task.

Verify names, dates, recipients, promises, and financial information especially carefully. If AI says the sender approved a cost, for example, locate the sentence that says so. If no clear sentence supports that interpretation, treat it as unconfirmed. Do not let a confident-sounding label substitute for evidence in the message.

Use a quick evidence checklist

Before responding, make sure each proposed action has a clear source in the email. Separate what the sender asks you to do from what they report, suggest, or predict. If you cannot point to the relevant wording, leave the item out or mark it as uncertain.

A short manual check is useful when an email has forwarded text, several recipients, multiple questions, or an ambiguous “we.” If responsibility is unclear, ask the sender to clarify who should act and by when rather than assigning yourself a task based only on AI’s interpretation.

• Can I point to the sentence that contains the sender’s direct ask?
• Is the action directed to me, rather than quoted or assigned to someone else?
• Have I kept background, suggestions, and possible outcomes separate?
• Do the names, dates, conditions, and amounts match the original?
• If the ask is ambiguous, have I identified what needs clarification?

Decide only after the distinction holds up

Once the labels match the original, decide how to respond to the actual request. You might answer it, accept or decline it, ask a follow-up question, or explain that you need more information. Context can help shape your response, but it should not silently become an additional assignment or commitment.

You can confirm the process worked when you can identify the sender’s requested action in the original message, distinguish it from the surrounding explanation, and explain any unresolved uncertainty. If the AI summary and the email disagree, rely on the original wording and clarify with the sender when necessary. AI can help organize a message; it cannot establish intent that the sender did not make clear.