Salesforce Public Sector California, United States

California Department of Motor Vehicles

Customer Service Automation · Document Processing

The CA DMV needed to replace legacy, siloed licensing and service systems with an omnichannel platform that could handle identity services for tens of millions of residents while cutting wait times, manual paperwork, and repeated handoffs.

175+ field offices
300+ kiosks
55 percent of the calls were solved via automated workflows
60 million transactions processed annually

Reported impact

Business outcome

The DMV shortened high-friction transactions, solved more calls through automation, and created a reusable digital-service architecture that supports new programs without repeating legacy modernization from scratch.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

The California DMV modernized core citizen-service workflows on Salesforce Customer 360 for Public Sector using Experience Cloud, Public Sector Solutions, MuleSoft, Service Cloud, Scheduler, Shield, Tableau, and CRM Analytics. Its Digital eXperience Platform gives residents a portal and chatbot front door, while Service Cloud captures those interactions alongside CTI and IVR context to build a 360-degree resident profile. If automation cannot finish the request, workflow rules and Salesforce Scheduler move the citizen into a virtual field-office appointment, while the same platform supports intelligent document processing, decision automation, and a mobile driver's license workflow tied to the DMV system of record. Shield, Tableau, and CRM Analytics add governance and operational reporting so the DMV can reuse designs across programs and measure where automated workflows deflect work before staff intervene.

Data flow

Residents start through Experience Cloud and chat, CTI/IVR activity is written into Service Cloud profiles, MuleSoft moves data among DMV programs and document workflows, Scheduler escalates complex cases to virtual appointments, and Shield plus analytics layers monitor service performance and security across the platform.

Solution architecture

9 components · 4 layers
  1. Ingest
    • MuleSoft Connects channel, document, and program systems into a unified digital workflow.
  2. Serving
    • Salesforce Customer 360 for Public Sector Provides the modernized core platform for California DMV citizen-service and licensing workflows.
    • Experience Cloud Runs the DMV portal and digital front door for self-service interactions.
    • Public Sector Solutions Supplies reusable application components for DMV program modernization.
    • Service Cloud Stores contact-center, CTI, IVR, and resident profile activity for agents and automation.
    • Tableau Provides dashboards for spotting service-delivery trends and events.
    • CRM Analytics Supports integrated reporting on operational performance and channel usage.
  3. Orchestration
    • Salesforce Scheduler Moves residents from automated channels into virtual appointments based on workflow rules.
  4. Governance
    • Shield Adds security and governance controls across DMV service data.

Architecture clues

  • Chat, CTI, and IVR all feed the same Service Cloud resident profile.
  • DXP is built on Experience Cloud, Public Sector Solutions, and MuleSoft.
  • The mobile driver's license pilot uses an elastic architecture tied to the DMV system of record and AWS.

Evidence from the source

An estimated 55 percent of the calls were solved via automated workflows.
Built on Experience Cloud, Public Sector Solutions, and MuleSoft, DXP is the new core system.
The amount of time it takes to apply for a REAL ID ... dropped from 35 to 7 minutes.
These actions and activities are then captured in a personalized profile record in Service Cloud via the Salesforce Computer-Telephony Integration (CTI) with the IVR.
Transparency Evidence & methodology 86/100 reference value · 89% 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 value86/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • 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. Salesforce

    California Department of Motor Vehicles customer story

    First-party
    https://www.salesforce.com/customer-stories/california-department-of-motor-vehicles/
    Source type
    Vendor-published customer story
    Published
    Sep 3, 2026
    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

  • Published on source page Sep 3, 2026 · Salesforce · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this