Getting Help
How to get support when you need it.
Support Channels
1. Documentation (Self-Service)
Best for: Finding answers quickly, learning features, API reference
- Search the docs - Use the search bar above
- Browse by topic - Check the sidebar navigation
- View examples - Code samples in each SDK guide
Average resolution time: Immediate
2. GitHub Discussions (Community)
Best for: Questions, feature requests, sharing ideas, discussing best practices
Available to: All users
How to use:
- Visit GitHub Discussions
- Search for similar questions
- Post your question with details
- Community and Toggly team will respond
Average response time: 24-48 hours (best effort)
Tips for better responses:
- Include code samples
- Specify which SDK you're using
- Share error messages
- Explain what you've tried
3. GitHub Issues (Bug Reports)
Best for: Reporting bugs, requesting features
Available to: All users
How to report:
- Visit GitHub Issues
- Search for existing issues
- Create new issue with template
- Provide reproduction steps
What to include:
- SDK version
- Framework/runtime version
- Minimal reproduction code
- Expected vs actual behavior
- Error messages/stack traces
4. Email Support (Paid Plans)
Best for: Account issues, technical support, private issues
Available to: Paid plan users
Contact: [email protected]
Response times:
- Professional: 24-48 hours (business days)
- Enterprise: 4-8 hours (custom SLA available)
What to include:
- Your account email
- Detailed description
- Steps to reproduce
- Screenshots if applicable
- SDK/platform details
5. Enterprise Support
Best for: Critical issues, custom integrations, strategic guidance
Available to: Enterprise plan users
Features:
- Dedicated support channel (Slack/Teams)
- Video call support
- Priority bug fixes
- Custom SLA agreements
- Training and onboarding
How to access:
- Schedule a call
- Email: [email protected]
Before Contacting Support
Help us help you faster by gathering this information:
For Technical Issues
-
SDK Details:
- SDK name and version
- Framework/runtime version
- Operating system
-
Error Information:
- Full error message
- Stack trace
- Browser console output
-
Reproduction:
- Steps to reproduce
- Minimal code example
- Expected vs actual behavior
-
Context:
- When did this start?
- Did it ever work?
- Recent changes made
For Account/Billing Issues
- Account email
- Organization/team name
- Current plan
- Specific issue or question
- Invoice number (if applicable)
Emergency Issues
Critical Production Issue
If you have a critical production issue:
- Disable the problematic feature in the dashboard immediately
- Check Status Page for known incidents
- Contact support with "URGENT" in subject
- Enterprise users: Use your dedicated support channel
Security Vulnerabilities
If you discover a security vulnerability:
DO NOT post publicly on GitHub.
Instead:
- Email: [email protected]
- Include detailed description
- Provide steps to reproduce (if safe)
- We'll respond within 24 hours
Support Response Times
| Plan | Response Time | Channels |
|---|---|---|
| Community | Best effort (24-72h) | Docs, GitHub Discussions |
| Professional | 24-48 hours | Email + Community |
| Enterprise | 4-8 hours | Dedicated channel + Email + Community |
Business days (Monday-Friday, 9am-5pm PST)
Self-Service Resources
Before contacting support, try these resources:
- Common Issues - Most frequent problems
- Authentication Guide - API key and token issues
- API Error Codes - Understanding error messages
- Status Page - Current system status
Tips for Faster Resolution
1. Search First
Most questions have been answered:
- Search documentation
- Search GitHub Discussions
- Search GitHub Issues
2. Provide Context
Include:
- What you're trying to achieve
- What you've already tried
- Relevant code snippets
- Error messages
3. Use the Right Channel
- Quick question? → GitHub Discussions
- Bug report? → GitHub Issues
- Account issue? → Email
- Critical issue? → Email with URGENT tag
4. Be Specific
Instead of: "It doesn't work"
Say: "When I call toggly.isEnabled('my-feature') in React 18.2 with @ops-ai/react-feature-flags-toggly v2.1.0, I get undefined instead of true/false. The feature flag is enabled in the dashboard. Here's my code: [...]"
Feedback
We're constantly improving! Share feedback:
- Feature requests: GitHub Discussions
- Documentation feedback: Edit button (top right of each page)
- General feedback: [email protected]
Additional Resources
- Support Page - All support options
- Status Page - System status
- Changelog - Latest updates
- Blog - Tutorials and guides