返回提示词目录第 1450 页

撰写供应商支持工单

根据问题类型整理供应商工单的主题、证据、严重度和后续材料,帮助提高技术支持沟通效率。

完整提示词

<context>
Most vendor cases are not outages: a configuration question, a bug with a workaround, a quota that blocks a launch next month, a feature the product lacks, a charge nobody expected. These cases sit in low-severity queues where the first responder is often a generalist, so they stall in a predictable loop: the responder asks for the version, the account id or the exact steps, a day passes, and the answer is a docs link the customer already read. Each case type needs different evidence. A question needs what was tried and which docs did not answer it. A bug needs versions and a minimal reproduction. A limit increase needs current usage, the forecast and the date it is needed, because quota reviews take time. A feature gap needs the use case and an ask to log it as a feature request with a reference. A billing case needs the invoice and line item, the expected and charged amounts, and the usage evidence.
</context>

<task>
Write a support case.

<issue>
{{issue}}
</issue>
{{#case_type}}
Case type: {{case_type}}
{{/case_type}}

1. If the input describes a production outage or severe degradation happening now, say so at the top of Case, recommend escalating it as an incident at the vendor's highest appropriate severity instead of a routine case, and keep the rest short.
2. Use the case type given, or infer it from the input, and recommend a low or normal severity with a one-line reason. Say what would justify a higher one.
3. Write a subject line that names the product, the case type and the specific point, for example "Managed Postgres: request to raise max connections on prod-eu from 500 to 1,500 before 1 Dec".
4. Write the body with one clear ask in the first two sentences, then the evidence for this case type:
   - question: goal, what you tried, the docs pages you read and where they fall short, the exact question;
   - bug: versions, minimal reproduction, expected versus actual, frequency, workaround in use;
   - limit increase: current limit and usage, forecast with its basis, the date needed, and the resource ids;
   - feature gap: the use case, current workaround and its cost, and a request to log a feature request and share its reference;
   - billing: invoice and line item, expected versus charged amount, the usage or contract terms behind your expectation, and the resolution you want.
5. State your deadline, if any, and what happens on your side if it is missed, without threats.
6. Under Before sending, list what to attach, the placeholders to fill and what to do if the reply is a docs link that does not answer the question (reply with the specific gap, ask for the case to go to a specialist).
</task>

<constraints>
- Use only identifiers, amounts, versions and dates from the input; missing ones become `[add: ...]` placeholders. Never invent the vendor's severity names, limits, prices, SLAs or contract terms.
- For billing cases, do not assert the vendor is wrong; state the discrepancy and ask for an explanation or correction.
- Calm and factual; the body under about 250 words.
</constraints>

<output_format>
## Case
Case type, recommended severity and why, subject line, then the body.

## Before sending
Bullets: attachments, placeholders to fill, follow-up if the first reply misses.

## Redaction check
Bullets: anything in the input that looks like a secret, token, connection string, card number or personal data, or "None found".
</output_format>

可替换内容

  • {{issue}}
  • {{#case_type}}
  • {{case_type}}
  • {{/case_type}}
  • [add: ...]

分类与标签

办公效率、供应商沟通、技术支持、工单写作、问题描述

前往 AI 图片创作