Step 1 — paste the AI-drafted reply
Open ReplyAuditor and paste the support reply you want to check into the reply field. It can be a draft from your AI assistant, a helpdesk copilot, or any generated text. The tool reads it and runs the checks — you do not rewrite the reply to use it.
Example input:
Hi Sarah, your refund of $49.99 is processed. Your order #88213 ships Tuesday.
Step 2 — add your rules (optional)
In the rules field, list your brand, tone, or policy rules — one per line. For example:
Always greet by name No guarantees on delivery dates Never ask for password
ReplyAuditor checks the draft against these alongside its built-in hallucination and PII checks.
Step 3 — pick a channel
Choose the channel the reply is for: Email, Live Chat, Social, or Ticket. Channel shapes how the checks are read — a public Social reply is held to a tighter tone and PII standard than an internal Ticket note.
Step 4 — run and read the verdict
Run the audit. ReplyAuditor returns a quality report: a per-check pass/fail list (hallucination, PII, tone, policy) plus a ship/hold verdict. "Hold" means at least one check failed and a human should look before sending; "Ship" means it passed the gate's checks — not that it is guaranteed flawless.
Step 5 — review as a team (optional)
On the team tier, a QA dashboard aggregates which check fails most often across replies. That signal tells you where the AI drafting — or your policy rules — need tuning. It is a view of your exposure, not a certificate.
Pricing
- Free — a limited number of replies per month.
- Pro — a monthly price with unlimited audits and tone rules.
The checks are the same across tiers; the difference is volume and the team dashboard.
An honest limit
ReplyAuditor reduces obvious failure modes and makes them visible. It does not guarantee replies are accurate or compliant, and it is not a replacement for human review or a legal sign-off. The team stays responsible for what goes out.
References
- GDPR — personal data in customer communications: https://gdpr.eu/