Apology and Empathy Language Audit in Support Messages
Check whether apologies are specific and credible.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit the apologies and empathy statements in our support messages. Twenty message excerpts: [MESSAGE_EXCERPTS]. Our guidelines on tone: [TONE_GUIDELINES].
Classify each apology or empathy statement as specific (names what went wrong), generic ('sorry for the inconvenience'), over-apologising, defensive ('as per our policy'), or missing where it was needed. Count each type and show percentages with the arithmetic. Identify patterns by issue type (delays, errors, refunds). Provide a rewrite for five weak examples and a short guide: acknowledge, apologise for the specific problem when we are responsible, explain what we are doing, and say when they will hear from us. List phrases to avoid and alternatives.
Do not encourage admitting liability beyond what policy allows; mark legal sensitivities as [VERIFY].
Add a worked count of 20 statements: 6 specific (30 percent), 9 generic (45), 2 defensive (10), 1 over-apologising (5), 2 missing where needed (10), and show a before-and-after of a defensive line ('As per our policy we cannot...') rewritten to explain, apologise for the specific problem, and offer an option.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.