Extract the issue and attempted steps from a support conversation
Автор: AILesson7 мин на настройкуПроверено на:ChatGPTПроверено: 2026-08-28
Быстрый ответ
Build a factual troubleshooting state from a conversation without merging different attempts or inventing results. Укажите: Support conversation, Case context, Extraction schema. Ожидаемый результат: A source-linked issue record with environment, reproduction, attempts, outcomes, gaps, safety signals, and next questions.
1
Добавьте контекст
ваш текст остаётся в этом браузере. AILesson Prompts не отправляет его ни в модель, ни на сервер.
2
Ваш промпт
Незаполненные поля остаются видимыми как заполнители, поэтому вы всё равно можете скопировать и отредактировать промпт
Extract the troubleshooting state faithfully from the supplied support conversation.
Full conversation, speakers, timestamps, attachments, corrections, redactions, and channel changes:
[conversation]
Product, version, incidents, prior cases, account facts, scope, and terms:
[context]
Fields, confidence, privacy, escalation signals, and target audience or system:
[schema]
Separate customer report, support statement, system evidence, attachment evidence, and inference. Identify primary symptom, expected versus observed behavior, onset and frequency, business impact, environment, reproduction conditions, error text, affected scope, and current state. List every attempted step chronologically with actor, exact action, prerequisites, timestamp, observed result, whether the result was verified, and whether the step is safe to repeat. Do not collapse similar attempts, assume completion, infer causation, or treat no reply as success. Preserve contradictions and corrections. Mark facts unknown rather than filling standard fields. Redact secrets and unnecessary personal data; flag safety, security, privacy, financial, legal, or accessibility escalation signals. End with duplicate questions to avoid, the smallest necessary clarification set, and a handoff-ready next-action boundary without prescribing an unsupported fix.
Конфиденциально по умолчаниюПромпт собирается локально в вашем браузере. Не вводите конфиденциальную информацию в сервисы ИИ, если ваша организация этого не разрешает.
От исходных данных к результату
Разобранный пример
Посмотрите, как конкретный контекст превращает этот рецепт в полезный результат
Реальный ввод
Support conversation
09:02 Nora: Since yesterday, Desktop App sync says Paused after our password changed. Windows 11, app 4.2.1. Internet works. 09:05 Support: Please restart. 09:12 Nora: Restarted; still Paused. 09:18 Support: Clear cache. 09:20 Nora: I have unsynced drafts, so I did not clear it. 09:24 Nora uploads screenshot showing Paused, no error. 09:40 Support: Try Reauthenticate under Settings > Accounts > Workspace. 10:03 Nora: Windows sign-in opened, I completed it, then saw E401. 10:05 Nora: Correction—the app is 4.2.0, not 4.2.1. No password or private draft attached.
Case context
Approved incident INC-882 concerns blank PDF charts, unrelated unless evidence says otherwise. Approved 4.2 procedure warns not to clear cache or reinstall when unsynced drafts exist. E401 after reauthentication requires escalation after one retry, but no retry has yet been requested in this conversation.
Primary symptom — high: sync remains Paused after a company password change (Nora, 09:02); expected state is not explicitly stated, though successful sync is implied and should remain an inference. Onset: “since yesterday,” exact date/time unknown. Impact: unsynced drafts exist; quantity and business consequence unknown.
Environment — high: Windows 11, Desktop App 4.2.0, corrected at 10:05. The earlier 4.2.1 statement is superseded, not silently merged. Internet reported working at 09:02, not independently verified.
Attempts
Restart requested 09:05, completed by Nora before 09:12; observed result: still Paused. Safe to record as failed.
Clear cache suggested 09:18 but explicitly not performed at 09:20 because unsynced drafts exist. Do not record it as attempted or request it again; approved guidance identifies data-loss risk.
Reauthenticate requested 09:40; Nora opened Windows sign-in and completed it before 10:03; observed result: E401. Customer report, not system log.
Evidence: screenshot at 09:24 shows Paused and no visible error; attachment contents beyond that are unknown. INC-882 is not linked to this symptom.
Unknowns: exact onset, workspace identifier, whether all workspaces/users are affected, E401 timestamp precision, and whether an approved single retry has occurred. Next boundary: Tier 2 should preserve drafts, avoid cache clearing/reinstall, confirm affected scope, and decide whether to request the one approved reauthentication retry or escalate. Do not ask again for OS, corrected app version, internet status, restart, screenshot, or whether cache was cleared.
Почему это работает
1
Chronological attempt records prevent customers from repeating steps that already failed.
2
Evidence-type labels keep diagnostic inference from becoming a false technical fact.
Проверьте результат
Is every attempt tied to an actor, action, time, and observed result?
Are report, evidence, and inference kept separate?
Are known answers protected from duplicate questioning?
Используйте уверенно
Часто задаваемые вопросы
Практические ответы о том, когда использовать этот рецепт, что нужно предоставить и где по-прежнему важна проверка человеком
What should I prepare before using “Extract the issue and attempted steps from a support conversation”?
For “Extract the issue and attempted steps from a support conversation,” prepare Support conversation, Case context, and Extraction schema. 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 “Extract the issue and attempted steps from a support conversation” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A source-linked issue record with environment, reproduction, attempts, outcomes, gaps, safety signals, and next questions—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 “Extract the issue and attempted steps from a support conversation”?
The published test record for “Extract the issue and attempted steps from a support conversation” 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
