What a Brainmox agent does.
Five practical workflows.

1. Turn meeting notes into an action list

Observed example · fictional meeting notes

Start with: Notes containing decisions, named owners and stated deadlines. Include corrections explicitly, keeping the original wording available for comparison.

Result: An editable action list or CSV with task, owner, due date, source note and unresolved question.

1. Give the assistant the notes and request one row per action, preserving source references.
2. Require missing owners or dates to remain unresolved; distinguish decisions from suggestions.
3. Clarify an ambiguous item, request an updated file and compare the changed row with the original.

In our existing demonstration, five fictional notes produced an action list, followed by a correction to an owner and a deadline. The linked walkthrough preserves both CSV versions. Use those artifacts to judge how a correction reaches the delivered file, rather than treating a polished summary as evidence of accurate assignments.

Your review: The meeting organizer checks every assignment and deadline before sharing the list. A suggested owner is not an accepted assignment.

Stop and check: Stop if the list assigns an unnamed owner, invents a deadline or drops an unresolved question. Return the row with the exact source text and ask for a correction.

Inspect the original and revised action lists →

2. Prepare Gmail replies for review

Observed example · fictional email threads

Start with: Selected Gmail conversations, the account to use and explicit limits on promises, availability and sending.

Result: Saved reply drafts that you open and inspect in Gmail.

1. Connect the intended Gmail account in Draft mode and identify the conversations to read.
2. Ask for replies grounded in the thread, with questions for missing or conflicting information.
3. Open each draft in Gmail and compare it with the actual source, including later corrections.

The three observed cases cover a missing attachment, a corrected meeting date and an ambiguous next step. The meeting case needed a clarification because the correction arrived in a separate thread. Draft mode restricts sending through Brainmox's tools; Google's underlying consent is broader, and reading messages can attempt to mark them read.

Your review: The sender checks To/Cc, the newest message, attachments, dates, commitments and formatting before deciding to send.

Stop and check: Stop if the reply claims to have read a missing file, confirms unapproved availability or uses an older date. Fix the draft and recheck the thread.

See the saved drafts and permission boundaries →

3. Assemble a weekly client report

Observed example · six fictional project updates

Start with: Dated project updates, the reporting period, completed outcomes, blockers and next steps. Name the source for each update.

Result: A Word report plus a CSV task ledger that can be reconciled against the supplied notes.

1. Gather the current updates and specify the reporting cutoff and timezone.
2. Ask for a report and a task ledger, keeping uncertain status separate from completed work.
3. Open both files, reconcile each reported outcome with its source and correct inconsistencies.

Our linked example includes the actual Word report and six-row CSV returned by Brainmox, the fictional source notes and the review findings. The review identified limits around source freshness, timezone wording, summary categories and formatting. Repeating this task on a schedule still requires fresh inputs and a person checking the result.

Your review: The project owner checks completed totals, overdue work, freshness, status labels and the document's formatting before distribution.

Stop and check: Stop if stale notes are presented as current, the report counts planned work as completed or its totals disagree with the ledger. Resolve the source discrepancy before sharing.

Download the actual report, ledger and templates →

4. Compare two versions of a project brief

Illustrative how-to · no observed run

Start with: Two clearly named, readable files: brief-v1 and brief-v2. Specify the fields to compare and which version is newer. Keep the originals unchanged.

Result: A comparison table with field, old wording, new wording, source location and question for the reviewer.

1. Provide both files through the supported file workflow and ask the assistant to confirm it can read each one.
2. Request a field-by-field comparison of scope, owner, delivery date and unresolved decisions, quoting short source passages.
3. Ask for differences and unanswered questions in a separate file; verify the output without overwriting either original.

Try this fictional fixture: brief-v1 says ‘Homepage copy; owner Sam; delivery October 15.’ Brief-v2 says ‘Homepage and navigation copy; owner Sam; delivery October 22.’ The expected comparison identifies the added navigation scope and the date change, retains Sam and flags that acceptance of the new scope is not stated. This expected result is authored for evaluation, not output from Brainmox.

Your review: The project owner opens both originals and checks every reported change, including sections the assistant says are unchanged.

Stop and check: Stop if either file is unreadable, the comparison misses the added scope or it treats a proposed change as approved. For scanned or complex files, inspect extracted text and tables; file support does not guarantee faithful interpretation.

Check supported file capabilities →

5. Prepare a recurring morning briefing

Illustrative how-to · no observed scheduled run

Start with: Selected calendar events and dated task notes, an explicit timezone and a defined briefing destination. Connect only the sources the job needs.

Result: A short brief listing today's commitments, preparation, overdue follow-ups and decisions, with source references and missing-source warnings.

1. Run the briefing once on a bounded set of sources and compare the result with the originals.
2. After correcting the instructions, configure a recurring prompt such as weekdays at 8:00 a.m. America/Toronto.
3. Check the first scheduled occurrence and its originating conversation or channel. Verify the next run after changing a source fact.

For a fictional test dated October 8, provide a 10:00 a.m. America/Toronto project review and a task note saying ‘send the revised brief by October 7; completion unknown.’ The expected result includes meeting preparation and flags the overdue task for a status check. It must not claim the file was sent. Repeat with the task source unavailable: a useful brief identifies the gap instead of treating the missing source as an empty task list. These are test expectations, not measured scheduling results.

Your review: The person receiving the brief checks times, priorities, omissions and source freshness. They decide what to act on.

Stop and check: Stop if the brief silently omits an unavailable source, reports the wrong timezone or presents a suggestion as a confirmed commitment. Correct the source or schedule before relying on the next run.

Use the morning-brief instruction and review schedule →

Set up the sources, access and review first

Brainmox is a managed cloud assistant with supported file tools, account connections, searchable memory and schedules. File work needs readable source material; Gmail needs a connected account with the chosen access; a scheduled briefing needs an explicit timezone and accessible sources. Instructions describe the task, while permissions govern the available actions.

When to keep the task with a person

Keep decisions with a person when authority is unclear, a source cannot be verified or a wrong action would create a consequential commitment. An assistant can prepare a comparison or draft; accepting scope, promising a deadline and sending a client message remain separate decisions. Test one bounded job before adding more sources or external actions.

Choose one workflow and define a pass

Write down the frequency, required sources, access, consequence of an error, reviewer and evidence of success. Start with a result you can inspect directly: a corrected row, a saved draft or a report reconciled with its inputs.

Download the workflow-selection checklist (plain text)

Choose a workflow you can evaluate

Need to choose the tool before trying a workflow? Compare AI assistants by task and cost.

Start with material you are allowed to share, a bounded task and an output you can check yourself. Record corrections before repeating the workflow. These examples do not establish customer time savings or a guaranteed result.

For the difference between suggested text and delegated work, read agents, chatbots and copilots. For an unanswered request, use the client follow-up examples.

Brainmox's private-beta offer is $299 USD/month or $2,990/year for one assistant, with supported usage under beta limits. Signup requires an invitation code; join the waitlist to request one, or read how access works.

See the product overview and the private-beta offer, or use the assistant evaluation scorecard and the workflow cost worksheet to structure your review.