evidoria

← Back to browse

Good practice Imported

StateChat — the US State Department's Enterprise AI Chatbot Reaches 62,000+ Users, 90% Report Time Savings

United States of America · Washington · See the United States of America profile · See the Washington profile

Evidence: Observational / pre–post Top 15% 80/100 · Ask Evidence Copilot about this practice

The US State Department's enterprise AI chatbot StateChat grew from 150 testers to 62,000+ users by June 2026; a 2025 survey of 2,706 employees found 90% reported time savings and 96% would recommend it.

62,000+ users
Enterprise chatbot users (by June 2026)
150 testers
Alpha testers at launch (start of rollout)
8,000 users (approx.)
Beta users (beta phase)
90 %
Employees reporting time savings (Aug-Sep 2025 survey)
1.6 hours/week
Average time saved per task (Aug-Sep 2025 survey)
96 %
Would recommend the tool (Aug-Sep 2025 survey)
2,706 of 3,700 invited employees
Survey respondents (26 Aug-26 Sep 2025)
StateChat — the US State Department's Enterprise AI Chatbot Reaches 62,000+ Users, 90% Report Time Savings

Details

Maturity
Scaling
Promoter
U.S. Department of State
Period
2024-2026 (enterprise rollout; survey Aug-Sep 2025)
Keywords
internal operations, generative AI, workforce productivity, federal government

Context

On 27 July 2026, the U.S. Department of State published a public Generative AI Playbook built around the rollout of 'StateChat,' its enterprise chatbot for sensitive-but-unclassified work, jointly introduced by Chief Information Officer Kelly Fletcher and acting Chief Data and AI Officer Amy Ritualo. StateChat secured a FISMA High Authority to Operate after a year-long security review.

Objectives

Provide a secure, enterprise-wide generative AI chatbot to help State Department staff with everyday work tasks, with a staged adoption model documented for reuse by other agencies.

Activities

A staged seven-phase delivery model (Groundwork, Alpha, Beta, Launch, Driving Adoption, Deeper Functionality, Impact Assessment) took StateChat from 150 alpha testers to roughly 8,000 beta users to over 62,000 users by June 2026, about three-quarters of the Department's roughly 80,000-strong workforce. A department-run survey between 26 August and 26 September 2025, with 2,706 of 3,700 invited employees responding, measured usage and satisfaction.

Results

90% of regular users reported time savings, averaging 1.6 hours per week per task, and 96% said they would recommend the tool. The minority reporting no savings cited weak system integration and time spent verifying outputs.

Conclusions

CIO Kelly Fletcher acknowledged the department had 'wildly underestimated' the training and change-management effort needed. The outcome data comes from the agency's own survey of its own users rather than an independent audit, and no cost or error-rate figures are disclosed.

Implementation
Indicative cost
Medium (€50k–€500k) — No cost figures are disclosed in the public record.
Time to results
Medium (1–3 years) — Rollout 2024-2026: 150 alpha testers, then roughly 8,000 beta users, then over 62,000 users by June 2026, following the seven-phase delivery model; survey conducted 26 Aug-26 Sep 2025.
Staffing & skills
U.S. Department of State CIO Kelly Fletcher, Acting Chief Data and AI Officer Amy Ritualo, Department-wide adoption and change-management team

Conditions for success

  • Security accreditation: FISMA High Authority to Operate after a year-long security review
  • Staged seven-phase delivery model (Groundwork, Alpha, Beta, Launch, Driving Adoption, Deeper Functionality, Impact Assessment) with checklists and lessons learned
  • Sustained training and change-management investment, acknowledged as initially 'wildly underestimated'

Common failure modes

  • Minority of users reporting no time savings cited weak system integration and time spent verifying outputs
  • Training and change-management effort required was greater than initially planned

Commonly funded by

National / regional programmes

Indicative funding routes for practices of this type — always check each programme's current calls and eligibility rules.

Do you run this practice? Claim it — verified implementers get a public contact pathway and can propose corrections.

Data sources

Where this practice's information was retrieved from, and when.

Attachments

Similar practices you may find useful