Reignite Health: The 2025 AI Booking Implementation

Scope and Date of This Account

This article describes the 2025 Cliniko-based implementation for Reignite Health. It is a historical account of that work, not a description of the current software or hosting arrangement.

Reignite's mobile allied health setting required booking conversations to account for practitioners working across locations. Patients, family members and facility staff could have different information and authority to make a request.

The implementation work therefore focused on connecting the conversation to the booking rules and records. This article does not claim a measured increase in revenue, patient satisfaction or call-answer rate.

Booking Rules Had to Match the Service

A useful booking request needed more than a preferred time. The system had to identify the relevant location, appointment type and practitioner, then obtain availability from Cliniko.

The conversation also needed to distinguish an existing patient from a new enquiry and handle a family member calling for someone else. Identity and authority checks belong in the service design; a familiar name alone is not enough to justify disclosing patient information.

Where the required information was incomplete or the requested action could not be performed, the appropriate outcome was a request for staff follow-up rather than an invented confirmation.

Connecting Conversation and Calendar

The integration connected the booking conversation with Cliniko data. The important boundary was the receiving system's response: identifying a time and successfully creating the appointment are separate events.

A test plan for this kind of work needs to cover an ordinary booking, a changed preference, an unavailable practitioner and a slot taken before the request finishes. Retrying a request should not create a second appointment.

Clear outcomes make those tests useful. Staff should be able to distinguish a confirmed booking, a request awaiting attention and a failed action.

Escalation and Ongoing Maintenance

Administrative automation does not replace clinical judgement. Questions outside the approved scope, concerns requiring a clinician and callers asking for a person need a defined handover process.

Practice information changes. Practitioner availability, service locations and appointment rules need maintained sources, with responsibility assigned for updates. A change in the practice system can also require changes to the integration and its tests.

A successful technical check at one point in time does not establish that all later calls will be handled correctly. Operational review remains part of running the service.

What Can Be Measured

To assess an implementation like this, compare a defined period before and after launch. Record the number of attempted bookings, appointments actually created, corrections, duplicate records, failed integrations and staff handovers.

Revenue requires completed and paid services; patient satisfaction requires a documented method and sample. Neither can be inferred from an agent's availability or a successful demonstration.

The earlier version of this article included outcome percentages and satisfaction scores without supporting measurement records. Those figures have been removed. The useful account is the work involved and the evidence needed to assess its result.

Applying the Lessons to Another Practice

Begin with your own appointment rules and the systems your team uses today. Test the complete request and confirmation process before moving routine calls to a new service.

Book a 30-minute consultation to discuss your requirements. It is free for businesses with 20 or more full-time staff; otherwise AUD $200 including GST.