Review evidence before wording
Confidence can help prioritize attention, but it does not replace review. The person who sends the reply remains responsible for it.
- Read the latest customer message and relevant conversation history.
- Confirm the summary does not turn an assumption into a fact.
- Open the cited knowledge and confirm that it supports the proposed steps.
- Check for account, billing, security, refund, data, or engineering actions that require escalation.
- Edit the reply for accuracy, clarity, tone, and customer-specific context.
- Approve and send only when the response is safe and complete.
Use a consistent email structure
Start with the configured greeting, keep related troubleshooting steps together without blank lines between every step, end with a clear next action, and append the organization's saved signature.
When to escalate
Escalate when the required action exceeds support authority, documentation conflicts, the issue may affect security or data integrity, the customer reports broad impact, or a product change is required.