{"resourceId":"orland-park-humphrey-residents-cannot-reach-staff-20261007","versions":[{"version":"external-0a65ff8824356db16561546e8dea568a4a6ce895f0f37b4559ef34d0e301e006","resource":{"id":"orland-park-humphrey-residents-cannot-reach-staff-20261007","title":"Orland Park residents tell trustees the Humphrey AI phone and web assistant never connected them to a person","organization":"Village of Orland Park, Illinois (Board of Trustees; IT Department)","sector":"Resident-facing AI phone and chat assistant","geography":"Orland Park, Illinois, United States","publishedAt":"October 7, 2026","publicationDate":"2026-10-07","eventDate":"2026-10-05","sourceName":"The Regional News (Southwest Regional Publishing)","sourceLabel":"Local news report on a board meeting","sourceUrl":"https://southwestregionalpublishing.com/2026/10/07/residents-say-village-chatbot-wont-connect-them/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["operating-model","accessibility-workforce","knowledge-work"],"finding":"At the Oct. 5 board meeting two residents said Humphrey, the AI assistant answering the village's main number and website since late August, failed to transfer them to staff: one called four times on a weekday morning and never reached a person despite being told she would be connected; another spent about two hours and had to visit in person. One noted the information desk no longer exists. The mayor promised a human follow-up. The IT director had described Humphrey as grounded only on village-supplied content.","sledRelevance":"Escalation to a human is the control most resident assistants promise; this is a direct report of it failing on a main phone line, weeks after launch.","evidence":"Resident testimony at a public meeting reported by local press; no system data.","architectureImplications":"Interpretation: phone-channel AI needs a tested, monitored transfer path to staff during business hours; grounding on approved content does not address routing failures.","governanceImplications":"Complaints surfaced through public comment rather than monitoring; the board has no reported metric for failed transfers.","securityPrivacyImplications":"Not discussed; the grounding claim limits misinformation risk but says nothing about call data retention.","caveats":"Two residents; small sample acknowledged by the reporter; no transfer or resolution data; cause of failures unknown.","streamIds":["local-government"],"roles":{"sales":"Sales framing: Orland Park shows the reputational cost when an AI phone assistant blocks access to staff. Buyers considering phone deployments will ask how escalation is guaranteed and measured. Lead with transfer reliability, staffed fallback hours and reporting, not containment rates. Two complaints are not a failure rate, so do not cite this as proof the product fails; cite it as the scenario a contract and monitoring plan must cover. Avoid pitching staff reductions alongside a front-line AI assistant.","engineering":"Engineering framing: The issue is call routing, not answer accuracy. Engineers should check how the assistant hands calls to queues, what happens when no agent is available, and whether repeated failed transfers are logged. Prerequisites are integration with the telephony system and staffed queues. Constraints include business-hours coverage and caller identification. A proof of value should place scripted test calls requesting a person at different times and confirm each reaches a human or a callback request within a set time.","delivery":"Delivery framing: For an existing deployment, delivery work is a transfer audit: review call logs for requests for a person, measure completed transfers, and fix routing. Ownership sits with the IT director and the department queues receiving calls. Interpretation: publish a simple monthly report to the board on transfer success and complaints so issues surface through monitoring rather than public comment. Re-check whether removing in-person information points is appropriate while the assistant is still being tuned."},"roleDetails":{"sales":{"customerProblem":"Residents report the AI phone assistant does not connect them to staff, damaging trust in the new service.","stakeholders":["Mayor and Board of Trustees","Village Manager","IT Director","Department heads receiving transfers","Residents"],"discoveryQuestions":["What share of calls ask for a person, and how many reach one?","What happens when no staff member is available?","How are complaints tracked?","Was the information desk removal tied to the assistant?"],"valueHypothesis":"Reliable escalation could preserve the convenience benefits while restoring trust; no measured data exists yet.","potentialEngagement":"A transfer-reliability audit with scripted test calls and log review, reported to the board.","unsupportedClaims":["That Humphrey fails broadly","Any containment or savings figure","That grounding prevents all service failures"]},"engineering":{"fit":"Relevant to any AI assistant on a main phone line with handoff to staff queues.","architectureIntegration":"AI voice and chat assistant integrated with village telephony and queues; grounded on village-supplied content.","prerequisites":["Telephony integration","Staffed queues during business hours","Call logging of transfer attempts","Callback mechanism"],"constraints":["Business-hours staffing","Limited in-person alternatives","Vendor routing configuration"],"security":"Confirm call recordings and transcripts follow retention rules; not addressed in the source.","proofOfValue":["Scripted test calls requesting a person at five times of day","Log review of failed transfers over one month","Callback completion rate check"]},"delivery":{"work":"Audit and fix human escalation for the village AI assistant, and report results.","dependencies":["Vendor log access","Department queue owners","Board reporting cycle"],"ownership":"IT Director with the Village Manager's office.","skillsAdoption":"Staff guidance on receiving transfers and callbacks; resident communication on how to reach a person.","governanceCheckpoints":["Transfer audit results","Board update","Decision on restoring an in-person information point"],"acceptanceCriteria":["Share of 'speak to a person' requests reaching staff or a scheduled callback reported monthly","Complaints about failed transfers decline after fixes","Test calls pass at all staffed hours"],"risks":["Erosion of resident trust","Vulnerable residents unable to reach help","Problems surfacing only through public comment"]}},"retrievedAt":"2026-10-07T22:12:58-05:00","enrichedAt":"2026-10-07T22:21:14.164-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Removing the information desk while the phone assistant fails to escalate leaves residents who need a person, including older callers, with fewer options.","procurementImplications":"Contracts for AI phone assistants should include transfer-success service levels and reporting.","operatingModelImplications":"The village combined AI phone triage with fewer in-person points of contact; staff routing behind the assistant is part of the system.","sourceVerification":{"openedUrl":"https://southwestregionalpublishing.com/2026/10/07/residents-say-village-chatbot-wont-connect-them/","referenceExcerpt":"It kept saying I would be connected to a person, and this was like 11 a.m. on a weekday.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}