Compress a case into a searchable title and handoff summary without losing uncertainty or safety context
5 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Create a searchable support-ticket title and faithful summary from the supplied evidence.
Conversation, environment, symptom, error, attempts, impact, attachments, status, and corrections:
[case]
Title convention, products, components, issue types, severity, routing, tags, and fields:
[taxonomy]
Length, audience, redaction, forbidden data, confidence, and localization:
[limits]
Choose only taxonomy values supported by evidence; leave others unknown and explain routing ambiguity. Write a title that distinguishes product or component, observable symptom or error, triggering condition, and affected scope when known. Avoid vague labels such as broken, urgent, or not working, and do not include names, secrets, account IDs, unconfirmed causes, business judgments, or invented severity. In the summary separate expected behavior, observed behavior, environment, onset and frequency, affected scope, impact, chronological attempts and results, attachment evidence, current state, known incident relation, risks, and missing information. Preserve corrections and contradictions. Add search synonyms and exact error code without keyword stuffing. State routing and severity rationale from the supplied rules, plus facts still needed to confirm them.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Case evidence
Windows 11, Desktop App corrected from 4.2.1 to 4.2.0. After company password change, sync remains Paused. Restart completed with no change. Cache clearing suggested but not performed due to unsynced drafts. Reauthenticate completed and produced E401. Screenshot before reauthentication showed Paused with no error. One user confirmed; wider scope unknown. No data lost. Known PDF incident INC-882 is unrelated.
Ticket taxonomy
Title: Product | Component | Symptom (Trigger), max 90 characters. Product Desktop App; components Sync/Auth/Export. Types Incident/How-to/Access/Data loss. Severity: S1 safety or broad outage; S2 multiple users or blocked critical work; S3 single user with workaround or incomplete scope; S4 question. E401 routes to Identity Tier 2. Required fields: OS, version, error, affected users, attempts, data-risk flag.
Privacy and length limits
Internal English title and bilingual example summary. Redact customer and workspace identifiers. Summary under 180 words per language. Do not infer root cause. Confidence labels for scope and impact.
Summary
Expected: sync resumes after credentials are updated. Observed: Desktop App 4.2.0 on Windows 11 remains Paused after a company password change; reauthentication then returns E401.
Scope: one user confirmed, wider scope unknown (high confidence in single report; low confidence in total scope). Impact: unsynced drafts exist, but no data loss is reported; critical-work blockage is unknown.
Attempts: restart completed with no change. Cache clearing was suggested but not performed and must not be recorded as an attempt; unsynced drafts create a data-risk flag. Reauthentication completed and produced E401. Screenshot before that step shows Paused without an error.
Current state: unresolved. INC-882 concerns PDF export and is not related by supplied evidence.
Routing: Identity Tier 2 because E401 is confirmed. Provisional severity S3 because only one user is known and scope/critical impact are incomplete; reassess if multiple users or blocked critical work are confirmed. Search terms: E401, auth, reauthenticate, sync paused, password change.
Why this works
1
Observable titles improve retrieval without embedding a premature root-cause diagnosis.
2
Taxonomy rationale makes routing choices reviewable and correctable.
Check the result
Does the title distinguish the case using only observable facts?
Does the summary preserve attempts, corrections, risk, and unknowns?
Are route and severity justified by supplied rules rather than tone?
ChatGPT