Natera says its AI agents cut lab support response time by about 130 times

Natera says its SWARM AI system now answers laboratory equipment support tickets about 130 times faster, giving engineers diagnostic reports within minutes. The system combines an autonomous agent with an interactive assistant, aiming to preserve equipment expertise and keep engineers involved in the decisions that matter.

AWS AI Watch analysis

What happened

In a case study published by AWS, Natera describes building SWARM on Amazon Bedrock AgentCore to help troubleshoot lab instruments. AWS says the system covers 96.2% of support tickets and reduced average first response time from 17.4 hours to minutes. Those are figures reported by Natera and AWS, not an independent performance evaluation.

SWARM has two parts: one agent prepares a diagnostic report before an engineer opens a ticket; another lets engineers ask follow-up questions, upload images and explore alternatives. The system draws on equipment manuals, historical tickets and operational data. Its skill library contains 33 separately testable skills, including 24 for specific instrument families.

Why it matters

Laboratory downtime can delay sample processing and patient reporting. Natera says its support team handled more than 65 tickets a day across three Jira queues, while relying on specialised knowledge that could leave when experienced staff departed. The useful detail here is not simply that an agent was added: the system is designed to turn that knowledge into searchable, repeatable troubleshooting support.

The case study also describes controls for the clinical setting, including audit logging, least-privilege access and a design that keeps patient-identifiable information out of the vector index and language model. Natera says engineers remain responsible for reviewing the diagnostic reports. Faster first responses are useful; they are not the same thing as proven diagnostic accuracy or resolved equipment faults.

Our read

This is a concrete example of AI supporting a specialised operational workflow rather than being handed the keys to the lab. The practical lesson is to treat knowledge quality and evaluation as core engineering work: Natera says adding missing equipment manuals raised accuracy from 71% to 75% without changing the model. That is a better reminder than the usual temptation to blame every disappointing answer on the model.

What to watch

• Whether Natera publishes further detail on how ticket coverage and diagnostic accuracy are measured.
• How often engineers correct or override SWARM’s reports.
• Whether the approach proves useful across more equipment families and laboratory workflows.

Discussion spark: For AI-generated troubleshooting in a clinical lab, should engineers review every report or focus their attention on cases the system flags as uncertain?

not affiliated with or endorsed by Amazon Web Services (AWS)