{"resourceId":"hernando-polimorphic-front-door-contract-20260915","versions":[{"version":"external-2266089880e912e072a34f08662011c1a97a0e98287d1e616e770bd8844e28ad","resource":{"id":"hernando-polimorphic-front-door-contract-20260915","title":"Hernando approves $45,000/year Polimorphic Ask Hernando resident front door","organization":"City of Hernando","sector":"Small-city public works and resident contact center","geography":"Hernando, Mississippi, United States","publishedAt":"September 16, 2026 DeSoto Times-Tribune report of Sept. 15 board action","publicationDate":"2026-09-16","eventDate":"2026-09-15","sourceName":"DeSoto Times-Tribune","sourceLabel":"Independent local reporting of Board of Aldermen contract approval","sourceUrl":"https://www.desototimes.com/news/hernando-board-approves-contract-for-ai-customer-service-system/article_2e4c1cf3-b936-41e8-9c10-5afb9fa2671d.html","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["operating-model","governance-procurement","knowledge-work","data-security"],"finding":"On Sept. 15, 2026 the Hernando Board of Aldermen unanimously approved a Polimorphic contract for “Ask Hernando’s Front Door,” a phased 24/7 chatbot/phone/text/email front door for citizen questions, department routing, and public-works work orders, reported at about $45,000 per year. Officials cite after-hours access, work-order tracking (including Nexbillpay integration ambitions), and reducing non-emergency police-line overload. Vendor says answers come from public content; cybersecurity discussion noted need to block tricks that could reveal who reported code violations. No public rollout date and no measured outcomes yet.","sledRelevance":"Fresh small-city procurement signal: implementation capacity and accountability questions appear at award time—phasing, public-data grounding, integration boundaries—before any benefit metrics exist.","evidence":"DeSoto Times-Tribune (Sept. 16 covering Sept. 15 meeting): unanimous approval; ~$45k/year; chatbot + phone/text/email; Public Works director Stephen Hodges; vendor Ben Busching; phased approach; public info grounding; code-violation software integration caution; no launch timeline; funded partly via other project savings per Hodges.","architectureImplications":"Interpretation: Start with website chatbot trained on public content before voice; treat work-order and billing integrations as higher-risk boundaries requiring explicit allow/deny rules.","governanceImplications":"Interpretation: Board approval without a launch date should still set acceptance tests, data boundaries, and weekly success-manager checkpoints before go-live.","securityPrivacyImplications":"Interpretation: Explicitly block prompts that could expose complainant identity or non-public code-case data when integrating violation systems; segregate billing authentication from open Q&A.","caveats":"Pre-launch procurement reporting with substantial vendor statements; $45k savings narrative is city assertion; no accuracy, containment, or time-to-resolution metrics yet.","streamIds":["local-government"],"roles":{"sales":"Small cities drowning in after-hours calls and missed work orders look for an AI front door that residents will actually use. This evidence supports a phased contact-center modernization discussion with clear public-data scope and integration deny-lists—not a claim that $45,000 buys proven outcomes. Bound the engagement to pilot acceptance criteria before voice cutover. Do not promise police-line relief or faster work orders without baselines the city has not published.","engineering":"Fit is a multi-channel resident front door grounded in public web and code content, with optional work-order and billing integrations behind strict boundaries. Prerequisites include a content corpus, ticket taxonomy, and authentication boundaries for payments. Constraints: phased launch, no public timeline yet, and small staff capacity. Security must prevent leakage from code-complaint systems and keep public Q&A on public sources only, matching the board discussion.","delivery":"Train the chatbot on public content first, run joint testing with Public Works and the vendor success manager, then consider after-hours voice. Ownership sits with the Public Works director; the Board owns funding continuation. Define intents, deny-lists for code-complaint data, tracking-link UX, and human fallback before soft launch. Acceptance criteria must include passed leakage tests and a dated phase plan. Risks include launching voice before answers stabilize, overselling savings, and privacy failures on integrated systems."},"roleDetails":{"sales":{"customerProblem":"Residents cannot reach the right department after hours; work orders and billing questions fall through, overloading non-emergency lines.","stakeholders":["Board of Aldermen","Public Works director","Police dispatch (non-emergency load)","Residents","Vendor success manager"],"discoveryQuestions":["What is the go-live date and phase order?","Which systems integrate in phase 1 vs later?","How are code-complaint identities protected?","What baselines exist for call abandonment and work-order lag?"],"valueHypothesis":"A phased public-info chatbot plus work-order tracking can improve reachability if boundaries and tests precede voice automation—price alone does not prove value.","potentialEngagement":"Pilot readiness assessment: intent catalog, deny-list tests, and acceptance criteria before public launch, sized to a small-city staff capacity.","unsupportedClaims":["Guaranteed $45k net savings","Immediate 24/7 resolution of all requests","Police non-emergency relief without measurement","Public-data grounding eliminates privacy risk"]},"engineering":{"fit":"Phased AI front door (web chat, then phone/text/email) for routing and public Q&A with optional work-order/billing integrations.","architectureIntegration":"Public content retrieval → ticket/work-order system; isolate Nexbillpay and code-violation systems behind authenticated, deny-listed interfaces.","prerequisites":["Public content crawl/upload","Work-order taxonomy","Success-manager cadence","Security deny-list for sensitive integrations"],"constraints":["No public rollout date yet","Small staff capacity","Vendor-led training risk","Board already approved spend pre-metrics"],"security":"Block prompts that reveal complainants or non-public case data; harden billing paths; keep public Q&A on public sources only.","proofOfValue":["Intent containment tests","Deny-list abuse tests on code data","After-hours deflection sample","Work-order time-to-first-response baseline vs pilot"]},"delivery":{"work":"Build content corpus, configure channels, test routing, integrate work orders carefully, train staff, then soft-launch.","dependencies":["Polimorphic configuration","Nexbillpay/work-order interfaces","Public Works staff testers","Dispatch coordination"],"ownership":"Public Works director owns city-side outcomes; vendor provides success management; Board owns funding continuation.","skillsAdoption":"Teach staff to monitor answers, handle escalations, and update scripts/documents the bot reads.","governanceCheckpoints":["Pre-voice accuracy gate","Privacy deny-list sign-off","Soft-launch review","90-day metrics check"],"acceptanceCriteria":["Documented phase plan","Public-only Q&A verified","Code-complaint leakage tests pass","Human fallback published"],"risks":["Launch without timeline accountability","Privacy breach via integrated systems","Savings narrative without baselines","Resident distrust if routing fails"]}},"retrievedAt":"2026-09-19T03:05:16Z","enrichedAt":"2026-09-19T03:18:00Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: After-hours channels can help residents who cannot call 8–5, but small-city staff must still absorb escalations and content upkeep.","procurementImplications":"Interpretation: $45k/year deals should attach phase gates, privacy deny-list tests, and outcome baselines before renewing or expanding to voice.","operatingModelImplications":"Interpretation: A single front door only works if departments accept tickets and keep public content current; otherwise automation amplifies dead ends.","sourceVerification":{"openedUrl":"https://www.desototimes.com/news/hernando-board-approves-contract-for-ai-customer-service-system/article_2e4c1cf3-b936-41e8-9c10-5afb9fa2671d.html","referenceExcerpt":"Integrating Polimorphic into Hernando’s Public Works and general website is expected to cost $45,000 each year.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}