Support quality agent

Brex uses an agent to assess support interactions against its quality rubric and surface trends for team leads.

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

Copy as MD Ask ChatGPT

How it works

support interaction → rubric assessment and quality trends.

Assess interactions

The agent reviews support responses against Brex’s quality rubric.^{[Source 1]}

Feed back trends

Team leads use quality trends to coach staff and improve responses.^{[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
- support interaction → rubric assessment and quality trends^{[Source 1]}

How supervision levels work

Implementation details

Model: Not reported
Harness: Not reported
Sandbox: Not reported
Tool access: Not reported
Knowledge: Brex’s support-quality rubric.^{[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

Not reported

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 Support quality agent at Brex.

Repository: https://github.com/steel-experiments/internal-agents-map
Record: data/agents/brex-support-qa.yaml
Published record: https://internal-agents.com/agents/brex-support-qa
Readable context: https://internal-agents.com/agents/brex-support-qa.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: Not 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 WorkflowsRedesign roles: support quality assurance
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 WorkflowsRedesign roles: support quality assurance
Assess interactions
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 WorkflowsRedesign roles: support quality assurance
Feed back trends
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 WorkflowsRedesign roles: support quality assurance
Operating model assessment
Statement type
Inference
Provenance
Catalog judgment
Confidence
Unverified
Confidence reason
The source describes Support quality 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 WorkflowsRedesign roles: support quality assurance