From the Public Safety edition of October 5, 2026
Thames Valley and Hampshire police AI agent Bobbi automates about 75% of non-emergency contacts while escalating vulnerability cases to humans
Thames Valley Police and Hampshire & Isle of Wight Constabulary (reported by CX Today; vendor case study by Salesforce) · Police public contact / non-emergency services · Thames Valley and Hampshire, England, United Kingdom
- Publisher
- CX Today
- Original publication
- October 5, 2026
- Source retrieved
- 2026-10-06
What happened
CX Today reported on Oct. 5, 2026, from a Dreamforce 2026 interview, that Thames Valley Police and Hampshire & Isle of Wight Constabulary's public-facing AI agent Bobbi has been live since the previous November, with just over six months of data at interview time. The forces said about 75–76% of contacts are subject to automation and the remaining 25% are escalated to operators on a 24/7 digital desk. Topic-tagged knowledge articles trigger different instructions and guardrails (for example a supportive tone for domestic abuse and simpler language when a child appears to be writing). The agent was stood up in four days and taken live within ten weeks; the team tested about 3,000 conversations before deployment and continues to monitor and amend it, treating it 'like an employee' with clear accountability. The forces report fewer contact-centre contacts, reduced waits and higher satisfaction, and cite a cuckooing case that led to four arrests. Salesforce's vendor case study claims 200+ daily conversations, 75% resolved independently, a 97% lower cost per interaction, a 4.6 CSAT score, and about two potential violence-against-women-and-girls cases routed daily. Next steps under consideration include having the agent take actions on users' behalf and an internal staff agent.
Why it matters
Policing public-contact lane: a generative AI agent handling non-emergency police enquiries with explicit human escalation for vulnerability. Cross-tagged emergency-services because it diverts 101 demand from police call handlers, though it is not a 999 dispatch tool.
Evidence and measured results
Trade-press interview with force digital leaders (operator claims) plus a visibly attributed Salesforce customer story (vendor claims). No independent evaluation, missed-vulnerability error rate or escalation accuracy is published.
Limitations and uncertainty
Figures are operator and vendor claims without independent verification; CX Today cites 1,900 knowledge-base articles while Salesforce cites 91, an unexplained discrepancy; no false-negative rate for missed vulnerable contacts; ROI and staff-hours figures are projections; UK context limits direct U.S. transferability.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Police non-emergency lines face long waits and high volumes, while vulnerable callers must still reach a human quickly.
- Stakeholders
- Force contact-centre leadership
- Digital and data leads
- Public protection and safeguarding units
- Victim services
- Police and crime commissioner
- Data protection officer
- Discovery questions
- What share of non-emergency contacts are status requests or FAQs today?
- How is vulnerability defined and labeled for testing?
- Who owns and approves the knowledge content?
- Is a 24/7 human desk available for escalations?
- Value hypothesis
- Bounded: an agent may absorb routine enquiries and shorten waits if escalation accuracy is demonstrated on local data.
- Potential engagement
- Non-emergency AI agent pilot with a labeled escalation test set, monitoring dashboard and governance runbook.
- Unsupported claims
- 97% cost reduction or 900% ROI as expected local results
- Reliable detection of all vulnerable contacts
- Transferability to U.S. non-emergency lines without testing
- Crime-reduction effects
Pre-sales engineering
Role takeaway
- Fit
- Agencies with web or chat non-emergency channels and a curated knowledge base that can staff a live escalation desk.
- Architecture and integration
- Public chat to retrieval over approved articles to topic-triggered guardrails to case creation and live operator handoff with transcript, risk flags and summary.
- Prerequisites
- Curated and tagged knowledge articles
- Labeled vulnerability test conversations
- 24/7 operator desk
- Conversation and escalation logging
- Constraints
- Not an emergency (999/911) channel
- UK data protection rules on sensitive disclosures
- Knowledge base must be maintained
- Planned action-taking needs new authorization
- Security
- Minimize personal data captured, protect transcripts containing abuse disclosures, and log every automated answer and escalation decision.
- Proof of value
- Escalation recall on labeled vulnerable conversations
- Wait-time change against baseline
- Share of automated answers rated correct in quality review
- Complaint and re-contact rates
Delivery
Role takeaway
- Work
- Stand up content governance, a labeled test set, monitoring reports and a staffed escalation desk before launch.
- Dependencies
- Knowledge content owners
- Contact-centre staffing
- Vendor platform configuration
- Safeguarding team input on topics
- Ownership
- Force contact management and digital leadership, with safeguarding leads owning vulnerability rules.
- Skills and adoption
- Operators need training on reading handoff summaries and risk flags; content owners need skills in writing agent-ready articles.
- Governance checkpoints
- Pre-launch conversation test sign-off
- Monthly quality review
- Safeguarding review of missed escalations
- Approval before any action-taking capability
- Acceptance criteria
- Proposed: escalation recall above an agreed threshold on labeled tests
- Proposed: published monthly automation and escalation rates
- Proposed: every knowledge article reviewed within a set period
- Proposed: measured wait-time reduction versus baseline
- Risks
- Missed vulnerability in automated chats
- Over-reliance on vendor metrics
- Knowledge drift
- Scope creep into action-taking agents
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?
Retrieval-grounded agent over force-approved knowledge articles, with topic-triggered instructions, case creation and live handoff passing transcript, risk indicators and summary to operators.
Governance
Who approves, reviews and stays accountable for outcomes?
Accountability is framed as ownership of the agent's knowledge and behaviour, with pre-launch testing and ongoing monitoring; planned moves toward agents taking actions will need new authorization and audit controls.
Security and privacy
What data, permissions and controls need testing?
The handoff passes contact details, IP address and transcripts to operators; vulnerability detection on chat text raises retention and use questions for sensitive disclosures that the sources do not address.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Offers a lower-barrier text channel (including adaptive reading level) and shifts operators toward higher-harm conversations; workforce effects beyond reduced contacts are not measured.
Procurement
What should contracts, pricing and exit terms secure?
Agencies should require vendors to report escalation accuracy and allow agency control of knowledge content, rather than buying on vendor ROI claims.
Operating model
Which teams own the service once it runs?
Contact handling becomes agent-first with human escalation, and the agent is managed like staff through monitoring, coaching and content updates.
Publication history
- 2026-10-05Public Safety · Issue 295 resources
Stable resource ID: tvp-hiowc-bobbi-ai-agent-public-contact-20261005