Overview
Reporting bugs and errors helps improve the platform and resolve issues affecting your work. This guide covers how to identify, document, and report technical problems through official channels to ensure they reach the appropriate support team quickly and are resolved efficiently.
Learning Objectives:
Identify what constitutes a bug vs. expected behavior
Gather necessary diagnostic information before reporting
Submit bug reports through appropriate channels
Track reported issues and follow up on status
Apply best practices for clear, actionable bug reports
Prerequisites
You'll Need:
Active workspace access
Description of the issue you're experiencing
Steps to reproduce the problem
Screenshots or screen recordings (if possible)
Browser and OS information (if relevant)
Error messages or codes (if displayed)
Identify and Document the Bug
What to Include in Your Report
Verify it's actually a bug
Check if issue is covered in existing documentation
Confirm you have proper permissions for the action
Try refreshing the page or signing out/in
Test in different browser or clear cache
Gather diagnostic information
Screenshot/video: Capture visual evidence of the issue
Error messages: Copy exact text of any error messages
Steps to reproduce: Write down exact steps leading to issue
Environment: Note browser, OS, device type
Workspace: Which workspace the issue occurred in
Frequency: Does it happen every time or intermittently?
Impact: How does this affect your work?
Result: You have comprehensive documentation ready for bug report.
Tip: Use browser dev tools (F12) to check Console tab for JavaScript errors—include any red error text in your report.
Submit Bug Report
Access help/support menu
Look for "Report a Bug" icon (lower-right corner)
Click to open the form
Complete bug report form
Name
Email: Email associated with your TeamAI workspace
Description:
What you were trying to do
What you expected to happen
What actually happened
Steps to reproduce (numbered list)
Add a Screenshot: Click Allow when prompted so TeamAI can access your tab and take a screenshot.
Submit report
Click "Send Report" button
Result: Bug report is submitted to support queue.
What Happens After Reporting
Triage and assignment
Support team categorizes bug and assigns priority
May request additional information within 72 hours
Investigation
Developers attempt to reproduce issue
May contact you for clarification or testing
Resolution
Bug is fixed and deployed
You receive notification that issue is resolved
Verification
Test fix in your workspace
Confirm resolution or report continuing issues
Result: Clear process ensures bugs are resolved systematically.
Best Practices
Search first - Check existing help docs before reporting
Be specific - Include exact error messages, screenshots, and reproduction steps
One bug per report - Don't combine multiple issues in single report
Test thoroughly - Verify issue is reproducible, not a one-time glitch
Include context - Explain how issue impacts your work and workflow
Test fixes - Verify resolution and report if issue persists
Common Questions
Q: What's the best way to report a bug?
A: Use in-app bug reporting form or email support with comprehensive details.
Q: How long until I get a response?
A: Depends on severity; it usually takes 72 hours.
Q: What if I don't have screenshots? A: Provide detailed written description with exact error messages and steps to reproduce.
Q: Who can see my bug reports?
A: Support team and relevant developers only.
Q: Can I report bugs anonymously?
A: No—support needs your contact info for follow-up questions and verification.
Q: What if I can't reproduce the bug consistently?
A: Report anyway. Include "sometimes" or "first time" in frequency field. Include patterns if you notice them.