COMPILESQUAD — SUPPORT-INTAKE REVIEW EXAMPLES
Prepared 30 September 2026

SYNTHETIC / UNRUN: These are invented requests, proposed routing labels and illustrative drafts written for this guide. No live model evaluation or customer deployment is represented. The deliberately unsuitable drafts below are teaching examples, not observed model outputs.

Purpose: agree what a reviewer should accept, edit or reject before a pilot. These four examples are not automatically the 20 tests in a client scope. Agree your own categories, queues and acceptance criteria.

Sample routing: email issues -> Service Desk; access requests -> Identity Team; missing context -> Service Desk. A reported broad mail outage is urgent for human triage. Urgent is not a diagnosis or response-time promise. Queue names are illustrative.

For each authorised test, record: actual output; routing correct under the agreed policy (yes/no/unresolved); draft decision (accept/edit/reject); exact defect; corrected draft; reviewer/date. Keep results blank until a test and review occur. Never count an unrun case as a pass.

1. A MAIL APP NEEDS CLARIFICATION (CS-EVAL-01)
Subject: Outlook keeps asking me to sign in
Invented request: Since a password change, Outlook prompts me every few minutes. Web mail and Teams still work. Only I am affected.
Expected routing: email · normal · Service Desk
Reject this illustrative draft: Your password has been reset and Outlook is fixed.
Reviewer correction: Web mail still works, and no reset or repair has been performed. Remove the unsupported completion claim.
Revised illustrative draft: Which Outlook version and operating system are you using? Please share the non-sensitive error text, if any. Do not send passwords or verification codes. You reported that web mail still works; the reviewer can use that distinction when investigating.
Actual test output: [not run]
Routing check: [not evaluated]
Draft decision and defect: [not evaluated]
Reviewer and date: [not reviewed]

2. AN ACCESS REQUEST NEEDS APPROVAL (CS-EVAL-02)
Subject: Cannot open the shared support mailbox
Invented request: My individual mailbox works. I have never had permission to open our shared support mailbox. Please grant me access.
Expected routing: access · normal · Identity Team
Reject this illustrative draft: You now have access to the shared mailbox.
Reviewer correction: A request is not an approval. The draft must leave permission changes to an authorised person.
Revised illustrative draft: Please use your normal access-request process to identify the shared mailbox and its approver. An authorised person must review the request before any access is granted. No permission change has been made.
Actual test output: [not run]
Routing check: [not evaluated]
Draft decision and defect: [not evaluated]
Reviewer and date: [not reviewed]

3. A REPORTED OUTAGE NEEDS HUMAN TRIAGE (CS-EVAL-05)
Subject: Company mail unavailable for everyone
Invented request: Nobody in our 40-person team can send or receive mail. Both desktop Outlook and web mail are failing now.
Expected routing: email · urgent · Service Desk
Reject this illustrative draft: The email provider is down. Service will return in 30 minutes.
Reviewer correction: The reported impact supports urgent triage, but neither the cause nor a restoration time has been verified.
Revised illustrative draft: You report that the whole team cannot send or receive mail in either Outlook or web mail. What time did this begin, and what non-sensitive error message appears? Please use your agreed urgent-support channel so the responsible team can investigate.
Actual test output: [not run]
Routing check: [not evaluated]
Draft decision and defect: [not evaluated]
Reviewer and date: [not reviewed]

4. A VAGUE REQUEST NEEDS CONTEXT (CS-EVAL-12)
Subject: Please help
Invented request: It is not working.
Expected routing: other · normal · Service Desk
Reject this illustrative draft: Restart Outlook to resolve your email problem.
Reviewer correction: The request does not identify an application or an email problem. Ask for context before proposing a diagnosis.
Revised illustrative draft: Which system is not working, what were you trying to do, and what happened? Please share any non-sensitive error text and whether other people are affected. Do not include passwords or unrelated personal documents.
Actual test output: [not run]
Routing check: [not evaluated]
Draft decision and defect: [not evaluated]
Reviewer and date: [not reviewed]

BEFORE YOU USE THIS WITH YOUR OWN WORKFLOW
Agree the request categories, reviewer and escalation process. Use approved synthetic or redacted examples. Do not paste private customer tickets into an unapproved AI tool. Keep actual outputs separate from expected labels. Human review is required; no replies or business actions are automatically sent by this worksheet.

DISCUSS FIT
Describe one inbox or form, the types of requests and who would review drafts. Do not send credentials or sensitive tickets with an initial enquiry.
https://www.compilesquad.com/ai-workflow-pilot
https://www.compilesquad.com/contact

For further illustrated workflow and review examples:
https://www.linkedin.com/company/compilesquad/