Every protocol runs inside a room.
Amura's clinical programs are built as rooms. They're time bound, configurable, and tied back to an atomic service definition. A 90-day gut health protocol is really a treatment room with a prescribed meal plan, a recipe library, AI nutrition insight, and compliance tracking baked in. The atom holds the rules. The room runs the program.
Twenty-two thousand clinical records, each living in a WhatsApp thread.
WhatsApp wasn't a stopgap. It was the actual system. Dietitians sent meal plans in chat. Patients logged their meals in reply. Consultations, lab results, medication adjustments, progress updates, all of it moved through individual conversations. For the first hundred or so clients, it was personal and it mostly worked.
Then the platform grew to thousands of active clients. A dietitian managing two hundred clients had two hundred separate threads, each one holding a different treatment history at a different point in a ninety-day program. Finding a specific patient's compliance log from three weeks back meant scrolling through messages. Sending an updated meal plan meant sending it manually to every person it applied to. Nothing surfaced unless someone went looking for it.
The chat interface wasn't the problem. The problem was that a conversation thread is not a clinical record, and it never was.
Program lifecycle
Three rooms. One patient. Four constructs underneath.
Every patient journey runs through three rooms in sequence: a sales room for intake and qualification, a diagnosis room for clinical assessment, and a treatment room where the doctor prescribes the 90-day plan. Pools hold the care team. Services define what each person does inside each room. The tree sequences the journey gate by gate. The rooms run it.
Every service is defined before it touches a patient.
The practitioner builds the program at the atomic level: its overview, tags, delivery modules, images, and pricing tiers. The Gut Reboot is a 21-day wellness program with video sessions, live Q&A, and tiered pricing, all set once at the source. Every room and every patient inherits from it without ever changing it.
Configured at this level
Each delivery piece, whether it's a video session, a live Q&A, or a guided exercise, gets defined right here. The room scheduler reads these to build the patient's timeline, so nothing gets improvised downstream.
Base, early bird, and promo tiers all live at the atomic level. The CPQ engine reads them at checkout, and the store item inherits them without ever overwriting the source.
Sub-offerings bundle into rooms. The patient joins after payment.
Services and products merge into a Room Config, which is the clinical pathway itself. A single room can hold a sales room for discovery, a diagnosis room for intake, and a treatment room for the active program. The offering goes up on the store, and the moment the patient pays, they're dropped into the room and the program clock starts.
A 90-day elimination diet, one meal at a time.
The meal planner is the backbone of the diet protocol. Every day has its own set of meals tied to the current phase, so the patient always knows what to eat, when, and the calorie target for each one. The same plan also turns up inside the treatment room, where each meal lands as a reminder card the patient can act on without leaving the chat. Every "Had it" gets logged against the program, so compliance just happens in the background.
The day view lists every prescribed meal with its time and calories, plus a quick way to swap one out. Inside the chat, the same meal shows up as a reminder card, so the patient can mark it done right where the conversation is happening. No separate app, no manual logging.
Every recipe comes with a clinical insight tuned to the patient.
When a patient opens a recipe, the AI reads what they're managing, things like blood sugar targets, restrictions, and macro goals, then writes a short nutrition note specific to that dish. It isn't generic advice. It's worked out against their profile the moment the recipe loads. Tapping "Prepare it" walks them through the cooking, one timed step at a time.
Prepare
The AI insight banner shows up on every recipe, a one line clinical note (macros, blood sugar, allergens) tuned to whatever the patient is managing. Tapping "Prepare it" steps through the recipe with timers and a video option for each step. The cooking experience is the care experience.
The program runs its course. The patient renews, or the room closes.
When the program period runs out, the system checks for a renewal. If the patient pays, the room just keeps going, with the same clinical history and the same setup, extended into the next cycle. If they don't, the room is terminated. Access ends, every record is kept, and the offering is marked complete.
More clients, more care, less noise.
- Every client record living in a separate WhatsApp thread
- Dietitian scrolling through hundreds of chats to find history
- Meal plans and updates sent manually per client
- No way to see compliance without checking each conversation
- Every client in a structured treatment room with full history
- Listener flags patterns without the clinician reviewing every entry
- Meal plans prescribed at program level, delivered day by day
- Signal surfaced automatically so clinicians see what needs attention
on platform
80 to 220
daily compliance
"The part that took the most time was the daily check-ins. Logging entries for each client, sending out meal reminders one by one because everyone eats at a different time. Most of that runs automatically now. Clients upload a photo of their meal or their weight and it gets logged. The reminders go out on each person's schedule without anyone having to send them. Prescriptions sit inside the subscription so I can see where every client is without keeping a separate tab open for each one."