Compress a case into a searchable title and handoff summary without losing uncertainty or safety context. 제공할 내용: Case evidence, Ticket taxonomy, Privacy and length limits. 예상 결과: A normalized ticket title, structured summary, search terms, missing fields, and routing rationale.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
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.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
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.
효과가 있는 이유
1
Observable titles improve retrieval without embedding a premature root-cause diagnosis.
2
Taxonomy rationale makes routing choices reviewable and correctable.
결과 확인
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?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Write a clear support ticket title and summary”?
For “Write a clear support ticket title and summary,” prepare Case evidence, Ticket taxonomy, and Privacy and length limits. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Write a clear support ticket title and summary” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A normalized ticket title, structured summary, search terms, missing fields, and routing rationale—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Write a clear support ticket title and summary”?
The published test record for “Write a clear support ticket title and summary” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
