Draft an inbox handoff queue
Get the source data and prepare the review

Documentation-verified component path; proposed adaptation, not tested

WHAT WAS CHECKED
Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Menus/features are vendor-documented; prompts, field maps and human gates are editorial adaptations. No actual client work, account login, installation, connection, external write or site edit occurred.

BEFORE YOU START
- Existing firm-approved Microsoft Copilot work access in Outlook with permission for the chosen threads; account/tenant/feature access must be checked.
- Bounded manually selected thread list, lawyer-approved routing policy and alias role/owner matrix. This is not a claim of exhaustive inbox discovery.
- Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized.

DATA ACQUISITION LIMITS
- Summary by Copilot is native thread summarization; it does not establish mailbox completeness or safe delegation. The exact classification prompt below is an editorial adaptation.
- No output changes folders, rules, importance, completion status or ownership automatically. Missing source references or ambiguous/consequential requests require attorney review.

WHEN THIS CAN RUN
Blocked until actual sources, permissions and required human approvals are supplied; no real inputs were available in this verification.

STEP 1: Read the selected thread with native AI
Tool: Outlook Copilot
Open: Open selected conversation > Summary by Copilot (or Summarize)
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Use only a thread approved for the firm’s existing Copilot processing. Review the generated summary and open available numbered citations to the source messages. Repeat only for the bounded thread list and record capture time. If Copilot is unavailable, read the messages manually; do not claim an AI route ran.

Expected output: Thread summary grounded in the selected conversation, subject to human completeness checking.
Use it next: Use the verified thread identity and approved routing policy in the Outlook Copilot chat step.
Check: Review all messages in the thread for omitted requests or context; native summaries are not evidence of absence.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://support.microsoft.com/en-us/outlook/copilot-pages/summarize-an-email-thread-with-copilot-in-outlook
https://support.microsoft.com/en-us/outlook/frequently-asked-questions-about-copilot-in-outlook

STEP 2: Ask for a source-linked routing proposal
Tool: Outlook Copilot Chat
Open: Copilot icon in Outlook navigation header > chat prompt field
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Paste the exact thread reference and the approved client-free routing policy/role matrix into the prompt. Keep the request scoped to this chosen thread. If the chat cannot resolve the exact thread or returns uncheckable source references, stop that row and perform manual review.

PASTE THIS PROMPT
Use only this explicitly selected email thread [VERIFIED THREAD REFERENCE] and this approved routing policy/role matrix [PASTE POLICY]. Return message/source reference,explicit requested action,proposed queue staff|attorney|FYI|waiting,approved owner role or null,evidence quote and uncertainty. Put ambiguous, potentially consequential and deadline-related items in attorney review. Do not infer a legal deadline, legal duty, matter association or substantive urgency. Do not search unrelated matters, forward, reply, create rules, move, hide, delete or mark messages complete. Report missing thread/source access rather than guessing.

Expected output: Proposed routing/action/owner queue for the selected thread.
Use it next: Copy the answer to a new local Word review document; preserve actual source-message references in restricted review and use aliases in any broader summary.
Check: Verify every proposed action against the original message; do not adopt apparent urgency or a legal deadline from an AI inference.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://support.microsoft.com/en-gb/outlook/copilot-outlook/chat-with-copilot-in-outlook
https://support.microsoft.com/en-us/outlook/frequently-asked-questions-about-copilot-in-outlook

STEP 3: Human review and final handoff
Tool: Responsible staff reviewer and lawyer/process owner
Open: Local reviewed report beside the frozen source set
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Attorney validates every proposed handoff and privacy scope. Staff records only approved action/owner/source reference in the local handoff document; if a later task or message is authorized, verify its completion separately.

Expected output: Reviewed inbox handoff queue for the explicitly selected threads.
Use it next: No folder/rule changes or communications occur in this recipe.
Check: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.