Many agents.
One patient operations layer.
Many specialised AI agents, the phone, the chat, the form, the rules and follow-up, and the reporting, sharing one administrative triage brain. Built for radiology networks, configurable per site, hosted in the country where you operate.
Good triage isn't one decision.
It's many.
The way a well-run clinic does reception is by separating the work. One person scopes what the caller actually needs. Another runs the booking. A third validates that nothing important was missed. Triagents was built the same way.
TriageAds attracts the demand, and measures it on the scans it produces rather than the clicks it buys. TriageVoice, TriageChat and TriageForms capture it: three front doors, the phone, the chat and the form, for patients who will only use one of them. TriageWorkflow progresses it, applying each site's rules, giving operators their working views, and then running the outbound work nobody has time for. TriageInsights measures all of it for the network's executives, and what it measures decides what gets attracted next.
They share the same triage brain. None of them are bolted-on. The five core products, Voice, Chat, Forms, Workflow and Insights, are offered together: you don't pick which to deploy, you configure how each behaves for your sites. TriageAds is a separate service with separate fees, quoted on its own. Integrations are a capability of the layer rather than a seventh product; the scope is set out below.
- Attract
- Capture
- Triage
- Book
- Follow up
- Measure
- Optimise
What each one does.
TriageAds
Measures patient demand on what it produces: bookings and attended scans, not clicks, and recommends where budget should move to fill idle capacity. A separate service, quoted separately.
- Google, Microsoft and Meta attributed
- Cost per completed scan, per campaign
- Budget recommendations, applied only with your authorisation
TriageVoice
Answers every inbound call within two rings, day or night. Urgent vocabulary hands to a person in about a second.
- 24/7 answering, any call volume
- Web voice on mobile and desktop
- SMS confirmation on booking
TriageChat
A widget on your site that books, cancels and reschedules on its own. No app, no login.
- Books and reschedules unassisted
- Captures after-hours enquiries
- Confirmations by SMS and email
TriageForms
Structured intake for patients who will not call or chat, booked in whichever booking mode your site runs.
- Jump to chat or voice mid-form
- Unfinished forms: AI callback or reception follow-up, as configured
- Monitors the page it sits on
TriageWorkflow
Applies each centre's booking logic, roster rules and integrations, gives operators their working views, then runs the follow-up nobody has time for: no-shows, unbooked referrals and the waitlist.
- Per-centre booking and routing
- Operational views for the team running the desk
- No-shows rebooked, cancelled slots backfilled
TriageInsights
Executive reporting across every centre, with drill-down into any single site. Where TriageWorkflow shows operators the work in front of them, TriageInsights shows the network what it adds up to.
- Rollup across 1–500+ centres
- Modality utilisation and no-shows
- Exportable, board-ready reporting
Many agents.
One backbone.
The agents speak different languages, phone audio, text, dashboard, but they share everything underneath. Change a clinic's escalation rule once and Voice, Chat, Forms and Workflow all honour it the same moment.
Shared triage brain
Every agent consults the same radiology rule engine. A patient who starts in the form and switches to a phone call carries their context across.
One per-clinic config
Hours, services, escalation rules, knowledge base, set once in TriageWorkflow and inherited by every agent. Change once, applied everywhere.
One audit log
Every conversation across every channel logged in one place, with full transcript, intent, and outcome. Exportable for management, auditors, and compliance.
One data residency
Hosted in the country where the clinic operates. Australian clinics → sovereign Australian infrastructure. US clinics → US-based. UK clinics → UK-based. The platform does not move patient data out of that country.
A capability,
not a seventh product.
Your RIS remains the system of record. Triagents keeps the work around it moving, and the connector and implementation work included in your deployment is written into the quotation. Standard connectors and bespoke integration work are different things, and support for a given RIS version is confirmed during scoping rather than assumed.
| Scope | Systems | What that means for you |
|---|---|---|
| Standard connector | Best Practice, Medical Director, Genie | Practice management systems. Enabled per site in the quotation. |
| Standard connector | Major RIS platforms | Vendor API, HL7 messaging or FHIR eRequesting, depending on what the RIS exposes. Support depends on the version and write path at your site and is confirmed during scoping. |
| Standard connector | CRM by webhook (HubSpot, Salesforce, Pipedrive) | Outcomes and enquiry context passed to the CRM you already run. |
| Bespoke integration | Anything else | Scoped by the implementation team against your own systems and itemised in the quotation before you commit. |
Three ways a booking lands.
Every agent at a site books the same way. Your quotation states which mode you run, which system is the system of record, and whether any synchronisation with the RIS is included.
TriageWorkflow's own booking system
Appointments are confirmed in Triagents. TriageWorkflow is the system of record for the booking unless RIS synchronisation is included in the quotation; native bookings do not synchronise with a RIS automatically.
Direct into your RIS
Where a supported write integration is enabled for your RIS, the agent reads availability and writes the confirmed booking back. Your RIS remains the system of record.
Booking request for staff
Where neither confirmed-booking path is in use, the agent finishes the conversation and hands reception a ready-to-key booking request with the referral attached. It is a task to complete, not a confirmed booking.
A platform that grows
with the clinics that use it.
Triagents isn't a fixed product. The radiology rule engine, the escalation logic, the dashboards, the integrations: every layer is built to be extended. New capabilities ship continuously, driven directly by what our customers ask for in their weekly reviews.
If you run a practice and there's a workflow we don't yet handle, that conversation is how the next release gets scoped. Customers shape the roadmap: not the other way around.
From the blog
What we are learning, written down.
- What can AI agents actually do in radiology?Not AI reading scans. What an AI agent actually does across reception, booking, referrals, capacity and follow-up, and what it must never touch.
- We called 100 radiology practices after hours. Here is what answered.Original research: the same 100 radiology practices, rung on Sunday evening. Not one reached a person, and eleven were answered by an AI agent.
- We called 100 radiology practices. Here is what we found.Original research: we rang 100 Australian radiology practices and timed every call. Eight reached a person straight away; the median wait was 90 seconds.
Book a radiology network assessment.
We'll map it to your network.
30 minutes with a solutions engineer. We model your call volume, centre count, and integrations, then show the AI agents running on your own scenarios, and answer everything compliance- and security-related upfront.