返回提示词目录第 1146 页

起草服务中断抵扣申请邮件

帮你梳理服务协议条款与中断证据,核算抵扣金额并起草申请邮件,提示需专业确认。

完整提示词

<context>
Most cloud and SaaS service credits are never paid because customers never claim them: SLAs usually require the customer to submit a claim, often within 30 days or by the end of the following billing month, with specific evidence, through a specific channel. People who manage vendors know the details that decide a claim: how the SLA defines downtime (the whole service or a single component, error-rate thresholds, minimum durations), exclusions (scheduled maintenance, customer-caused issues, beta features, force majeure), whether uptime is measured per month or per region, the credit table and its cap, and whether credits are the "sole and exclusive remedy". A good claim cites the clause, gives exact UTC times and evidence, shows the calculation, and asks for confirmation by a date, in a neutral tone that keeps the relationship intact.
</context>

<task>
Prepare a service-credit claim for {{account}}.

<sla_terms>
{{sla_terms}}
</sla_terms>

<incident>
{{incident}}
</incident>

1. Eligibility check: from the SLA wording only, state the uptime commitment, how downtime is defined, exclusions that might apply to this incident, the claim deadline and channel, and the evidence required. Quote clause numbers. Mark anything not stated as "not stated". If the incident appears excluded or below the threshold, say so plainly.
2. Credit calculation: convert the incident times to one time zone, compute downtime minutes in the measurement period, monthly uptime percentage (show the formula and the minutes in the month), the matching credit tier, and the credit amount against the monthly fee, applying any cap. Show the working; mark assumptions.
3. Claim email: subject "SLA credit claim: [service], [incident date], [account ID]"; the claim and amount in the first sentence; the clause relied on; incident timeline with UTC times and the vendor's own incident reference; evidence attached (monitoring exports, ticket numbers, status page screenshots); the calculation summary; a request to confirm the credit and when it will apply, by a date inside the claim window; a brief, neutral note of business impact.
4. If they refuse: a short reply asking them to identify the clause or measurement they rely on and to share their uptime data for the period, plus the escalation route (account manager, then the contract's dispute process).
5. Under Notes: whether the sole-remedy clause limits other compensation, and when to involve legal or procurement.
</task>

<constraints>
{{> guardrails/professional-limits}}
- Use only the SLA wording and incident data provided. Never invent clauses, credit tiers, deadlines, uptime figures or vendor statements.
- If the vendor's reported times differ from the user's monitoring, show both and claim on the defensible figure, explaining the difference.
- Neutral, factual tone; no threats to leave unless the user wants that said.
- Keep IDs and amounts as [placeholders] when not given.
{{> output/uncertainty}}
</constraints>

<output_format>
## Eligibility check
Table: term | what the SLA says (clause) | applies to this incident?
## Credit calculation
Working and result.
## Claim email
Ready to send.
## If they refuse
The reply.
## Notes
Remedy limits and when to escalate.
</output_format>

可替换内容

  • {{account}}
  • {{sla_terms}}
  • {{incident}}
  • {{> guardrails/professional-limits}}
  • {{> output/uncertainty}}
  • [service]
  • [incident date]
  • [account ID]
  • [placeholders]

分类与标签

办公效率、供应商沟通、服务中断、服务抵扣、申请邮件、协议条款

前往 AI 图片创作