Turn scattered software symptoms into a sanitized support case
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
- Actual incident notes and product/OS/version evidence already available to authorized staff; a non-sensitive test view if a screenshot is needed.
- Existing firm-approved Acrobat Studio, AI Assistant add-on, or another plan including Acrobat AI; online services/cloud storage, language and region must be permitted. No purchase, login or connection is part of this verification. The manual route works without AI.
- 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
- No universal application log export is claimed. Raw network logs, client screenshots, tokens and whole desktops are excluded. Historical observations may be reported without reproducing the failure.

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: Capture only the observed symptom
Tool: Windows Snipping Tool and local incident notes
Open: Windows+Shift+S > rectangular capture; Snipping Tool > Save
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

For a permitted synthetic view, capture only the relevant application area. Otherwise use already-approved evidence without reproducing the issue. Record product/version as actually observed, exact error, occurrence time/timezone, expected/actual behavior, observed steps and frequency; unknown fields remain unknown. Keep raw evidence restricted and write a separately approved text description keyed to evidence IDs.

Expected output: Sanitized incidents.txt and evidence inventory; optional sanitized screenshot stored locally.
Use it next: Staff visually checks every image; only approved text descriptions, not unrestricted screenshots, enter the AI source set.
Check: Capture is a manual evidence step, not diagnosis. Never expose notifications, paths with client names, credentials or unrelated windows.
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/windows/apps/use-snipping-tool-to-capture-screenshots

STEP 2: Load only the approved AI input
Tool: Acrobat PDF Spaces
Open: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Add sanitized incident notes and the evidence-ID descriptions.  Use clear source/version labels and verify the Files panel. Do not add originals that have not separately been cleared for Adobe processing.

Expected output: Visible approved source set in the PDF Space; no account integration is implied.
Use it next: Use the AI Assistant message field in this same space for the next prompt.
Check: Confirm every named source is actually loaded and readable. PDF Spaces supports up to 100 files, 100 MB and 600 pages per file; unsupported/password-protected/handwritten material blocks affected extraction.
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/explore-pdf-spaces/create-pdf-spaces.html
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/supported-formats-limitations.html
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/pdf-spaces-faq.html

STEP 3: Run the bounded prompt and inspect citations
Tool: Acrobat AI Assistant
Open: The PDF Space AI Assistant message field
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Paste the prompt below. Open each source-number citation, check it, and use Copy to transfer the answer into a new local Word document or text file. Correct errors using the originals before reliance.

PASTE THIS PROMPT
Draft a support case from these sanitized incident observations. Include environment, expected behavior, actual behavior, observed steps, frequency, first/last occurrence, evidence IDs and unanswered questions. Distinguish observations from hypotheses and leave missing details unknown. Cite the source note for each fact. Describe any proposed reproduction with synthetic data only; do not execute it. Exclude credentials, client information, raw logs and unrestricted screenshots. Do not diagnose a root cause as proven, contact support or change settings.

Expected output: Support-case draft and a list of attachments the human must separately approve.
Use it next: Save the checked draft as support-case-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Contradicting screenshot descriptions must remain a conflict; similar product names must not be merged.
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

STEP 4: 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.

Staff or IT confirms facts, scrubs each proposed attachment and verifies the vendor’s official support destination. Save the approved draft and attachment list locally.

Expected output: A support-ready draft with explicit unknowns and attachment approvals.
Use it next: Contacting support or uploading any file is a separate authorization, not part of this documentation pass.
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.
