Support and Feedback

Bitment's support model runs through the product itself: the AI knows how the product works and can teach you a feature or do it for you, and the same conversation is how you tell the Bitment team something is broken or missing.

Where to find it

Open the AI (Chat, or the Assistant panel in the top menu bar) from anywhere in the product. There's no separate help center or support ticket form to navigate to.

Key concepts

The product manual: a set of hand-written pages describing every feature, that the AI reads from directly rather than guessing.
Feedback ticket: a report you file through a conversation with the AI, which lands in the Bitment team's backlog.
Diagnostics consent: a toggle in your account settings controlling whether the Bitment team's engineers can load a diagnostic view of your session to help troubleshoot a problem.

Ask the AI

For "how do I" and "where is" questions, ask the AI directly rather than hunting through menus. It has read the actual, current product manual for every app, so its answers describe real screens and real controls, not an invented workflow. In many cases it can also just do the thing for you rather than only explaining it.

File feedback

If something is broken, missing, or just confusing, tell the AI and ask it to file feedback.

Describe the problem to the AI in a chat, in whatever detail you have.
Ask it to file feedback (or feedback about a bug, a missing feature, anything you'd report).
The report goes straight into the Bitment team's backlog, carrying the context of your conversation with it.

Attach a screenshot for a visual bug. Paste or drag a screenshot (or a log file) into the same part of the conversation as your report, before asking the AI to file it. The AI carries attachments from your most recent message that had any, so the Bitment team sees exactly what you saw. If you attached something unrelated to the report, say so and the AI leaves it off the ticket.

What happens to feedback

Once filed, a feedback ticket goes into the Bitment team's own triage workflow. It isn't a black hole: the team works through filed feedback the same way any product backlog is worked, using the conversation context and any attached screenshots to understand the report without having to ask you to reproduce it.

Your account settings include a diagnostics toggle controlling whether a Bitment engineer is allowed to open a "view as" session against your account to help diagnose a problem (see Identity model for how that session works). It's opt-in: until you turn it on, that kind of session can't be opened against your account at all. If it's ever used, the operator interface shows a visible banner for as long as that session is active, so it's never invisible to you.

Requesting an app be enabled

Not every app is turned on for every person by default. If an app you expect isn't in your dock, ask the AI (or the Bitment team directly) to have it enabled; app access is turned on per person by the Bitment team.

Release notes

Bitment publishes a note for each deployment describing what changed and why. These aren't in-product yet as a browsable changelog; ask your Bitment contact if you want the history for a specific stretch of time.