Routine bookings handled
Find a slot, hold it, confirm. AI takes care of the calendar work and the confirmation message.
OrcaLinq books appointments, handles rescheduling, and refuses clinical advice — routing those questions to your team with a Wake audit trail.
AI is excellent at the high-volume routine work clinics handle every day — booking, rescheduling, location, hours, parking, what-to-bring. The platform is engineered to refuse clinical questions and hand them to a clinician.
Find a slot, hold it, confirm. AI takes care of the calendar work and the confirmation message.
Symptom, diagnosis, medication, or treatment topics are routed to a clinician or front-desk endpoint with a policy note. Always.
Structured intake collected through chat with explicit consent. Wake audit trail captures what was asked and answered.
Booking on the website, reminder on WhatsApp, follow-up via email — same conversation thread, no lost context.
A common pattern: a patient mixes a routine request with a clinical one. The AI handles what it should, escalates what it shouldn't.
Patient (web widget): "Hi, can I book an appointment with Dr Patel for next week?"
AI: "Of course. Dr Patel's next openings are Tuesday 10:00, Wednesday 14:30, or Thursday 16:00. Which works for you?"
Patient: "Tuesday 10. Also I've been getting headaches a lot, what should I do?"
AI: "Booking Tuesday 10:00 with Dr Patel — confirmed, you'll get a confirmation by email and WhatsApp. For the headaches, I'm not able to give clinical advice, but I can let our front desk know so a nurse can call you back today, or you can wait to discuss with Dr Patel on Tuesday. Which would you prefer?"
Patient: "Call me back today."
AI: "Got it. Forwarding to our front desk now — they'll call within the next two hours. If anything feels urgent before then, please use the emergency contact in your area."
Front desk (back-office, 12:14 PM): Wake entry shows the booking, the clinical-question handoff, the agreed callback window, and the patient's phone. Nurse calls within 90 minutes.
The AI booked. The AI did not diagnose. The clinician decides the medical answer. Wake has the trail.
Reads urgency on every message. Emergency keywords bypass booking entirely and route to crisis guidance + on-call page.
Routes by specialty, requested clinician, language, and urgency. On-call rotation respected.
Hours, location, fees, what-to-bring, accepted insurance — all answered from approved sources with citations.
Forced handoff on clinical advice, prescription, emergency, and insurance-coverage questions. Confidence threshold cannot override these policies.
Every booking, every refusal, every clinical handoff logged. Auditable, defensible, exportable for compliance review.
No. The platform is configured to refuse clinical questions and route them to a human — clinician, front desk, or designated endpoint. The AI handles bookings, rescheduling, location, hours, parking, and routine logistics only. The refusal is policy-driven and audit-logged on every refusal.
The platform is designed with tenant isolation at the data plane, encrypted credentials, configurable retention, and a Wake audit trail. Specific compliance posture depends on your channel mix, the data you collect, and your data-processing agreements. Discuss requirements with us before going live; we sign DPAs and BAAs where appropriate.
Yes. Connected calendar tools let the AI propose, hold, and confirm appointment slots. Cancellation and rescheduling follow the same flow, with a Wake audit entry on each change. No-show fees and rescheduling-window policies are tenant-configured.
On channels that support it, the AI can collect basic intake data through a structured conversation with clear consent prompts. LIFF on LINE, a custom in-page form on web, or a structured chat flow on WhatsApp are all supported. Sensitive fields (insurance, history) can be redacted from the visible transcript.
Yes. Routing rules can match on requested clinician, specialty, location, language, or urgency. Out-of-rota requests follow the policy you configure — typically routed to the senior clinician on call.
Emergency intent is detected by Sonar and the AI will not attempt to book — it provides emergency-services guidance per your jurisdiction's standard, refuses any other answer, and pages the on-call clinician immediately.
Yes — outbound reminders via WhatsApp, SMS, or email follow channel-specific template rules. Patients can confirm, reschedule, or cancel by replying; the response loops back into the same routing policy.
Bring a sample inquiry or two — including the kind that mixes booking and clinical questions. We'll show what the routing decision looks like for each, and how Wake captures the audit trail.