From the Emergency Services edition of October 5, 2026
North East Ambulance Service opens £200,000 market engagement on an AI overlay for its existing Avaya Elite telephony platform
North East Ambulance Service NHS Foundation Trust (UK) · NHS ambulance service / emergency call handling procurement · United Kingdom (North East England)
- Publisher
- Stotles (listing of Find a Tender notice 2026/S 000-091997)
- Original publication
- 2026-09-29
- Source retrieved
- 2026-10-06
- Event date
- 2026-09-29
What happened
North East Ambulance Service published a preliminary market engagement notice on Sept 29, 2026 to test feasibility, capability, assurance needs, delivery complexity, indicative cost and market appetite for an AI-enabled overlay to its existing Avaya Elite telephony. It is valued at about £200,000 with responses due Oct 30, 2026. NEAS says the work will shape requirements for a future full telephony replacement aligned with emerging national standards, and that an options appraisal, business case, pilot or procurement may follow, but none is guaranteed.
Why it matters
International signal that ambulance call centers are approaching AI as an overlay on legacy telephony, with assurance and feasibility tested before buying; transferable to U.S. PSAPs on aging call-handling equipment.
Evidence and measured results
Official procurement notice as listed by an aggregator (wording cross-checked against the Find a Tender notice). States intent and scope only; no AI functions, vendors or results.
Limitations and uncertainty
Pre-tender engagement only; scope of the AI functions not described; UK NHS structures and standards differ from U.S. PSAPs; aggregator listing of an official notice.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Ambulance control room runs on legacy telephony and wants AI capability without an immediate full replacement.
- Stakeholders
- Ambulance service CIO/digital director
- Emergency operations centre leadership
- Clinical safety officer
- Procurement
- Discovery questions
- Which call-handling problems should the overlay solve?
- What assurance evidence will you require?
- How will it carry into the replacement platform?
- Value hypothesis
- A scoped AI overlay may add capability on legacy telephony if assurance and failover are proven.
- Potential engagement
- Market-sounding support and assurance requirements for AI on existing call-handling telephony.
- Unsupported claims
- Any performance benefit
- Selected functions or vendor
- Commitment to procure
Pre-sales engineering
Role takeaway
- Fit
- AI capability layered on legacy contact-center telephony in an emergency call center.
- Architecture and integration
- Overlay on Avaya Elite; requirements inform later replacement aligned with national standards.
- Prerequisites
- Telephony interface inventory
- Clinical safety case approach
- Failover design
- Constraints
- Pre-tender only
- Functions undefined
- UK-specific standards
- Security
- AI layer must meet NHS data protection and clinical safety requirements for call audio.
- Proof of value
- Failover test with AI layer down
- Integration without call-handling latency
- Supplier assurance evidence
Delivery
Role takeaway
- Work
- Gather supplier evidence, define assurance needs, produce options appraisal.
- Dependencies
- Telephony vendor
- Suppliers
- Clinical safety team
- Ownership
- NEAS digital and procurement with emergency operations centre leadership.
- Skills and adoption
- Control room staff consulted on functions and workflow before any pilot.
- Governance checkpoints
- Engagement close Oct 30, 2026
- Options appraisal
- Business case decision
- Acceptance criteria
- Assurance requirements documented before tender
- Failover defined for any pilot
- Risks
- Overlay locks in legacy constraints
- Undefined scope
- Assurance underestimated
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?
Overlay on an existing Avaya Elite platform rather than replacement; requirements to inform a later full telephony replacement.
Governance
Who approves, reviews and stays accountable for outcomes?
Explicitly tests assurance needs and delivery complexity before committing, a sound staged approach for safety-critical call handling.
Security and privacy
What data, permissions and controls need testing?
Not specified; any AI overlay on 999 telephony will touch call audio and patient information and will need NHS data protection and clinical safety assurance.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed in the notice; call handler roles and caller experience will depend on what functions the overlay performs.
Procurement
What should contracts, pricing and exit terms secure?
Market sounding before tender, open to SMEs and VCSEs, with a staged path from evidence to options appraisal; a model for agencies unsure what AI on legacy telephony can do.
Operating model
Which teams own the service once it runs?
AI added at the telephony layer of the ambulance control room, ahead of platform replacement.
Publication history
- 2026-10-05Emergency Services · Issue 305 resources
Stable resource ID: neas-ai-telephony-overlay-market-engagement-20260929