Audit a support reply for risky commitments

Screen outgoing support responses for accidental promises, unverified feature dates, and unauthorized policy exceptions before hitting send.

You getRisk Assessment, flagged Statements and clean Revised Draft

Prompt

Prompt
Act as a customer support quality assurance lead. Review the draft response below to identify any unsupported commitments, speculative product roadmaps, or risky policy exceptions.

Rules:
- Flag absolute guarantees, definitive release dates, and unauthorized financial or SLA promises.
- Highlight phrases that admit fault or liability before root causes are confirmed.
- Provide a safer rewritten version of each problematic sentence, keeping a helpful customer-facing tone.
- Note any missing standard disclaimers.

Output format:
- Risk Assessment (Low, Medium, or High)
- Flagged Statements (original phrase, risk reason, safer rewrite)
- Clean Revised Draft (the complete response ready to send)

The customer message and my proposed draft are below:

Example output

Example for: an engineer-written draft addressing an active service outage

Risk Assessment: High

Flagged Statements:

  1. Original: "We will have this fully fixed by 3:00 PM EST today."
  • Risk: Commits to an unverified technical fix time, creating an escalation if debugging stalls.
  • Safer rewrite: "Our engineering team is actively deployed on this issue, and we will provide our next status update by 3:00 PM EST."
  1. Original: "I will apply a full month credit to your account for the inconvenience."
  • Risk: Offers a financial concession outside standard agent authorization limits before outage duration is known.
  • Safer rewrite: "Once the incident is fully resolved, our billing team will review service credits in accordance with our uptime SLA."

Clean Revised Draft:

Hi Alex,

Thank you for alerting us to this connection issue. Our engineering team has identified the root cause in the authentication cluster and is working to restore services. We are treating this as our top priority.

We will post our next status update on our status dashboard and via email by 3:00 PM EST. Once normal service is verified, we will follow up regarding SLA credits for the disrupted period.

Thank you for your patience while we resolve this.

Written by AI from this prompt. Your results will vary.

Paste both the customer's question and your rough response into Claude, Gemini, or ChatGPT. If your company has a strict SLA or refund threshold, paste that rule as an extra line for more precise checks.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Customer Support