{"resourceId":"south-carolina-bradley-resident-ai-assistant-20260630","versions":[{"version":"external-68aea0f67d67b93b352ab291e8c4aa9a79e8ddefe2471902372fe3ba5d4123ef","resource":{"id":"south-carolina-bradley-resident-ai-assistant-20260630","title":"South Carolina Bradley Resident AI Assistant reports 82.2% first-contact resolution on verified .gov answers","organization":"South Carolina Department of Administration / Tyler Technologies","sector":"State government — citizen digital services / shared information access","geography":"South Carolina, United States","publishedAt":"2026-06-30","publicationDate":"2026-06-30","eventDate":"2026-06-30","sourceName":"Tyler Technologies investor news — South Carolina Expands Access to Government Services with Tyler Technologies’ Resident AI Assistant","sourceLabel":"Vendor press release with state CIO quotation","sourceUrl":"https://investors.tylertech.com/news/news-details/2026/South-Carolina-Expands-Access-to-Government-Services-with-Tyler-Technologies-Resident-AI-Assistant/default.aspx","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["accessibility-workforce","operating-model","knowledge-work","governance-procurement"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Central conversational gateway retrieving exclusively from verified state web content, with multilingual front door and analytics on unmet intents—architecture favors RAG-over-.gov rather than transactional case systems.","governanceImplications":"Statewide CIO sponsorship and verified-.gov grounding reduce hallucination surface versus open-web bots; still depends on content owners keeping agency pages accurate and on vendor transparency claims.","securityPrivacyImplications":"Public-information scope lowers PII exposure versus authenticated case bots, but logging of resident questions and analytics retention still need privacy review; vendor-hosted assistant implies third-party data-processing terms.","caveats":"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.","streamIds":["state-government"],"roles":{"sales":"Sales framing: South Carolina published scarce statewide chatbot operating metrics—82.2% first-contact resolution, 38,000+ questions, 54 languages—on a Tyler Resident AI Assistant grounded in verified .gov content. Engage state CIO/digital-service and DMV/revenue/court content owners comparing AskCA or Nebraska Navigator paths. Offer a bounded content-readiness and FCR baseline assessment—not a promise to hit 82.2%. Unsupported: that every state’s bot will match SC volumes or that metrics were independently audited.","engineering":"Engineering framing: Fit is a public RAG chatbot over curated .gov corpora with multilingual routing and intent analytics—not eligibility adjudication. Integrate content crawls/sitemaps, allowlisted domains, conversation logging, and weekend/after-hours capacity. Prerequisites: authoritative agency page inventory and change-management for content owners. Constraints: vendor stack (Tyler); public-info only; FCR methodology opaque; SC-specific information architecture.","delivery":"Delivery framing: Work is content curation, bot launch on primary portals, analytics review loops with agencies, and multilingual QA. Ownership typically spans DoA/CIO for the gateway and agencies for source pages. Acceptance should include published FCR/containment definitions, domain allowlist evidence, and language-coverage tests—not press-release counts alone. Risks: stale .gov pages; over-trusting FCR; expanding from information to transactional advice without workflow integration."},"roleDetails":{"sales":{"customerProblem":"States want statewide resident chatbots but lack peer FCR/engagement metrics beyond a few announcements.","stakeholders":["State CIO / digital services","DMV and revenue content owners","Court/public-information leads","Procurement for citizen-experience platforms"],"discoveryQuestions":["What is your definition of first-contact resolution for an information bot?","Which .gov domains are allowlisted as ground truth?","What share of interactions occur after hours or in non-English languages?","Who owns fixing pages the bot surfaces as weak?"],"valueHypothesis":"A 4–6 week content-and-telemetry readiness review can establish FCR baselines before statewide navigator expansion.","potentialEngagement":"Bounded discovery: map allowlisted corpora, define FCR/containment KPIs, and pilot analytics with two high-volume agencies.","unsupportedClaims":["Guaranteed 82.2% FCR replication","Independent audit of Tyler’s published counts","That information bots reduce in-person visits in every program"]},"engineering":{"fit":"Public multilingual RAG assistant over verified state websites with intent analytics—not case-management automation.","architectureIntegration":"Crawl/allowlist .gov sources; serve widget on enterprise portal; log intents; escalate unresolved queries to human channels.","prerequisites":["Authoritative domain allowlist","Content owners for DMV/tax/courts","Telemetry for FCR and language mix"],"constraints":["Vendor-hosted Tyler stack","Public-information scope only","Opaque FCR methodology in the release"],"security":"Minimize PII in prompts/logs; review vendor data-retention and subprocessors for conversation transcripts.","proofOfValue":["Agreed FCR definition with sample audits","Language coverage test pack","Intent analytics driving content fixes"]},"delivery":{"work":"Stand up allowlisted corpus, launch portal widget, train content owners, and run multilingual QA with KPI dashboards.","dependencies":["Portal/CMS teams","Agency content stewards","Tyler (or equivalent) implementation","Privacy/legal review of logs"],"ownership":"CIO/DoA for platform; agencies for source accuracy; vendor for model/runtime SLAs.","skillsAdoption":"Content stewards need bot-intent literacy; service desks need escalation playbooks when FCR fails.","governanceCheckpoints":["Allowlist change control","Monthly FCR/language KPI review","Privacy review of transcript retention"],"acceptanceCriteria":["Documented FCR definition and audit sample","Published allowlist of source domains","After-hours and multilingual test evidence"],"risks":["Stale or conflicting .gov pages","Metric inflation without definition","Scope creep into authenticated transactions"]}},"retrievedAt":"2026-09-21T22:11:42-05:00","enrichedAt":"2026-09-21T22:11:42-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"54-language support and after-hours/weekend availability can improve access for non-English and off-shift residents; does not by itself prove WCAG/accessibility conformance of the widget.","procurementImplications":"Illustrates turnkey Resident AI Assistant procurement with statewide expansion after agency pilot patterns (parallel to Nebraska); buyers should require FCR definitions, allowlist controls, and analytics deliverables in contracts.","operatingModelImplications":"Centralizes resident information discovery while leaving program transactions with agencies—shifts some Tier-0 load but creates ongoing content-stewardship operating costs.","sourceVerification":{"openedUrl":"https://investors.tylertech.com/news/news-details/2026/South-Carolina-Expands-Access-to-Government-Services-with-Tyler-Technologies-Resident-AI-Assistant/default.aspx","referenceExcerpt":"An 82.2% first-contact resolution rate, with most inquiries answered in one exchange","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}