From the Emergency Services edition of October 29, 2026
Craighead County, Ark., AI non-emergency call-taker 'Lezle' answered nearly 5,000 calls in 30 days and cut dispatcher call load 56%, with early misroutes
Craighead County / Jonesboro E-911 (Arkansas) · 911 emergency communications and dispatch · Craighead County (Jonesboro), Arkansas, United States
- Publisher
- KAIT (K8 News, Jonesboro)
- Original publication
- 2026-10-29
- Source retrieved
- 2026-10-30
What happened
K8 News reports that 'Lezle', an AI agent answering Craighead County non-emergency calls for nearly two months, answered nearly 5,000 calls from Sept. 29 to Oct. 28 and cut dispatchers' call load by 56% over the past 30 days. Dispatchers say it resolves more than half of calls itself, mainly clerical matters such as records or warrants. E-911 dispatcher Terra Summers describes early glitches, including Lezle telling a caller to file a car accident report online when an officer should be sent. Errors are reported to administrators or the programmer. Trigger words such as 'emergency', 'breathing' or 'fire' transfer callers to a live dispatcher.
Why it matters
A rare U.S. follow-up with a month of operating numbers and a named failure mode for a non-emergency AI call-taker, after the archive's September 2 report that Jonesboro was only testing it.
Evidence and measured results
Local TV report quoting a dispatcher and a resident. The 56% and nearly 5,000 figures are operator-reported without method, baseline or error count; the '70 hours' quote is not explained. The accident-report misroute is described anecdotally with no count of similar errors.
Limitations and uncertainty
Single local-news follow-up; vendor not named; figures are self-reported for one 30-day window; 'more than half resolved' and '56% call load' may use different denominators. Follow-up to an archived Sept. 2, 2026 KAIT item (different URL) on the testing phase; this record adds the first operating results.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Non-emergency calls, many clerical, consume dispatcher time on a small E-911 floor.
- Stakeholders
- E-911 director
- Dispatchers
- County or city administration
- AI vendor
- Residents
- Discovery questions
- How do you count calls the AI resolves versus transfers?
- How many misroutes have dispatchers reported and how fast were they fixed?
- Which call types must never be deflected online?
- Value hypothesis
- Moving clerical calls to AI may reduce dispatcher call load substantially, as Craighead reports 56%, if misroutes are caught and fixed (interpretation).
- Potential engagement
- An independent 30-day audit of AI-resolved and transferred calls with a misroute log review.
- Unsupported claims
- Accuracy or misroute rate
- Hours or cost saved
- Caller satisfaction
- Safety on emergency calls
Pre-sales engineering
Role takeaway
- Fit
- Fits PSAPs with high clerical non-emergency traffic (records, warrants).
- Architecture and integration
- AI agent on the non-emergency line with keyword-triggered live transfer and routing to the correct office.
- Prerequisites
- Call logging with outcome codes
- Transfer routing to dispatchers and offices
- Defect reporting workflow
- Constraints
- Keyword triggers may miss indirect emergencies
- Vendor and model not named
- Single-county figures
- Security
- Define retention and vendor access for transcripts that include records and warrant questions.
- Proof of value
- Audit sample of AI-resolved calls for wrong deflections
- Containment rate with stated denominator
- Time from defect report to fix
Delivery
Role takeaway
- Work
- Operate and tune call flows through a dispatcher-reported defect loop.
- Dependencies
- Vendor programming support
- Administrator access to call-flow configuration
- Dispatcher reporting time
- Ownership
- E-911 center administration, with vendor support for model changes.
- Skills and adoption
- Dispatchers learn to spot and report AI errors; administrators learn to edit call flows.
- Governance checkpoints
- Written list of incident types the AI must always transfer
- Monthly misroute review
- Public reporting of containment method
- Acceptance criteria
- Proposed: misroute rate below an agreed threshold in audited sample
- Proposed: defects fixed within an agreed number of days
- Risks
- Incidents needing a response deflected online
- Figures reported without method
- Dependence on one vendor programmer
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Keyword-triggered transfer to a live dispatcher sits in front of the AI; corrections go through an administrator-or-programmer loop rather than a formal change process.
Governance
Who approves, reviews and stays accountable for outcomes?
The misroute shows non-emergency AI can give unsafe instructions on incidents that need a response; agencies need an incident log, review cadence and a rule for what the AI may never deflect.
Security and privacy
What data, permissions and controls need testing?
Records and warrant questions involve personal data; the source does not describe retention, vendor access or call recording terms.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Dispatchers describe relief on the floor and stay in the loop to report errors; a wary resident accepts AI only if it sticks to non-emergency calls.
Procurement
What should contracts, pricing and exit terms secure?
Buyers should require vendors to report containment with a defined denominator and to fix misroutes within a set time.
Operating model
Which teams own the service once it runs?
AI handles clerical non-emergency calls while dispatchers act as the error-reporting and escalation layer.
Publication history
- 2026-10-29Emergency Services · Issue 535 resources
Stable resource ID: kait8-craighead-county-lezle-ai-nonemergency-56pct-call-load-30-days-20261029