Lighthouse AdvisorySLED AI Adoption Intelligence

State Government

Four newly archived sources juxtapose measured state citizen-service AI capacity with same-week regulatory build-outs. South Carolina’s Tyler “Bradley” Resident AI Assistant (06/30/2026 investor release) reports >38,000 questions since Sep 2025, 82.2% first-contact resolution, and 54-language support from verified .gov content. Texas DPS’s Amazon Connect driver-license contact center (StateTech 07/02/2026) cites 68% routine-case deflection and >10,700 additional weekly cases after AI-enabled self-service. On 09/21/2026 New York began operationalizing the RAISE Act—November registration for large frontier developers, DIGIT inside DFS, 72-hour critical-incident reporting, and Jan 2027 compliance—while CSBS’s newly public AI Supervisory Framework (announced 09/16; Guide approved 08/13) gives state bank examiners a discretionary GenAI/inventory/vendor scoping tool without creating new legal duties. One pattern: treat published chatbot/contact-center KPIs as necessary but incomplete without examiner and frontier-developer registration controls that states are now standing up.

Evidence records
4
Cross-source patterns
1
Evidence classes
2 independent reporting1 vendor claim1 public-sector association guidance
Outcomes
3 emerging1 mixed
Source freshness
2 recent2 new this fortnight
Research completed
2026-09-22

Choose a role to see its takeaway beside every record in the ledger.

Patterns across the evidence

Synthesis · Lighthouse Advisory interpretation

1 pattern, each supported by at least two sources
  1. Citizen-service AI capacity metrics are advancing beside state financial-regulatory AI exam and registration build-outs

    SC Bradley and Texas DPS publish engagement/deflection metrics for resident information and driver-license channels, while New York’s DIGIT/RAISE registration timeline and CSBS’s examiner framework show states simultaneously operationalizing frontier-developer and supervised-institution AI controls. Treat chatbot KPIs as incomplete without parallel registration/exam readiness.

    Operating questionWhen a state cites chatbot or contact-center AI capacity gains, what examiner inventory, GenAI policy, and frontier-developer incident-reporting controls are being stood up in parallel?

    Supporting evidenceSouth Carolina Department of Administration / Tyler TechnologiesTexas Department of Public SafetyState of New York (Governor Hochul / Department of Financial Services DIGIT)Conference of State Bank Supervisors (CSBS)

Evidence ledger

Full record · every source keeps its link and limitations

4 records
  1. Vendor claimEmergingRecent

    South Carolina Bradley Resident AI Assistant reports 82.2% first-contact resolution on verified .gov answers

    Why now: archive already covers Nebraska Navigator expansion but lacked South Carolina’s sibling Tyler Resident AI Assistant metrics. Tyler’s 2026-06-30 investor release, quoting SC CIO Nathan Hogue, states that Bradley—live since September 2025 and answering only from verified .gov sites—handled more than 38,000 questions from over 10,800 unique users, averaged 195 questions/day (peak 426), achieved an 82.2% first-contact resolution rate, ran 24/7 with 15% weekend interactions, and supported 54 languages (~6% non-English). Emerging/measured engagement signal for statewide citizen information bots, not an independent outcome evaluation.

    South Carolina Department of Administration / Tyler TechnologiesSouth Carolina, United States2026-06-30

    Why it matters, evidence and limitations
    Why it matters
    Gives peer states concrete engagement and FCR-style metrics for a Tyler Resident AI Assistant deployment spanning DMV, courts, and tax information discovery—useful when comparing AskCA/Nebraska-style statewide navigators.
    Evidence and measured results
    Tyler IR/Business Wire 06/30/2026: >38,000 questions; >10,800 unique users since Sep 2025; avg 195/day peak 426; 82.2% first-contact resolution; 15% weekend; 54 languages / ~6% non-English; answers sourced from verified SC .gov websites; SC CIO Hogue quote on single trusted starting point; analytics on vehicle, legal/court, and tax intents.
    Limitations and uncertainty
    Vendor-published metrics; FCR definition and sampling method not disclosed; commercial interest; June date older than prefer-window—included because URL/metrics were not in archive and parallel Nebraska story should not monopolize Tyler chatbot evidence.
  2. Independent reportingMixedRecent

    Texas DPS driver-license contact center cites 68% routine-case deflection after AI-enabled rebuild

    Why now: prior stream coverage emphasized Texas DIR AI sandbox stand-up without published Driver License Division capacity outcomes. StateTech (2026-07-02) reports DPS CIO Jessica Iselt Ballew describing an Amazon Connect + Salesforce rebuild with AI-powered virtual agents, chat, text, and IVR. Historically ~640,000 monthly calls with ~10% live answer rate; modernization reportedly handles eight times more cases, triples weekly chat/IVR inquiries, deflects 68% of routine cases, and adds >10,700 weekly case capacity—while status checks were ~40–45% of call reasons. Mixed: strong capacity claims but AI contribution not isolated from broader cloud CRM redesign.

    Texas Department of Public SafetyTexas, United States2026-07-02

    Why it matters, evidence and limitations
    Why it matters
    Concrete licensing/transport shared-service metrics for states facing DMV/driver-license call-center backlogs—pairs automation deflection with human escalation rather than headcount-only scaling.
    Evidence and measured results
    StateTech 07/02/2026 citing Ballew at AWS Summit: pre-change ~640k monthly calls / ~200 concurrent capacity / ~10% answered; 40–45% callers sought license status; post-change eight times more cases; weekly chat/IVR inquiries tripled; 68% routine deflection; >10,700 additional weekly cases; unified agent desktop replacing up to eight systems.
    Limitations and uncertainty
    Trade press of conference remarks; baselines span multi-year modernization; AI vs IVR/CRM effects conflated; July date older than prefer-window—included as unarchived measured licensing outcomes newly relevant beside DIR sandbox narrative.
  3. Independent reportingEmergingNew this fortnight

    New York begins RAISE Act registration build-out via DIGIT in DFS with 72-hour incident reporting

    On 2026-09-21 Gov. Hochul announced next implementation steps for the Responsible AI Safety and Education (RAISE) Act: large frontier AI developers begin registering in November; compliance and regular reporting to the new Office of Digital Innovation, Governance, Integrity and Trust (DIGIT) inside DFS begin January 2027; critical safety incidents must be reported to DIGIT within 72 hours; quarterly catastrophic-risk assessments and biennial disclosure statements are required; Marc Gilman was appointed deputy director for RAISE as DIGIT’s first full-time hire; DIGIT will issue an annual public report. Emerging regulatory operating capacity—not yet an enforcement record. Cross-check: amNY quotes Hochul that AI kill-switch exploration carries “No commitments at this time.”

    State of New York (Governor Hochul / Department of Financial Services DIGIT)New York, United States2026-09-21

    Why it matters, evidence and limitations
    Why it matters
    Shows a peer state moving from enacted frontier-AI statute to staffing, registration, and incident-reporting operations housed in a financial regulator—directly transferable planning signal for other state CIOs/AGs watching CA/IL/NY safety regimes.
    Evidence and measured results
    CBS6 09/21/2026: November registration start; DIGIT within DFS; Marc Gilman deputy director; Jan 2027 compliance; 72-hour critical incident reports to DIGIT; quarterly catastrophic-risk filings; biennial disclosure; public tip pathway; annual DIGIT report; AG James enforcement statements. amNY corroboration of exploratory kill-switch language without commitment.
    Limitations and uncertainty
    Independent reporting of announcement—not a .gov primary release URL located this run; registration portal UX unpublished; kill-switch not a current requirement; effectiveness awaits 2027 filings.
  4. Public-sector association guidanceEmergingNew this fortnight

    CSBS releases discretionary AI Supervisory Framework for state bank and nonbank examiners

    Why now: same-week NY DIGIT/DFS RAISE build-out elevates how state financial regulators will examine AI; CSBS’s framework was not in the archive. Publicly announced 2026-09-16, the Core Examiner Guide v1.0 (approved 2026-08-13) gives state examiners a proportionate, discretionary tool to scope AI use, request governance/inventory/GenAI documents, and reuse existing third-party, model-risk, consumer-protection, and operational-risk procedures. It expressly does not create new legal obligations; each state agency decides incorporation. Emerging control infrastructure for supervised institutions—not measured exam outcomes.

    Conference of State Bank Supervisors (CSBS)United States (all state banking/nonbank supervisors; agency-optional adoption)2026-09-16

    Why it matters, evidence and limitations
    Why it matters
    Provides the concrete examiner question set and document-request list state banking departments may apply to GenAI/chatbots/vendors—material for state CIOs whose agencies or regulated entities will face these exams, and for GovOps comparing financial-regulator AI oversight maturity.
    Evidence and measured results
    PDF v1.0 approval 08/13/2026; sections on Initial Scoping, Document Request List, Governance and Oversight, AI Inventory and Use Cases, Generative AI and Emerging Use, and Use of Existing Supervisory Resources; statement that guide does not create new legal obligations; newsroom 09/16/2026: discretionary tool; each state agency determines incorporation; usable by industry for self-assessment.
    Limitations and uncertainty
    Optional; not federal guidance; does not bind state agencies that decline adoption; no public statistics yet on exam findings using the guide; Sep 16 precedes last run but was absent from 2026-09-20 edition and newly relevant beside NY DFS DIGIT operations.

How to read this edition

Source findings, measured results and limitations come from the cited publications. Patterns, operating questions, role takeaways and implementation considerations are Lighthouse Advisory interpretation, stated as questions to validate locally rather than guaranteed outcomes. Vendor and operator claims are labeled as claims. Full research method.

Independent reporting
Independent reporting with attributable sources but without a formal evaluation design.
Vendor claim
A supplier-provided assertion that has not been upgraded to independent evidence.
Public-sector association guidance
Practitioner guidance or an association-supplied case; not independent outcome evidence.