Return rules
The business defines when a customer is due. These are service rules, not automated medical advice.
How it works →REBOOK REPEAT · FICTIONAL TESTING ONLY
A proposed workflow for customers who are due to return. Use business-approved intervals, check permission and future appointments, then review the exact follow-up before live activation.
Real uploads, messaging, launch and trial remain locked.
Video coming soon · placeholder
Explore the proposed service. The current application supports fictional workflow testing; real uploads, messaging, launch, and the trial remain locked.
The business defines when a customer is due. These are service rules, not automated medical advice.
How it works →A future booking excludes the customer from the relevant reminder. Stale source data holds outreach.
How it works →The owner reviews the audience, sender, wording, and booking destination.
How it works →Customers use the business’s existing booking link. A request is not a confirmed appointment.
How it works →Replies hold automated follow-ups and go to the designated business staff.
How it works →Record confirmation and completion only when source evidence is available.
How it works →Business setup, privacy review, exact campaign approval and the fictional workflow are available to explore. Live service remains locked.
Build readiness register →