Skip to main content
Bug report illustration showing the importance of detailed information Fixing a bug without details is like searching for a burnt-out bulb in a skyscraper without knowing the floor. Just like a technician needs specific information (address, room, lamp type), our developers need precise details to diagnose and fix issues quickly.
The more detailed your bug report, the faster we can resolve the issue. Incomplete reports may significantly delay the resolution process.

​
Bug Reporting Methods

You have several convenient ways to report bugs:

​
1. Chat Interface Flag Feature

When you encounter an issue during a chat interaction:
  1. Locate the Bug Report Icon: Click the flag icon next to the problematic chat message
  2. Choose Your Option:
    • Download Technical Report: Get a detailed technical report with all relevant data
    • Generate Bug Report: Send a detailed report directly to our support team
Technical Report Includes:
  • Page URL and host information
  • Session UID and message UIDs
  • Original query and chatbot response
  • Documentation usage indicator (True/False)
  • User and company details

​
2. Direct Support Channels

​
Essential Information for Bug Reports

To help our support team address your issue swiftly, include the following details:

​
Basic Information

  • User Name: Your system identifier (email or username)
  • Time of Occurrence: Exact date and time when the bug occurred
  • Environment: Specify if it happened in development, pre-production, or production
  • Brief Description: What problem did you encounter? Use simple, clear terms

​
Technical Details

User Agent Information: Your browser/application details when the bug occurred. Find this by entering navigator.userAgent in your browser console: How to find your user agent information Console Errors: If comfortable with technical details, check your browser console:
  1. Right-click on the webpage
  2. Select “Inspect” or “Inspect Element”
  3. Click the “Console” tab
  4. Screenshot any error messages

​
Visual Evidence

  • Screenshots or Screen Recordings: Visual proof of the issue
  • Step-by-Step Reproduction: Provide exact steps to recreate the bug
Example reproduction steps:
  1. Log in to your account
  2. Click on the ‘Reports’ section
  3. Select date range ‘Last Month’
  4. Observe the error that occurs

​
Expected vs Actual Behavior

  • Expected Behavior: What you thought should happen
  • Actual Behavior: What actually occurred instead
The chat interface flag feature automatically captures most technical details, making it the fastest way to report chat-related issues.

​
Best Practices for Bug Reporting

​
Do:

  • Provide as much detail as possible
  • Include screenshots or recordings when relevant
  • Test if the issue is reproducible
  • Use clear, descriptive language
  • Include error messages exactly as they appear

​
Don’t:

  • Assume the cause of the problem
  • Skip steps in your reproduction guide
  • Use vague descriptions like “it doesn’t work”
  • Report multiple unrelated issues in one report
Our support team is committed to providing prompt and efficient assistance. Detailed bug reports help us resolve issues faster and improve the platform for all users.
⌘I