AWS Logistics United States

DoorDash

Customer Service Automation · Enterprise Knowledge Search

DoorDash needed to handle hundreds of thousands of support calls with faster, lower-latency self-service for Dashers while keeping answers grounded, safe, and accurate.

2.5 seconds or less
50x
increase in testing capacity 50x
of calls per day fielded by generative AI solution 100Ks

Reported impact

Business outcome

DoorDash reported increase in testing capacity 50x, response latency with Anthropic's Claude 3 Haiku, and 2.5 seconds or less, improving generative AI contact center self-service with measurable gains in productivity improvement, customer experience, speed to market, and scalability.

  • Customer Experience
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

DoorDash uses Amazon Connect Customer, Amazon Lex, Amazon Bedrock, and Anthropic's Claude 3 Haiku in Amazon Bedrock to support generative AI contact center self-service. DoorDash needed to handle hundreds of thousands of support calls with faster, lower-latency self-service for Dashers while keeping answers grounded, safe, and accurate. In practice, the implementation runs transformation or AI logic on Amazon Bedrock, and delivers outputs through Amazon Connect Customer. Tickets, conversation history, knowledge articles, and operational context are consolidated into a governed cloud data layer; Amazon Bedrock applies analytics or model logic; results are surfaced through Amazon Connect Customer. The case study reports increase in testing capacity 50x, response latency with Anthropic's Claude 3 Haiku, and 2.5 seconds or less, showing measurable improvement after the rollout.

Data flow

Tickets, conversation history, knowledge articles, and operational context are consolidated into a governed cloud data layer; Amazon Bedrock applies analytics or model logic; results are surfaced through Amazon Connect Customer.

Solution architecture

6 components · 2 layers
  1. Compute
    • Amazon Bedrock Provides managed foundation models and prompt workflows for the application
    • Anthropic's Claude 3 Haiku in Amazon Bedrock Provides managed foundation models and prompt workflows for the application
    • Knowledge Bases for Amazon Bedrock Provides managed foundation models and prompt workflows for the application
    • Amazon SageMaker Supports model development, tuning, evaluation, or managed generative ai inference
  2. Serving
    • Amazon Connect Customer Runs the voice or contact-center workflow that end users interact with directly
    • Amazon Lex Handles conversational intent routing inside the self-service voice experience

Architecture clues

  • 2.5 seconds or less

Evidence from the source

2.5 seconds or less
increase in testing capacity 50x
of calls per day fielded by generative AI solution 100Ks
reduction in generative AI application development time using Amazon Bedrock 50%
response latency with Anthropic's Claude 3 Haiku
Transparency Evidence & methodology 90/100 reference value · 87% 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 value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/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
    6 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • 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 provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    DoorDash customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/doordash-bedrock-case-study/
    Source type
    Vendor-published customer story
    Published
    May 23, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.