For the patients who
won't chat.
Plenty of people will never open a chat widget and will not ring a clinic if they can avoid it. TriageForms is the door they will use: a real form, asking only what this scan needs, with chat and voice one tap away in the same panel if they get stuck. Bookings land in the booking mode your site runs, straight into your RIS where a write integration is enabled, and anyone who gives up halfway is followed up, by an AI callback or by reception, whichever your clinic configures.
Anything we can answer for you?
Not everyone will talk to you.
Voice and chat cover the patients willing to start a conversation. A large share never will. They will not phone during work hours, they will not open a chat bubble, and if the only way to book is to talk to someone, they put it off. The referral sits in a glovebox for three weeks.
So TriageForms gives them a form, on purpose. Fields, a progress bar, a visible end. What is different is that it responds to every answer, and that the moment a patient does want to ask something, chat and voice are right there in the same panel: carrying everything they have already entered across, so nobody starts again.
What they enter becomes a booking in the mode your site runs, written straight into your RIS where a supported write integration is enabled. If they stop halfway, that is not a lost lead either, Triagents calls them back to finish it, or hands it to reception to call, whichever your clinic has configured.
Completion rate, time to complete, and the share of submissions needing no reception touch are all tracked, so this is a number you can check rather than a claim we make.
The door for
everyone else.
A form, deliberately
Not a chat wearing a disguise. Fields, a progress bar, a back button, and a visible end, because the people it is built for chose a form on purpose. It just happens to be a form that responds to every answer.
Booked the way your site books
What the patient enters becomes a booking in whichever mode your site runs: confirmed in TriageWorkflow's own booking system, written directly into your RIS where a supported write integration is enabled, or handed to reception as a ready-to-key booking request where neither is in use. Never a PDF for someone to read and retype at 8am. The mode, the system of record and any RIS synchronisation are stated in your quotation.
Nothing is abandoned
A form left half-finished is a patient who still wants a scan. Triagents can call them back and finish the booking, or raise it for reception to call, whichever your clinic configures.
Chat or call, without starting again
A question the form cannot settle is where most patients give up. Here they open chat or ask for a call from inside the form, and everything already entered goes with them. Same brain, same rules, no repeating themselves.
Shaped by your own rules
Machine, duration, contrast and funding pathway resolve from the same per-site configuration behind TriageVoice and TriageChat. Add a scanner or change a roster and the form follows, with no branching logic to rebuild.
Referral capture on upload
A photographed referral is read on submission, referrer, requested study and clinical notes lifted out, so the patient types their name and little else.
The form also watches
the page it sits on.
Embedding the form gives us a vantage point on your booking page, so we use it. A form cannot book anybody who gave up before the page finished loading, which makes your booking page our problem as much as yours.
Load time, continuously
Your booking page is measured the way a patient meets it: a mid-range phone on mobile data. Core Web Vitals are tracked over time, so the slow drift that follows a few CMS changes shows up as a trend instead of a mystery.
Where patients drop
Bounce on the booking page, and how far into the form people get before they stop. A completion rate falling in the same week the page got heavier is a story your analytics will not tell you on its own.
When it breaks, you know
If the page stops responding, or the form stops rendering on it, your team is alerted rather than finding out from a referrer on Monday. Silent booking-page outages are the expensive kind.
Alerts go wherever your team already looks. When you would rather not chase it yourself, hand the page to us: fixing booking pages is what our conversion and UI work has been for 25 years.
What clinics ask about the form.
How is this different from a chat widget?+
What happens to a half-finished form?+
Where do completed submissions go?+
Can a patient ask a question without starting again?+
Does Triagents monitor the booking page as well?+
What happens when a patient uploads a referral?+
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.