Braio

Public help

Czytaj po polsku

Braio help - first workflow, QA and SEO/GEO reports

Start with one task and a clear result. This help covers basic product requirements and limits without publishing an organization's internal documentation.

Feature names and availability may depend on role, plan and workspace configuration. If a feature is not visible, confirm access with your administrator or the Braio team.

Content reviewed:
01

A first finance workflow on synthetic data

Start with the public cash-flow pack before attaching company files. Inspect the sheets, mappings, currency and private profile; you activate proposed settings after reviewing them. Choosing a starter prepares a screen and does not launch paid work.

The chat accepts XLSX, CSV, PDF and DOCX within limits, but dedicated calculations require structured sources and supported formulas. Unsupported inputs, missing sources or failed controls can block a process. The original is retained and missing data is not presented as zero.

02

Your first task in four steps

Choose a small, repeatable process. These are preparation instructions, not the result of a completed rollout.

  1. 01Define the expected artifact and acceptance criteria: what should be produced and how you will judge its usefulness.
  2. 02Check your role, agent access and permissions for the required sources.
  3. 03Run the agreed task and handle required consent where configured.
  4. 04Assess the result, cost and limitations. Record what needs improvement before increasing scope.
03

Assessing a QA report and fix

A report concerns a particular scenario and run. Review the evidence and distinguish an application defect from an obstacle to executing the test. The fix loop requires repository access and does not merge PRs on its own.

A retest after merge checks the outcome. An incomplete retest does not confirm a fix. The fix loop allows up to two attempts for one issue.

04

What the SEO/GEO report measures

In SEO/GEO, submit up to 10 public URLs. Braio reads raw HTML without executing JavaScript and checks access, directives, structure and page data. An agent can assess content using the collected facts; a report identifies a measurements-only run when no agent assessment is available.

The 0-100 score describes page readiness. It is not a Google ranking or a prediction of ChatGPT recommendations. The report does not measure actual citations, off-site mentions, keyword volumes or GSC data. We do not claim PDF/CSV export or screenshots from browsing the page here.

  • One active report per workspace; access depends on role.
  • Model calls are metered; the operation can require cost consent according to configuration.
  • Findings require review. An audit does not change the site or guarantee indexing.
05

Integrations and developer access

Slack and Teams need setup and organization consent. Repositories and other tools have their own permissions. Test installation, user identity and result delivery before wider rollout.

Confirm QA API/MCP access, token scope, limits and the current setup process for your deployment. The existence of code does not establish an available public CLI package or marketplace listing.

06

What to include in a support request

Include the feature, time, expected and actual result and task identifier if available. Do not send API keys, passwords or customer data in public channels. Agree on access and investigation with the workspace administrator or Braio team.

Questions and answers

Does a high SEO/GEO score guarantee an AI recommendation?
No. Technical readiness, an actual citation and a product recommendation are different outcomes. Search engines and models select their own sources.
Why can I not see a feature described on the website?
Check role, plan, configuration and integration status. A description of a capability does not replace confirming availability in your workspace.