24 hours before
Before the appointment
Send preparation notes, location details, intake reminders, or practitioner-specific instructions.
Built for Cliniko clinics
Cliniko follow-up email automation
MyHealthFollowup sends clinic-controlled email sequences around appointments: pre-appointment reminders, post-visit instructions, review prompts, and longer-term recalls from the same template and rule system.
Cliniko API key handling stays on the backend
Draft HTML previews and test sends use synthetic sample data
Delivery, skipped, failed, cancelled, and retried states stay visible
Appointment journeys
One automation layer for reminders, recaps, recalls, and reviews.
Use Cliniko appointment types and practitioners to decide which sequence applies. Each rule can contain as many timing steps as a clinic needs, so the system does not lock you into fixed use cases.
2 hours after
After the appointment
Follow up with care instructions, next steps, review requests, or rebooking prompts.
Any offset
Longer-term recall
Keep 3 month, 6 month, or clinic-defined check-ins running without manual reception lists.
Current MVP control plane
The local sandbox now covers the core clinic workflow end to end.
A clinic can connect Cliniko, write HTML templates, test them, configure rules, sync appointments, process due messages, and review the operational trail from one dashboard.
Template designer
Full HTML templates, merge-field validation, Mailchimp import cleanup, desktop and mobile preview, and test email sending.
Rule builder
Appointment-type and practitioner filters with any number of before or after timing steps.
Operational controls
Sync appointments, process due messages, cancel or retry scheduled sends, and inspect redacted message events.
Audit history
Sensitive configuration and operational actions are logged with redacted details for clinic administrators.
Platform shape
Calm clinic operations, backed by explicit backend boundaries.
ClinikoConnection verification, metadata loading, appointment sync, and communication preference checks
TemplatesHTML editor, merge fields, import cleanup, preview, plain-text fallback, and test sends
SchedulingIdempotent scheduled messages, due processing, cancellation, retry, and failed outcomes
SecurityBackend-only key handling, tenant role checks, redacted events, and no patient data in browser storage
Patient-aware by default
The send path checks consent and communication preferences before delivery.
The product is designed for health-adjacent data minimisation: render late, store little, redact operational views, and keep sensitive configuration auditable.
Checks reminder and follow-up email preferences before sending
Fetches patient details close to send time rather than storing rendered content months ahead
Keeps Cliniko key values out of local storage, source, logs, and Postgres rows
Uses redacted previews and events for support without exposing recipient emails
Ready for cleaner patient communication?