Skip to main content
Belcenter AIHelp center
Support

Report a bug and track its resolution

Submit a private screenshot, track replies, and review release notes for each version.

In your logged-in area, the Report a bug button at the top of each page lets you inform the team of an issue. On small screens, it appears as a bug icon.

Submitting a report

  1. Stay on the affected page, then click Report a bug.
  2. Enter a title and describe the steps taken, the result obtained, and the expected result.
  3. Review the screenshot prepared before opening the form. You can remove it. Password and secret fields are masked, but other visible data on the page may appear: review them before sending.
  4. Click Send. You will be taken to your request tracking page.

The affected page, bot or conversation, and the version used are attached to the report. The browser and screen dimensions assist with diagnostics. The screenshot captures the visible BeAI page, not the desktop or other tabs. Some embedded or external content may be missing. If the screenshot fails, you can send the text and context without an image.

If submission fails, your text remains available. You can try again without creating duplicate reports. A maximum of ten new reports per user per hour are permitted. Any screenshot attached via the API must be in PNG or JPEG format, up to 4 MB, within the dimension limits documented in the API.

Tracking responses

Open your avatar, then My reports. A badge on the report button indicates unread updates. Open a request to view the thread, reply, or add more details. You also receive an email whenever someone updates your request.

The statuses are New, In progress, To be specified, Resolved, and Closed. The platform team can update them. You can continue to provide further details in the thread. If someone modified the request while you were writing, save your text elsewhere, reload the request, and publish again.

Your reports and their screenshots are visible only to you and platform administrators. An organisation manager or reseller cannot access other users' requests by virtue of their role alone.

For platform administrators

The administration menu includes Bug tracking: all requests, filterable by status, with their screenshot, context, and message history. New reports and replies trigger an in-app notification and an email. Post a reply and update the status to keep the author informed. Emails include an authenticated link, without copying the description or screenshot.

Finding what's new

After each release, a modal automatically presents what's new once per account and version. An already open page checks for new versions every minute when visible, as well as when you return to the tab. If a modal, screenshot, or unsaved changes are active, the presentation waits for them to finish and then resumes automatically, without losing your work. A background tab does not mark updates as viewed.

The automatic modal only shows versions released since your last read point. On a first visit, it displays only the most recent version. Your read point is stored on your account, even if you switch browsers or devices; it does not rely on a cookie. Viewing an older version later does not move this point back.

Click View full history in the modal or Version … · What's new in your avatar menu to review all updates at any time. Viewing the modal on another device signed in to the same account also counts as a presentation; the history remains accessible from this menu.

The public API offers the same actions and permissions via /api/v1/bug-reports and /api/v1/releases; refer to its documentation from your account.

The GET /api/v1/releases API returns the last_seen_version point, the unread_releases list to show automatically, and the full history releases. Fetching this endpoint alone does not mark anything as read; POST /api/v1/releases/seen is sent after the modal is actually displayed. The portal uses the same private state.

Documentation updated with the application