Lorikeet
for Halaxy
Contact us
for Halaxy
for Halaxy
Built around the questions practitioners ask between patients — calendar sync, Medicare rejections, telehealth links, SMS reminders, adding a new physio — the agent diagnoses and actions, so your support team isn't stuck explaining the same fix three times an hour.
Loaded with dummy data for a fictional practice — Bondi Allied Health, run by Sarah Chen on Halaxy Plus.
Click any prompt to copy it.
AI support that understands practice management, Medicare and HICAPS claiming, telehealth, and the way Australian allied health practitioners actually work.
Diagnoses claim rejection codes (9613, 9633, 9635) in plain English and walks practitioners through the right resubmission path — without picking item numbers.
Creates and resends Halaxy Telehealth video links to patients before their appointment, troubleshoots join failures, and keeps URLs off voice.
Looks up outstanding invoices, confirms Tyro and HICAPS gateway status, and walks staff through resends and EFTPOS reconciliation.
Adds physios, psychologists, GPs end-to-end — captures AHPRA, sends the invite, and explains the 2-business-day verification window.
Toggles SMS reminders, explains the 13c credit model, and walks practitioners through customising and sharing their public booking page.
If a practitioner discloses a patient safety concern, the agent surfaces Lifeline, Beyond Blue and 000 calmly — and stays out of clinical advice the rest of the time.
Wired up specifically for Halaxy's AU allied-health practitioner base.
Pulled the public halaxy.com articles into the knowledge base and grounded answers in your real product terminology.
Eight topic-matched workflows — calendar, billing, claims, booking page, reminders and telehealth, admin, plus an open-conversation fallback.
Ten mock tools — practitioner profile, calendar, invoices, Medicare/HICAPS claim lookup, plus write actions for telehealth links, SMS settings, and adding practitioners.
Three STEER guardrails — no clinical advice, AU crisis-line surfacing, and tight scope around practice management — plus voice rules for chunking numbers and one-question-per-turn.
From this demo to production in weeks, not months.
Replace dummy data with real practice records, the live Halaxy help articles, and the actual Medicare reason-code library. Tighten the agent on real practitioner conversations.
Practitioner + practice lookups, claim status reads, invoice and calendar inspection. The agent answers and diagnoses without touching anything in production.
Resend telehealth links, update SMS settings, add practitioners, reset patient portal access. Enable progressively once you've validated read-only behaviour.
Add voice and email. Same workflows, same brand voice, every touchpoint a practitioner reaches for — chat widget, support email, and a real Australian phone number.
Lorikeet is built for businesses handling sensitive patient data — privacy and AU data residency are non-negotiable.
Multi-region deployments. Australian practitioner and patient data stays in AU. Pick the jurisdiction that suits your privacy posture.
Phased API access — start read-only, enable write-back when you're ready. The agent only sees and actions what you've explicitly authorised.
Security docs, sub-processor list, vendor questionnaire, and DPIA available on request — we can share access with your compliance reviewer.
Practitioners get rejection codes diagnosed in seconds instead of waiting for a support reply. The same 9613 question doesn't land in your queue twenty times a week.
The agent handles the top 60-70% of practitioner questions — calendar sync, SMS setup, telehealth links, booking page tweaks — so your team focuses on complex billing and Medicare cases.
AU, NZ, IE, NL and UK practitioners all get instant answers, even when your support team is asleep. Same accuracy across time zones.
The agent stays on practice management. It won't pick an item number, comment on treatment, or give clinical advice — even when asked directly. Built for health, by design.
Deploy with the Halaxy brand and voice. The agent represents your product, not a third-party chatbot.
Handle 3x the practitioners without growing the support team. The AI grows with your practitioner base.
Happy to walk through how this works in production and answer any questions.
Talk to the team