Customer Support
OperationsPhase 2Lead: CS Orchestrator Agent
Architecture Pattern
View full details →Customer queries are classified and routed to specialized handlers (account, payment, game, general). Each handler follows a resolution chain. Proactive Support and Knowledge Base agents work in parallel to deflect tickets before they arrive.
Core Operations. Automated CS via Intercom handles player queries and reduces manual workload. Depends on Phase 1 player data and risk flags.
Tools
Goals
Agent Sizing Rationale
8 agents: 1 orchestrator + 3 support specialists (odd for escalation voting) + 1 quality + 1 knowledge base + 1 proactive support + 1 station message. 3-agent panel votes on whether to auto-resolve or escalate complex tickets.
Support (3-agent resolution panel)
Quality, Knowledge & Proactive Support
Agents Used From Other Departments
These agents from other departments feed data into or are called by this department's agents.
Player segments determine support priority and tone.
VIP status triggers priority routing and dedicated support flows.
Risk flags inform CS agents about account restrictions and required verification.
CS surfaces churn signals (complaints, repeated issues) to Retention for proactive intervention.
CS response templates, help center content, and player-facing communications must maintain brand voice and visual consistency.
Complaints about fairness require compliance-reviewed responses. Legal threats need Legal involvement. Self-exclusion requests must be processed per regulatory requirements.
Payment disputes and stuck withdrawals require coordination with Wallet & Payments. CS agents need wallet status visibility to resolve payment-related tickets.