support
Acknowledge
First acknowledge the issue in plain human language.
Do not start with disclaimers when someone lost access or money.
support voice
Support response rules
How to reply to customers calmly, concretely, safely, and without extra promises.
Support does not argue with customer emotion or hide in fog. It helps, checks facts, and keeps boundaries.
support
Verify
Ask only necessary data: email/order/time, never sensitive extras.
Do not ask for passwords, full card details, private confessions, or irrelevant identity data.
support
Close
Close with next step, timeframe if known, and escalation path.
Do not promise impossible refunds, exact results, or guaranteed delivery time if unknown.
Reply structure
Every reply rests on four bones.
- Thank you / I understand the issue.
- What I am checking or already checked.
- What is needed from the customer, if anything.
- Next step and expectation boundary.
checklist
- No blame language.
- No unnecessary data collection.
- There is a concrete next step.
handoff
- Escalation includes summary, customer issue, checked facts, proposed action.
red flags
- Customer reports double charge.
- Customer asks to delete data.
- Customer threatens chargeback or legal action.
related doors