Support quality is the number one reason customers stay or leave. Your hosting infrastructure can be identical to competitors - your support is the differentiator.
Support Channels
Ticket System (Primary)
Every interaction creates a record. Recommended tools:
- Freshdesk: Free tier available, professional interface
- osTicket: Open source, self-hosted
- WHMCS built-in: Integrated with billing
Discord (Community Support)
For gaming hosting, Discord is expected:
- #support channel for quick questions
- Ticket bot for private issues
- Community members help each other (free support!)
Live Chat (Optional)
Crisp, Tawk.to, or LiveChat. Good for sales questions, less ideal for technical support (needs context that tickets provide).
Email (Backup)
Forward support@yourbrand.com to your ticket system. Never manage support directly in email - you'll lose track of issues.
Response Time Standards
| Priority | First Response | Resolution Target | |----------|---------------|-------------------| | Critical (server down) | 30 minutes | 2 hours | | High (performance issue) | 2 hours | 8 hours | | Normal (configuration help) | 4 hours | 24 hours | | Low (billing question) | 8 hours | 48 hours |
Communicate these targets to customers. Meeting your own standards builds trust.
Support Templates
First Response
Hi [Name],
Thanks for reaching out. I understand you're experiencing [issue summary].
Let me look into this for you. I'll update you within [timeframe] with a solution or next steps.
Best regards,
[Your name] - [Your brand] Support
Resolution
Hi [Name],
I've [action taken]. Here's what was happening: [brief explanation].
Your server should now be [working normally / updated / configured]. Please let me know if you notice any further issues.
Best regards,
[Your name]
Escalation
Hi [Name],
This requires additional investigation beyond standard support. I've escalated this to our infrastructure team for a deeper look.
You'll receive an update within [timeframe]. In the meantime, [any interim steps they can take].
Best regards,
[Your name]
Knowledge Base
Create documentation before customers ask questions. Top articles for game hosting:
- Getting Started: Step-by-step first server setup
- Plugin/Mod Installation: How to add mods via panel
- Server Configuration: Common settings explained
- File Management: FTP/SFTP access guide
- Billing: How to upgrade, cancel, pay
- Troubleshooting: Server won't start, high latency, crashes
Each article saves you from answering the same question repeatedly.
Handling Difficult Customers
Angry Customer
- Acknowledge their frustration
- Don't take it personally
- Focus on the solution
- Follow up after resolution
Unreasonable Demands
- Clearly state what's included in their plan
- Offer alternatives or upgrades
- Don't make exceptions that set unsustainable precedents
Abusive Customers
- One warning with your communication policy
- If it continues, refer to Terms of Service
- Document everything
- Terminate service if necessary
Metrics to Track
- Average response time: How fast do you reply?
- Resolution time: How long until problems are solved?
- Customer satisfaction: Post-ticket surveys
- Ticket volume: Are you scaling support with growth?
- Common issues: What can be prevented with better documentation?
Scaling Support
0-50 Customers
You handle everything. Respond quickly, learn common issues, build your knowledge base.
50-200 Customers
Consider part-time support help. Hire from your community - people who use your service make the best support agents.
200+ Customers
Dedicated support staff or team. Clear escalation procedures. Internal documentation for support processes.
Good support on quality infrastructure (like Space-Node) means fewer issues to handle in the first place. The fewer fires there are, the more time you spend building relationships instead of fighting problems.
