Monitoring and reports
What a report contains, when it is sent, how approval works and what the reviewer sends back.
On this page
What is sent
A report covers 7 days. It is a summary, not a copy of your account.
- A plain-language summary of at most 1200 characters.
- Counts: bots, routines by state, connectors by status, tasks and Pages. Counts only, no names.
- Findings from the audit rules, each with a severity.
- Up to 3 recommendations, each citing its evidence.
- Short evidence texts of at most 280 characters each.
- The visibility map: for each kind of information, whether the bot could see it and why.
- The version of each module that produced the report.
The report format has no field for conversation transcripts, limits the length of every text and rejects fields it does not know. The service also rejects any report that names an organization: your organization comes only from the connection key.
If your bot uses the compliance module, it can also send the status of each control with the send_compliance_status tool: the control's reference, title, status (green, yellow, red or unknown) and short reasons. Evidence, attestations and documents are not part of that format and stay on the bot's computer. Your dashboard shows the latest status sent.
Connecting your bot
Your bot reaches the service through one connector in Grok Bot, a remote MCP server that takes a connection key as its bearer token.
Create a connection key
In your dashboard, under Bot connection, an admin of your organization chooses Create connection key and copies the key. It is shown only once.
Add the connector
In Grok Bot, open your Ambitious Bot and add a custom connector for a remote MCP server, with the server address shown under Bot connection.
Paste the key
Choose a bearer token for authentication and paste the connection key, then save. Every request carries the key in the Authorization header as Bearer followed by the key.
The service keeps a one-way fingerprint of each key, never the key itself. Revoking a key under Bot connection takes effect on the next request. An organization can hold up to 5 active keys.
Tool approval
Sending a report is a tool call in Grok Bot, and Grok Bot asks you to approve it. No routine sends data without that step.
Before it asks, the bot writes the report as a review Page so you can read exactly what would be sent. You can pre-approve the tool in Grok Bot if you prefer not to be asked every week.
The weekly report
A routine named ambitious-snapshot does the work. It runs daily for the first 7 days after monitoring starts, then weekly.
Look
The bot lists what it can see and gathers the account details the audit needs.
Compare
The audit module stores a snapshot and compares it with the previous one.
Find and recommend
Rules turn the comparison into findings, and the module picks the recommendations worth your time.
Review and send
The bot writes the review Page, builds the report and asks for approval to send it.
If sending fails, the bot tries again on later runs and stops after 3 failed attempts, then tells you. A recommendation that was already sent is not repeated for 21 days.
What the rules look for
- A routine that is failing.
- A connector that needs to be signed in again.
- A routine that has been paused for a while.
- A bot that has not been used recently.
- Open tasks that have not changed in a week.
- Two routines on the same bot with the same schedule.
Reviewer advice
A person reads each report: Ambitious, or a partner consultant you assign. The reviewer writes advice on up to 3 recommendations and can add an overall note.
You read the advice in your dashboard next to the report it belongs to. The reviewer does not change your bots; you decide what to ask your bot to do.
Each recommendation shows a status: open, advised, done or dismissed.
Sending feedback
You can ask your bot to send feedback to Ambitious, about one report or in general. It uses the send_feedback tool with the same approval step, and it works without a subscription.
Billing and access
Reports are accepted while your subscription is active. You can update your payment method, view invoices or cancel anytime in the billing portal.
Your reports and review history are stored in a database that holds only your organization's data. Members of your organization, Ambitious reviewers and a consultant with an active assignment can read them; reads by reviewers and consultants are logged.