Booking, reminders and enquiries for healthcare and wellness
People want to book a visit easily, get a reminder and reach someone when they have a question. We build the booking site, the WhatsApp line and the inbox behind them, and judge marketing by the bookings it brings.
What gets in the way
Booking only by phone
People who want to book at night or between meetings have to wait until the line is open.
Missed visits
A visit booked weeks ahead is forgotten, and the slot stays empty.
Questions on every channel
Questions arrive by phone, WhatsApp and Instagram, and the answer depends on who sees them.
What we build for it
Solution
Booking & scheduling
People pick a service, a day and a time, and get a reminder.
- Booking sites
- Appointments & calendars
- Reminders & confirmations
- Deposits & payments
Solution
WhatsApp & customer messaging
Questions and reminders on WhatsApp, from one team inbox.
- WhatsApp inbox & automation
- Templates & broadcasts
Solution
CRM & sales
Every enquiry in one inbox, with an owner and a next step.
- Lead capture & follow-up
- Pipelines & reminders
- Customer history
Solution
Lead generation & growth
Marketing judged by the bookings it brings.
- Landing pages
- Campaigns
- Follow-up & nurture
Solution
Customer & partner portals
People see their own bookings and documents without a phone call.
- Customer portals
- Partner & supplier portals
- Documents & requests
Services behind it
Work and examples
The examples on this page are demos with made-up data.
Demo · sample data
Try the booking site
Book a slot as the customer on a sample site, then switch to the team inbox, where the enquiry lands once, on one record, with the source it came from.
Demo · sample data
Try the WhatsApp inbox
Follow one enquiry through a team inbox: the number’s flow asks its first question and routes the answer, and the contact record keeps the full history and where the enquiry came from.
Demo · sample data
Try cost per booking
Two channels spend the same and bring the same number of enquiries, so cost per lead says they are equal.
Delivery considerations
Data and access
Who can see and change which records is agreed in the written scope, before anything is built.
A log of every change
The systems we build can keep a log of who changed what and when.
Your existing systems
We connect to the systems you already use where they allow it, and say so in the scope where they do not.
Questions we get asked
Can it connect to what we already use?
Usually. WhatsApp, Google Workspace, Microsoft 365, accounting packages, payment providers and most systems with an API or an export. If something cannot be connected we say so in the scope.Do we own the software?
Who owns the code and the accounts the system runs in is written into the scope before any build starts, so there is no question about it later.What does it cost?
It depends on what the process needs, so we price each project in writing after a short scoping call rather than publish a rate card. The written scope sets out exactly what the price covers.
Your business may need something different.
Tell us how your team works, what is slowing it down and what you want to improve.