Anthropic Retail North America

Carvana

IT Operations Automation

Carvana wanted AI to investigate production alerts inside Slack, but its homegrown Slackbots consumed engineering time and lacked the team-scoped access controls needed to expand safely across retail science, verification, and wholesale workflows.

56% fewer alerts
Answers 65% faster for the wholesale platform team's issue and alert triage

Reported impact

Business outcome

Carvana reduced alert noise by 56 percent, cut answer time by 65 percent for the wholesale platform team, replaced two internally maintained Slackbots, and extended AI-assisted investigation, release verification, and hourly operational checks across multiple engineering teams.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

Carvana replaced two internal Slack-based agent systems with Claude Tag so alert triage, root-cause analysis, and fix generation could happen in the collaboration channels teams already use. Claude Tag is packaged into per-team bundles that combine instructions, tools, and scoped access, then runs under separate identities against Carvana's cloud data warehouse and engineering systems. In production channels it monitors alerts, identifies code owners, checks tickets, build history, logs, and repositories, and posts investigations in the exact format each team expects. The retail science team can ask Tag to open a pull request from the analysis thread; the verification team automatically compares each release to a pre-ship log baseline and even adds new logging when evidence is missing; the wholesale platform team gives Tag read-only access to tickets, builds, and code so it can trace issues to underlying services. Human review remains in the loop before anything ships.

Data flow

Production alerts land in Slack, where Claude Tag automatically starts an investigation using team-specific bundles. Tag reads tickets, build history, logs, code, and data-warehouse records, posts a root-cause analysis, and can draft a pull request or file follow-up work before a human reviews and promotes the change.

Solution architecture

2 components · 2 layers
  1. Compute
    • Opus 5 Handles the broad range of reasoning tasks Carvana runs through Claude Tag.
  2. Orchestration
    • Claude Tag Monitors Slack channels, investigates alerts, checks internal systems, and proposes fixes or pull requests.

Architecture clues

  • Bundles package instructions, tools, and scoped access per Slack channel.
  • Some teams schedule hourly checks for failing pipelines and stale feature flags instead of continuous monitoring.
  • The verification team keeps its comparison logic as a skill in the repo next to runbooks and alert notes.

Evidence from the source

Claude Tag can run under its own scoped identities, so Carvana set up one connection to its cloud data warehouse, plus separate identities that give individual teams their own slice.
Claude Tag monitors the Slack channels where production monitoring warnings show up and automatically begins investigating.
Each case ended the way a careful engineer would, with a ticket filed, a pull request offered, or a fix deliberately not made.
In the retail science channel, alert volume declined 56% as Claude Tag helped teams address recurring root causes
On the wholesale platform team, Claude Tag reduced the time required to reach an answer by 65%
Transparency Evidence & methodology 100/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Anthropic

    Carvana customer story

    First-party
    https://claude.com/customers/carvana
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Sep 15, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.