Support

When you need help with Teabar, there are several resources available depending on the urgency and nature of your issue.

Self-Service Resources

Before contacting support, check these resources:

Community Support

GitHub Discussions

For general questions, feature requests, and community help:

• URL: github.com/teabar/teabar/discussions
• Response time: Community-driven, typically within 24-48 hours
• Best for: How-to questions, best practices, feature discussions

Community Slack

Join our Slack workspace for real-time community support:

• URL: teabar.dev/slack
• Channels:
  • #general - General discussion
  • #help - Technical questions
  • #announcements - Product updates
  • #showcase - Share what you’ve built

Stack Overflow

Search and ask questions with the teabar tag:

• URL: stackoverflow.com/questions/tagged/teabar
• Best for: Specific technical questions with code examples

Bug Reports

Reporting Bugs

Report bugs through GitHub Issues:

1. Search existing issues first to avoid duplicates
2. Create a new issue with the bug report template
3. Include:
   • Teabar CLI version (teabar version)
   • Operating system and version
   • Steps to reproduce
   • Expected vs actual behavior
   • Relevant logs or error messages

# Generate diagnostic information
teabar diagnose my-env --output diagnostic.zip

URL: github.com/teabar/teabar/issues/new

Security Vulnerabilities

Report security issues privately:

• Email: [email protected]
• PGP Key: Available at teabar.dev/.well-known/security.txt

We follow responsible disclosure and will acknowledge your report within 24 hours.

Paid Support

Support Plans

Contacting Support

Pro and Enterprise customers:

# Submit support ticket via CLI
teabar support create --priority high --subject "Environment creation failing"

# Check ticket status
teabar support status ticket_abc123

# List your tickets
teabar support list

Or email: [email protected]

Include in your support request:

• Organization and project name
• Environment ID (if applicable)
• Description of the issue
• Steps to reproduce
• Impact and urgency
• Diagnostic bundle (if applicable)

Support Hours

• Pro: Monday-Friday, 9am-6pm (your timezone)
• Enterprise: 24/7 for critical issues

Escalation

If your issue isn’t being resolved:

1. Reply to your ticket requesting escalation
2. Contact your CSM (Enterprise customers)
3. Email: [email protected]

Feature Requests

Submitting Feature Requests

We love hearing how we can improve Teabar:

1. Check the roadmap: teabar.dev/roadmap
2. Search existing requests: GitHub Discussions - Ideas
3. Submit your idea with:
   • Use case description
   • Expected behavior
   • Impact on your workflow

Voting on Features

Vote on existing feature requests to help us prioritize:

• Use the thumbs up reaction on GitHub Discussions
• Comment with additional use cases or requirements

Training and Consulting

Self-Paced Learning

• Documentation tutorials: /docs/tutorials
• Video tutorials: youtube.com/@teabar
• Blog posts: teabar.dev/blog

Instructor-Led Training

Enterprise customers can request training sessions:

• Teabar Fundamentals (2 hours)
• Advanced Blueprint Design (4 hours)
• Platform Administration (4 hours)
• Custom workshops based on your needs

Contact your CSM or email [email protected]

Professional Services

For complex implementations:

• Blueprint design and review
• CI/CD pipeline integration
• Custom integrations
• Architecture consulting
• Migration assistance

Contact: [email protected]

Staying Updated

Release Notes

Stay informed about new features and fixes:

• Changelog: teabar.dev/changelog
• GitHub Releases: github.com/teabar/teabar/releases

Subscribe to Updates

# Get notified of new releases
teabar config set updates.notify true

# Check for updates
teabar update --check

Social Media

• Twitter/X: @teabar_dev
• LinkedIn: linkedin.com/company/teabar

Feedback

We’re always looking to improve. Share your feedback:

• Product feedback: [email protected]
• Documentation feedback: Use the “Was this page helpful?” widget
• NPS surveys: Respond to in-app surveys

Quick Reference