The landing page builder creates a public-facing marketing website for the clinic, served from the same installation, on the clinic's own domain or subdomain. New patient enquiries submitted through the contact form flow directly into the clinic's patient list.
The clinic admin uses a visual builder to compose sections, about the clinic, services, doctor profiles, contact details. Each section can be written manually or generated by the AI layer from a short prompt. The published page is served publicly on the clinic's configured domain.
The admin provides a short description of the clinic and the AI generates section copy, about section, services list, and doctor bio. The generated content is editable before publishing; it is never published automatically.
Enquiries submitted through the contact form are captured as leads in the clinic's system. Leads can be converted to patient records with one click. UTM parameters from the referring URL are captured alongside the submission, so the clinic can see which campaign or referral source produced each enquiry.
With the white-label add-on: the "Powered by" footer attribution is removed, all patient-facing emails are sent from the clinic's own domain (requiring correct SPF/DKIM DNS configuration), and the patient portal can be served from a custom subdomain. Nothing in the patient-facing experience identifies the underlying platform.
The clinic admin enters a GA4 Measurement ID in settings. The platform injects the standard Google Tag (gtag.js) on every page, the main application, the patient portal, and the landing page, so all traffic is tracked in a single GA4 property.
A Search Console domain verification meta tag can be added from settings and is inserted on public-facing pages for property verification.
UTM campaign parameters (source, medium, campaign) are captured from the URL when a contact form is submitted and stored against the lead record. When a lead is converted to a patient, the referral source is preserved on the patient record for lifetime value tracking.
All outgoing emails, appointment confirmations, reminders, prescription notifications, invoices, ABHA linking confirmation, use branded HTML templates with the clinic's logo and contact details injected automatically.
Staff can send one-off rich HTML or plain-text emails to any patient or any email address from within the clinic application, useful for personalised follow-ups or bulk communications outside the normal automated flows.
All outgoing emails are logged with recipient, subject, send status, and timestamp. Open events are tracked via a small transparent image embedded in HTML emails. Delivery failures trigger a logged error and optionally a retry.
The demo comes pre-loaded with real sample data, so you can click through actual appointments, patients and prescriptions.