Autor: AILesson5 min de preparaciónProbado con:ChatGPTRevisado el: 2026-08-28
Respuesta rápida
Compress a case into a searchable title and handoff summary without losing uncertainty or safety context. Proporciona: Case evidence, Ticket taxonomy, Privacy and length limits. Resultado esperado: A normalized ticket title, structured summary, search terms, missing fields, and routing rationale.
1
Añade tu contexto
Tu texto permanece en este navegador. AILesson Prompts no lo envía a un modelo ni a un servidor.
2
Tu prompt
Los campos sin rellenar permanecen visibles como marcadores de posición, para que puedas copiar y editar el 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.
Privado de forma predeterminadaLa preparación del prompt se realiza localmente en tu navegador. Evita introducir información confidencial en cualquier servicio de IA, a menos que tu organización lo permita.
De la entrada al resultado
Un ejemplo completo
Mira cómo un contexto concreto convierte esta receta en un resultado que puedes usar
Entrada real
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.
Por qué funciona
1
Observable titles improve retrieval without embedding a premature root-cause diagnosis.
2
Taxonomy rationale makes routing choices reviewable and correctable.
Comprueba el resultado
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?
Úsalo con confianza
Preguntas frecuentes
Respuestas prácticas sobre cuándo usar esta receta, qué debes proporcionar y en qué casos la revisión humana sigue siendo importante
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.
Pasa de entender la IA a poner manos a la obra. Practica cómo dar instrucciones, revisar y mejorar resultados con lecciones interactivas para el trabajo y la vida cotidiana.
ChatGPT
