The Center of CX
Subscribe
Government & Public Sector: State Government

State Government CX Stack Framework

State government contact centers handle the interactions citizens encounter most frequently: driver's licenses, unemployment benefits, Medicaid enrollment, professional licensing, and state taxes. The CX challenge is breadth: a single state government may run many separate contact centers across different agencies with different systems, different cultures, and different funding models.

Map your current capabilities across all 7 layers: 35 checkpoints. Mark what you have, what you need and what is planned. Your answers stay in this browser tab.

Figures for this segment

No public benchmark exists for these figures in this segment. Measure your own with the tool named beside each.

State Medicaid and CHIP call centers during the unwinding

7.1 million to 10.9 millionMACPAC (Medicaid and CHIP Payment and Access Commission) 2024

Monthly calls, April to August 2023

National figures from state reports to CMS, summarized by MACPAC for April 2023 to June 2024, when states renewed every enrollee after the pandemic coverage protections ended. These are peak months, higher than a typical one; state results varied widely.

State Government: the 7-layer CX stack

For each capability, mark whether you have it, need it or have it planned.

0 of 35 marked

Layer 7: Analytics & Governance

0 of 5 in place

Measure and govern. Vendors in this layer include NICE, Verint, Qualtrics.

  • Agency-specific satisfaction tracking across service lines
  • Unemployment claim processing time and citizen communication analytics
  • DMV wait time and transaction completion analytics
  • Medicaid enrollment success rate and abandonment tracking
  • Legislative reporting on service levels and citizen complaints

Key risk: Governor's office receiving citizen complaints without agency performance context

Layer 6: Routing & Orchestration

0 of 5 in place

Route the work. Vendors in this layer include Genesys, NICE CXone, Amazon Connect, Cisco.

  • Multi-agency routing: citizens often call the wrong agency first
  • Unemployment surge routing during economic downturns
  • DMV appointment scheduling and walk-in queue management
  • Medicaid enrollment routing with eligibility pre-screening
  • Tax season routing with dedicated teams for filing assistance

Key risk: Citizen transferred between several agencies before reaching the right one

Layer 5: Conversation Management

0 of 5 in place

Hold the conversation. Vendors in this layer include Granicus, Adobe, Salesforce, custom portals.

  • Citizen portal integration for self-service across state agencies
  • Proactive notifications for benefit status, deadlines, and renewals
  • Multilingual communication for diverse state populations
  • Accessible channels meeting state accessibility requirements
  • Appointment scheduling for DMV, licensing, and in-person services

Key risk: Benefit renewal deadlines missed because notifications didn't reach the citizen

Layer 4: Reasoning & Planning

0 of 5 in place

Decide the next step. Vendors in this layer include Amazon Lex, Google CCAI, Cognigy, Ada.

  • Benefits eligibility screening bots for Medicaid, SNAP, and TANF
  • DMV transaction bots for registration renewal and appointment scheduling
  • Unemployment claim status bots with real-time case data
  • Tax filing status and refund tracking bots
  • Professional licensing renewal and status bots

Key risk: Bot incorrectly screening Medicaid eligibility and deterring eligible citizens from applying

Layer 3: Policy & Guardrails

0 of 5 in place

Set the rules. Vendors in this layer include StateRAMP-certified vendors, ID.me, LexisNexis.

  • StateRAMP or equivalent cloud security requirements
  • State-specific accessibility and language access mandates
  • Unemployment fraud detection and identity verification
  • Medicaid enrollment and renewal compliance (CMS requirements)
  • State privacy laws (varying by state: some stricter than federal)

Key risk: Unemployment fraud from identity verification failures in the contact center

Layer 2: Workflow Execution

0 of 5 in place

Do the work. Vendors in this layer include Salesforce Gov Cloud, Pega, Appian, Deloitte/Accenture custom.

  • Unemployment claim filing and weekly certification workflow
  • Medicaid application and renewal workflow with CMS compliance
  • DMV transaction workflow: licenses, registration, titles
  • Professional licensing application and renewal workflow
  • Tax filing assistance and refund tracking workflow

Key risk: Unemployment claim processing taking weeks while citizens exhaust savings

Layer 1: Data Access

0 of 5 in place

Know the customer. Vendors in this layer include Deloitte, Accenture, CGI custom systems, IBM mainframes.

  • Benefits eligibility systems (Medicaid, SNAP, TANF, unemployment)
  • DMV systems: driver records, vehicle registration, titles
  • State tax systems: filing status, refund processing, audit
  • Professional licensing databases across license types
  • Inter-agency data sharing for integrated eligibility determination

Key risk: Legacy eligibility systems unable to provide real-time data to the contact center

Mark at least 18 capabilities to see your profile (0 of 35 so far).

Sources and assumptions

Every figure on this page is a published figure checked on the publisher's own page, a labelled planning assumption you can test with your own numbers, or a worked example.

Published figures

Planning assumptions

  • 20 to 30%: Share of transfers a statewide front door that classifies intent can remove. From practice; no public before and after figure exists. Count your cross-agency transfers before and after. Test with your numbers in FCR Leakage Diagnostic.

Worked examples

  • 45 minutes: Illustrative cross-agency transfer chain. An illustrative scenario with no measured journey.

No public benchmark

  • Average handle time, state contact centers. No regulator or trade body publishes handle time for this segment. Measure yours in AHT Decomposition.
  • First contact resolution, state contact centers. No regulator or trade body publishes first contact resolution for this segment; SQM's government figure covers its government participants as a whole. Measure yours in FCR Leakage Diagnostic.
  • Customer satisfaction, state contact centers. No public satisfaction figure exists for this segment's contact centers; ACSI publishes federal agency index scores, carried as a measure on the federal page.
  • Self-service containment, state contact centers. No regulator or trade body publishes self-service containment for this segment. Measure yours in AI Deflection Reality Check.