Premise
The assistant watches a support inbox and prepares replies before you sit down. The time savings come from ready drafts, not unsupervised sending.
Setup
- Connect the support inbox with draft access.
- Provide approved help articles and representative sent replies.
- Define escalation labels for refunds, legal issues, abuse, and angry customers.
- Schedule one morning drafting pass.
Boundaries
- It does not send, refund, promise features, or add contacts to marketing.
- Personal conversations and uncertain requests are skipped for review.
For each new support request, provide: requester, core need, whether it is an FAQ or possible defect, and one concise draft. Link an existing help article when it genuinely resolves the issue.
End each run with counts for drafted, already handled, skipped, and escalated. Escalate angry, legal, security, refund, or policy-sensitive messages instead of trying to sound clever.
Save drafts only. Never send, refund, promise a roadmap item, or subscribe the requester to marketing. If you cannot distinguish customer support from personal mail, leave it untouched.
Prompt
Draft support replies for my review. Learn tone and structure from my approved sent messages, but rely on current product documentation for factual answers.