How to get help and report a bug

Open the in-app help form and send a useful bug report without sharing sensitive information.

Last updated About 1 hour ago

Use the in-app help menu when allmates.ai does not behave as you expect. A useful report explains what you tried, what happened and what you expected, without exposing credentials or another person's private content.

Open the help menu

At the bottom of the left sidebar, select the bug icon labeled Feedback / Report a bug. You can also select Help & resources, then select Feedback / Report a bug from the menu.

The Help & resources menu with Documentation, Changelog and Feedback / Report a bug.

Feedback / Report a bug opens the Bugs form. Put a short title in Have something to say? and the details in Describe your request. Review any screenshot before you select Send.

The Bugs form with a title, a description, Take screenshot and Send.

If you need a guide rather than a bug report, select Documentation. It opens the allmates.ai help center in a new tab.

Report an error from a conversation

When a Mate reply ends with an error, select Report below the error. The same bug feedback form opens with the failed message identified for the support team.

Some connection errors show their own recovery action instead of Report. Use Feedback / Report a bug from the sidebar when you still need to report one of those errors.

What to include

Start with one sentence that names the action and the problem. Then add:

  • the steps that reproduce the problem,
  • what you expected to happen,
  • what happened instead, including the exact visible error,
  • the approximate date and time,
  • whether it happens every time or only sometimes,
  • the browser and device you used,
  • a screenshot or short recording when it makes the problem clearer.

Name the workspace or conversation only when support needs it and you are allowed to share it. A small, safe example is more useful than a full customer conversation.

Share a safe example

Remove or replace personal data, customer names and confidential text. Keep only the minimum input needed to show the problem.

Never include:

  • passwords, sign-in codes or recovery codes,
  • API keys, access tokens or connection secrets,
  • private content from another person's conversation,
  • a full confidential document when a short redacted sample reproduces the issue.

If the problem involves a file, create a small test file with the same format and structure when possible. If it involves a conversation, reproduce it in a new private chat with non-sensitive content. State that the example is a reproduction.

Before you send

Check whether reloading the page changes the result. For a service interruption, check any notice shown in the app and follow its link for more information. Do not repeat an action that could create duplicate data or send the same message several times.

Read your report once as if the reader cannot see your screen. Make sure the steps, expected result and actual result are distinct.

Good to know

  • A bug report helps the team investigate; it does not guarantee an immediate fix.
  • Do not post credentials, even when an error mentions authentication.
  • Keep one report focused on one problem. Submit a separate report for an unrelated issue.