About this article
This article was created using an automated generation workflow utilizing generative AI. Official Microsoft documentation was reviewed on October 20, 2026, and prompts and verification steps using fictional data were prepared. Execution on the actual Copilot interface has not been performed.Verification Status: 📘 Official Information Confirmed – Prompt Execution Unverified
- Supported Environments, Capabilities, and Limitations (Official Confirmation: October 20, 2026)
- Provide the original email and the purpose of the reply together
- Evaluate missing conditions before drafting the reply
- Revise the phrasing so that the recipient can easily answer
- Change one element and observe the conditions under which a date appears in the reply
- Organize long email quotations
- When reducing questions, indicate what has been temporarily assumed
- Scope of verification before actual transmission
- Official Information and Primary Sources
Supported Environments, Capabilities, and Limitations (Official Confirmation: October 20, 2026)
| Item | Scope and Target of This Example |
|---|---|
| Product / Entry Point | Microsoft Copilot Chat for Work (formerly Microsoft 365 Copilot Chat).Assuming standard chat on the Web versionAssuming standard chat on the Web version |
| Account / License | A work account authorized for use within the organization. Verify availability with your license and administrator settings. Personal Copilot accounts are out of scope for this example. |
| Additional License / Billing | Additional features within Office apps and pay-as-you-go agents are not used in this example. Do not assume that features requiring additional licenses are available. |
| Input / Storage Location | Fictional text is pasted directly. Local paths, OneDrive, SharePoint, and inboxes are not connected. |
| Actions to Test | Referencing, organizing, comparing, and drafting text based on the input. Content must be manually cross-checked against the original text by a human. |
| Out of scope for this example | File search, direct document editing/moving/deleting, email sending, and enterprise system registration |
| Limits and availability status | Does not assume preview functionality. Figures for input length, frequency, region, and screen differences, as well as physical device builds, are unverified. Break up long inputs, and verify availability on the screen. |
| Information management | Start by using dummy data only. Before expanding to business information, check organizational permissions and information classification. Do not rely solely on prompt instructions as a guarantee for access control or disabling web searches. |
Even with a short email like 'Please send the materials,' work cannot begin if the target, deadline, and submission format are unclear. If you draft a polite reply first, a single phrase such as 'Understood' may inadvertently accept unconfirmed conditions. Have Copilot Chat separate the request content and missing conditions before drafting the reply.
Provide the original email and the purpose of the reply together
This example does not connect to the Outlook inbox. Paste a dummy email body into the chat to create a draft for review. Sending emails, registering calendar events, and retrieving attachments are also not performed. By simply organizing the text, you can test what needs to be asked before replying.
次の架空メールについて、先に確認事項、その後に返信案を作ってください。 元メールだけを根拠にし、添付資料があると仮定しないでください。 1. 確定している依頼内容 2. 不足条件：作業開始に必須／後から調整可能、の2区分 3. 相手が答えやすい確認質問を3件以内 4. まだ納期を約束しない返信案を200字程度 依頼者の意図や感情は推測しないでください。 【架空メール】 件名：来月の説明会資料について 来月の説明会で使う比較資料をお願いします。 昨年版を参考に、最近の状況を反映しておいてください。 参加者はこれから調整します。 できれば早めに確認したいです。
The request is for comparative materials for an information session. However, the comparison targets, location of last year's version, date of the information session, and desired date for the first draft are not specified. 'Soon' is not a specific deadline. The goal of this trial is to keep these as questions rather than converting them into dates.
Evaluate missing conditions before drafting the reply
Even if the output is fluent, it does not necessarily determine the materials that need to be prepared. For example, if a sentence like 'I will submit it by next Friday' is included, a commitment not present in the original email has been added. Verify separately whether the phrasing is naturally polite and whether it aligns with the facts.
| Points to observe | Expected handling in this example |
|---|---|
| First draft deadline | Ask as an unspecified date and time |
| Comparison targets | Confirm the targets and comparison items |
| Last year's version | Confirm the source and available version |
| Participants | Keep as undetermined and do not assign roles arbitrarily |
| Current status | Verify the update scope and baseline date |
Asking everything at once can make it difficult for the recipient to answer. Consolidate the first three questions into items that have a major impact on getting started. For example, grouping the comparison target and perspective into one question, the first draft deadline and event date into another, and the sharing destination of last year's version into a third can help reduce back-and-forth communication.
This does not mean that limiting questions to three is always the correct approach. If there are four critical conditions, it is necessary to make the judgment to add a question. The three questions generated by the AI are candidates for organization, and it is the handler's responsibility to determine the business priorities.
Revise the phrasing so that the recipient can easily answer
Just saying "Please provide details" leaves the requester wondering what to write. Specify the requested information, such as "Please provide the comparison targets and the specific items you wish to compare." When listing candidates, write them in a way that makes it clear they are examples rather than confirmed facts.
When asking about deadlines, it is helpful not only to ask "By when?" but also to separate the first draft review from the final submission. Even if the date of the briefing session is known, the preparation period cannot be determined if there is no allowance for preliminary review. Before inserting a deadline into a draft reply, clarify what kind of deadline it is.
Mentioning last year's version does not necessarily mean an attachment exists. Rather than having the AI write "I have checked the attachment," ask where it is shared. Proceeding under the assumption that the AI can read materials not entered into the chat may lead to fabrications creeping into the content of the materials.
Change one element and observe the conditions under which a date appears in the reply
Replace the end of the original email with "Please share the first draft by noon on November 6th" and test the same instruction in a new conversation. In this case, the deadline for the first draft is expected to move to the confirmed items list. The comparison targets and the location of last year's version will still need to be verified.
Check whether just adding a single date causes the system to treat the volume and scope of the material as fully determined. Deadline information is only meant to fill the deadline field and does not resolve the ambiguity of the entire request. Observing limited output changes makes it easier to spot misinterpretations.
Furthermore, compare whether the output promises "We can submit this" or simply acknowledges the fact with "I have confirmed the deadline." At a stage where the workload is unknown, understanding the specification of a deadline is different from judging that the task can be completed by that deadline. Replies must maintain this distinction.
Organize long email quotations
In practice, past emails may be quoted across multiple levels, leaving behind obsolete deadlines. With each quote, separate the date, sender, and body, and instruct the system that "the latest explicit change takes precedence." If the deadlines still conflict, avoid picking one and instead output them to a conflict list.
There are also instructions whose meaning cannot be grasped from the body text alone, such as "regarding the matter from the other day." If Copilot supplies natural-sounding explanations, prune that section and revert to asking questions for clarification from the other party. Make sure not to confuse improving the readability of an email with inventing missing background information.
The process of adjusting the tone of the text should be left to the end. By asking to "make it concise and polite for external use" only after the facts and questions have been settled, you can separate content finalization from stylistic adjustment. Rewriting text to be softer too early can sometimes weaken the conditions or negative expressions of a request.
When reducing questions, indicate what has been temporarily assumed
If there is a scope that can proceed without asking the other party, record the provisionally set conditions. For example, you can prepare just the columns of a comparison table without needing to determine the actual contents of the comparison targets. Separating the parts that can be started from the parts that require an answer makes it easier to utilize waiting time effectively.
When including tentative content in a reply, frame it not as a decision that these conditions are acceptable, but as a proposal to prepare based on these conditions. Whether the recipient's silence constitutes approval requires a business agreement. Do not establish approval procedures using AI-generated text alone.
Furthermore, inquiring about the background of a request is not always mandatory. While knowing the intended use of a document makes it easier to select the right perspective, asking the recipient for a lengthy explanation increases back-and-forth communication. Prioritizing questions that can be directly reflected in the deliverable—such as 'What is the main point you want to convey at the briefing?'—leads to practical outcomes.
When reusing a draft reply, ensure that previous recipients and dates are not left in. Rather than greeting phrases, the template structure should follow the order of confirmed items, missing conditions, and clarification questions. Leaving project-specific information blank and maintaining a separate pre-send review section helps prevent errors such as carrying over past commitments to a different project.
Scope of verification before actual transmission
During the trial phase, use only the fictional emails provided above. When inputting business emails, verify the services and information classifications authorized by your organization, and review not only the body text but also the quotation history, signatures, and contact details. Subject lines and attachment names may also contain confidential information, so simply deleting names from the body text is not sufficient.
The generated reply draft must be reviewed by the responsible person before being entered into the transmission screen. Check the recipients, CCs, attachments, deadlines, and scope of acceptance, and carefully reread commitment terms such as 'I will handle this' or 'I will complete this.' Even if a draft within a chat is completed, it does not mean the email has been sent.
When measuring effectiveness, record not only the drafting speed but also the number of pre-send revisions and the number of review exchanges. If revisions for politeness decrease but the number of corrections for incorrect commitments increases, it cannot be considered an improvement. Treat the specificity of clarification questions as a key metric of success.
Asking about all unclear points places a heavy burden on the recipient, while asking nothing increases rework. Distinguishing between conditions essential for starting and conditions that can be adjusted later is done to avoid both outcomes. The role of AI is not to substitute for decision-making, but to lay out decision factors.
The first thing to establish in a reply is not a polite greeting, but the scope of work. Once the target, version, and deadline are aligned, the necessary confirmations can be communicated even in a short text. Retaining the wording of the original email as a basis and transferring only the confirmed commitments to the reply clarifies how to begin the task.
Official Information and Primary Sources
Product scope and input methods refer to official documentation. Fictional data, prompts, expected examples, and checklists are verification proposals for this article and do not constitute output examples guaranteed by Microsoft.
