Dispute preparation agent

Brex’s Payment Operations team built an agent to prepare reasoned card-dispute submissions.

Company: Brex
Approach type: Agent
Work: Finance ops
Human involvement: Unknown
Deployment stage: Deployed
Evidence strength: Limited primary
Entry reviewed: 2026-09-17

Copy as MD Ask ChatGPT

How it works

card dispute → reasoned submission.

Apply dispute rules

The agent uses the dispute guide and the outsourced team’s operating procedure.^{[Source 1]}

Prepare the submission

It finds applicable arguments and articulates the dispute rationale.^{[Source 1]}

Where people stay involved

People review, approve, or guide the agent’s work here.

Not reported: The source does not establish the required human review boundary.

Supervision level
Not classified
- card dispute → reasoned submission^{[Source 1]}

How supervision levels work

Implementation details

Model: Not reported
Harness: Brex’s internal Retool-based agent builder.^{[Source 1]}
Sandbox: Not reported
Tool access: Not reported
Knowledge: More than 100 pages of dispute guidance and the BPO standard operating procedure.^{[Source 1]}
Context management: Not reported
Credentials: Not reported
Interfaces: Not reported

Validation and failure handling

Not reported: The available sources do not describe how the team checks the output.

Reported observations

These results come from the sources. Notes below each result explain what it covers and any reported limits.

Key observation

Brex reports preparation time fell from three hours to three seconds; measurement method is not provided.^{[Source 1]}

Reported by: Brex
Scope: Dispute preparation agent: Brex reports preparation time fell from three hours to three seconds; measurement method is not provided.

The source does not report the denominator of this figure.

About this result

Category: Adoption output
Evidence type: Reported measurement
What it covers: Dispute preparation agent: Brex reports preparation time fell from three hours to three seconds; measurement method is not provided.

Lessons

Not reported: The available sources do not report lessons from this work.

Back to agents

Improve this record

Give your coding agent the context and instructions to prepare a source-backed update.

Suggest on GitHub

Paste the prompt into your coding agent, then describe the correction or add a public source.

Preview prompt

Help me update the Internal Agents Map record for Dispute preparation agent at Brex.

Repository: https://github.com/steel-experiments/internal-agents-map
Record: data/agents/brex-disputes.yaml
Published record: https://internal-agents.com/agents/brex-disputes
Readable context: https://internal-agents.com/agents/brex-disputes.md

Use the correction or public source I provide in this conversation. If I have not supplied either, ask what I want changed before editing.

Use an existing checkout of this repository, or clone it if needed. Read the current record from the repository. Follow AGENTS.md, CONTRIBUTING.md, and the relevant instructions in data/schema.md.

Verify that the evidence supports the requested change. Preserve uncertainty and distinguish reported facts from catalog judgments. Follow the repository process for capturing new sources. If evidence is insufficient, explain the gap instead of inventing details.

Make a focused change on a branch. Regenerate derived files and run the required checks. Do not edit generated content by hand.

Show me the change, supporting evidence, and check results, including any checks you could not run. Ask whether to submit a pull request unless I already requested one. Do not merge the pull request. If you cannot edit the repository, prepare a source-backed issue draft.

Sources and research details

Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.

Agent, Human, Ops: How Brex Is Changing Roles and Workflowshttps://www.firstround.com/ai/brexCase study · Independent secondary · Last source verification: 2026-08-31
Preserved copy

Question coverage and scope

purpose: Reported
workflow: Reported
human involvement: Not reported: The source does not establish the required human review boundary.
implementation: Reported
validation: Not reported
observations: Reported
lessons: Not reported

Research details for every claim on this page

Summary
Statement type
Fact
Provenance
Reported
Confidence
Not assessed
Confidence reason
No explicit confidence assessment is recorded for this claim.
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides
Harness
Statement type
Fact
Provenance
Reported
Confidence
Not assessed
Confidence reason
No explicit confidence assessment is recorded for this claim.
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides
Knowledge
Statement type
Fact
Provenance
Reported
Confidence
Not assessed
Confidence reason
No explicit confidence assessment is recorded for this claim.
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides
Apply dispute rules
Statement type
Fact
Provenance
Reported
Confidence
Not assessed
Confidence reason
No explicit confidence assessment is recorded for this claim.
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides
Prepare the submission
Statement type
Fact
Provenance
Reported
Confidence
Not assessed
Confidence reason
No explicit confidence assessment is recorded for this claim.
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides
Key observation
Statement type
Metric
Provenance
Reported
Confidence
Medium
Confidence reason
Self-reported by the source; no independent verification.
Reported by
Brex
Scope
Dispute preparation agent: Brex reports preparation time fell from three hours to three seconds; measurement method is not provided.
Denominator
Not reported
Method
Not reported
Observation date
Not reported
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides
Operating model assessment
Statement type
Inference
Provenance
Catalog judgment
Confidence
Unverified
Confidence reason
The source describes Dispute preparation agent and its work, but does not establish whether a person must approve or inspect each successful output.
Observation date
2025-09-25
- SupportsAgent, Human, Ops: How Brex Is Changing Roles and WorkflowsUnderstanding complex rules and guides