返回提示词目录第 1383 页

编写客服月度运营分析报告

整合咨询量、处理时效、满意度与积压情况,生成月报并提出有数据支撑的跨团队改进请求。

完整提示词

<context>
A useful support report shows whether customers are getting help fast and well, and what the rest of the company should fix so they need less help. Support leads know that raw ticket volume rises with growth, so the honest demand measure is contact rate: contacts per 1,000 orders or per 100 active customers. Response and resolution times are skewed, so medians and the 90th percentile tell the truth where averages do not, and business-hours and calendar-hours clocks give very different numbers. A fast first response that does not resolve anything shows up as a high reopen or repeat-contact rate. CSAT is answered by a minority, often the very happy and the very unhappy, so report the response count and rate beside the score, and look at CSAT by contact reason, because a policy customers dislike scores badly however good the agent was. Backlog age matters more than backlog size. The most valuable section is the contact drivers: the top reasons, their share, the trend, and which ones another team could remove through a product fix, clearer copy or self-service.

{{#context}}Context: {{context}}{{/context}}
</context>

<task>
<support_data>
{{support_data}}
</support_data>

{{#business_volume}}<business_volume>
{{business_volume}}
</business_volume>{{/business_volume}}

1. Report contact volume by channel and, if business volume is given, the contact rate and its trend; say whether volume moved because of demand or because of contact rate.
2. Report first response and resolution times as median and 90th percentile where available, naming the clock (business or calendar hours), against target and last month.
3. Report quality: reopen or repeat-contact rate, CSAT with response count and rate, and CSAT by contact reason where the data allows.
4. Rank the top contact drivers by volume with share and trend, and mark which are avoidable by a product, policy, content or self-service change.
5. Turn the avoidable drivers into specific requests to named teams, each with the ticket count that justifies it and the expected reduction stated as an estimate.
6. Summarise backlog size and age and whether staffing matched demand.
</task>

<constraints>
- Compute only from the data given; show counts behind percentages.
- Do not present an average time without the median, and do not mix business-hours and calendar-hours figures.
- Do not treat CSAT as representative without the response rate; say when the sample is too small to compare months.
- Do not name or rank individual agents in a stakeholder report.
- Do not invent contact reasons or estimated savings; label estimates as estimates.
{{> output/uncertainty}}
</constraints>

<output_format>
## Summary
Three to five sentences: demand, speed, quality, the top avoidable driver and the main ask.

## Volume and demand
Table: Channel | Contacts | Last month | Change | Contact rate. One sentence on demand versus rate.

## Speed and quality
Table: Measure | Median | 90th percentile | Target | Last month. Then CSAT with response count, and reopen rate.

## Top contact drivers
Table: Driver | Contacts | Share | Trend | Avoidable? | CSAT.

## Requests to other teams
Table: Request | Team | Driver | Contacts this month | Expected effect.

## Team and capacity
Backlog size and age, staffing against demand, notable incidents.

## Data notes
Bullets: clock used, tagging gaps, CSAT sample, anything not comparable.
</output_format>

可替换内容

  • {{#context}}
  • {{context}}
  • {{/context}}
  • {{support_data}}
  • {{#business_volume}}
  • {{business_volume}}
  • {{/business_volume}}
  • {{> output/uncertainty}}

分类与标签

办公效率、客服月报、工单分析、客户满意度、跨团队改进

前往 AI 图片创作