How each feature works, state by state.
One page per feature, drawn from the prototype: what starts each state, what ends it, and what production still has to send the screen. Newest change first.
Portal messages in the Inbox
The patient writes in the portal and it lands in the staff Inbox beside WhatsApp. The channel decides who reads and who answers: Presale and Patients tabs, envelopes, what an automatic message opens, the two roles rows, and what Artur and Greg build.
Promo, and how a landing page gets published
What belongs in the promo repo, how a landing page reaches promo.amiro.health, and the branch rule that keeps the live site out of harm.
Booking and rescheduling from the portal
Patients confirm, move, cancel and book on their own: every visit email opens that one visit, the portal does the same and books through the region’s patient widget. The desk sees who changed what. Curitt only.
Calls from Amiro
The desk calls a lead from Amiro, through the browser, from the clinic’s own number over Twilio. Eight pages, one per state: before the call, placing it, on the call, voicemail, when it does not connect, wrap-up, recording and transcript, phone numbers.
The Presale queue
How a lead moves in the Presale list when the desk books, writes, puts it later or calls, and the call is answered, busy, unanswered or a voicemail. The rules behind it and how nothing is forgotten.