ServiceNow Financial Services Menlo Park, California

Robinhood

Enterprise Knowledge Search · IT Operations Automation

Robinhood had more than 250 fragmented IT, HR, legal, facilities, and procurement support queues, so employees had to navigate different intake paths for routine needs and the small tech-ops team was overwhelmed by password, policy, and onboarding requests.

2,200 hours saved per month
6X return on investment in Moveworks
70% employee ticket deflection rate
90% internal support satisfaction

Reported impact

Business outcome

Robinhood deflects 70% of employee requests without human intervention, saves more than 2,200 hours per month, achieved 94% employee satisfaction and 90% internal support satisfaction, and can bring new teams and acquisitions live in weeks instead of months.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Robinhood rebuilt employee services on ServiceNow before turning on AI. The team first standardized its knowledge base, documented IT and HR workflows, and assigned ownership for each process so the platform could act on governed data instead of sprawl. It then deployed Moveworks from ServiceNow as the conversational front door in Slack, where employees ask for password resets, software access, HR guidance, and onboarding help through one entry point. Behind that interface, IT Service Management and HR Service Delivery route each request through common workflows instead of hundreds of disconnected queues. The same foundation now supports newly acquired teams, reduces support-channel duplication, and is expanding toward a service-aware CMDB and automated hardware lifecycle management so Robinhood can keep scaling with an eight-person technology-operations team.

Data flow

Employees start in Slack through Moveworks for passwords, software, HR questions, and onboarding. Routine requests are answered or deflected there, while IT Service Management and HR Service Delivery route the remaining work through shared workflows so acquired teams and new departments can be brought onto the same operating model quickly.

Solution architecture

3 components · 2 layers
  1. Serving
    • Moveworks Acts as the conversational front door for employee support inside Slack.
  2. Orchestration
    • IT Service Management Runs Robinhood's standardized IT request, incident, and onboarding workflows.
    • HR Service Delivery Handles HR service requests on the same governed workflow foundation as IT.

Architecture clues

  • Robinhood is building a service-aware CMDB as a future system of truth for services and assets.
  • Robinhood reduced around 250 service workflows to just a handful of governed workflows.
  • The team standardized its knowledge base before enabling AI use cases.

Evidence from the source

Before a single use case went live, they standardized the knowledge base, documented IT and HR service processes, established ownership of every workflow, and rebuilt employee services on ServiceNow.
Behind the scenes, ServiceNow IT Service Management and HR Service Delivery routed each request through standardized workflows, regardless of which team fulfilled it.
Robinhood introduced Moveworks from ServiceNow as the front door for employee support.
Today, Robinhood deflects 70% of employee requests without human intervention, with 94% employee satisfaction and 90% internal support satisfaction.
We ultimately saved more than 2,200 hours per month with ServiceNow.
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
    5 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. ServiceNow

    Robinhood customer story

    First-party
    https://www.servicenow.com/customers/robinhood.html
    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

  • Sitemap last modified Aug 13, 2026 · ServiceNow · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Aug 13, 2026 · ServiceNow · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.