Patient intake, on one thread.
Intake has the same shape everywhere: reach the patient, collect what the clinic needs, book the appointment, and leave a record someone can read. Alebex runs that sequence across voice, SMS and email as a single conversation.
Patient intake
A referral or a request enters, the agent reaches the patient, and the appointment lands in the calendar.
A referral, a form or a record — intake starts from something the clinic already holds.
Call recording is disclosed at the start of the call, and the recording is stored for audit.
The same questions, asked the same way, with the answers written to the record as fields.
SMS and email carry the same thread and the same memory, and a reply of “stop” ends contact on every channel at once.
The appointment is booked and the record updated in the same pass, not reconciled afterwards.
Anything clinical, and anything outside the approved answers, goes to a person with the thread attached.
One thread, whichever lane a step sits in.
Intake becomes a record without becoming clinical judgement.
The agent can gather approved details and arrange the next operational step. The moment a patient asks for clinical guidance, the thread changes hands with the work already completed attached.
The patient hears the clinic’s approved intake sequence, while each answer is written to the record as a field.
The handoff note shows staff what was asked, what was collected and exactly where the agent stopped.
Collection and scheduling on one side. Clinical judgement on the other.
The page is designed around this separation: approved operational work can continue, while every clinical question reaches a person with its context intact.
The agent collects and schedules. Clinical judgement is never inside its scope.
The fastest hallucination is still a hallucination.
Every sentence the model produces is checked before the caller can hear it, and the check runs alongside synthesis instead of in front of it. Pass and it speaks; fail and the in-flight audio is aborted and regenerated.
| Architecture | Arrangement | When the caller hears audio |
|---|---|---|
| The common alternative | A second LLM judging the first, in series | Only once the judge has returned. |
| Alebex | The check rides alongside synthesis, not in front of it | From the first sentence — the verdict lands under 50 ms alongside it. |
Arrangement, not to scale. The only time on this diagram is the verdict.
PIPEDA and CASL
Alebex claims PIPEDA and CASL compliance, and nothing beyond that.
Recordings, transcripts and customer information are held in Canada.
Built in Vancouver by Alexander Innovation Centre, Canadian-owned.
PIPEDA and CASL compliance built in.
“Stop” on any channel is handled immediately and the contact flagged.
Consent is disclosed at the start of every call, and recordings are stored for audit.
Patient intake resolves at the human clinical boundary.
The agent remains inside approved questions and operational steps. PIPEDA and CASL are the compliance claims made here; no broader certification is claimed.
Try the live demo
Drop in your website. Alebex reads it, learns what you do, and calls you in under 30 seconds — fully trained, zero setup.