Interactive demonstrations
Systems in Action
The Anatomy of a Working System, then one enquiry followed through three connected views.
Interactive demonstration
The Anatomy of a Working System
Five steps, seven tools, one coherent journey. Press Assemble to see how a well-organised enquiry process fits together.
Concept onlyA demonstration, not a live system connected to a real form, CRM, inbox or automation.
Seven tools and five steps, not yet working together.
- Step 1
Enquiry
Someone gets in touch through your form or messages.
- Step 2
Information captured
Their details are saved to one CRM record.
- Step 3
Follow-up
They hear back quickly, in a personal tone.
- Step 4
Appointment
They choose a time without the back-and-forth.
- Step 5
Onboarding
A clear welcome shows them what happens next.
- Web form
- Social DMs
- CRM record
- Email sequence
- Reminder
- Calendar
- Welcome pack
Curious what your own journey would look like, step by step?Let’s map it together
Then follow one enquiry through three connected views
Systems in action
One fictional healthcare-coaching enquiry, followed through three connected views. These demonstrations show how I map and improve a workflow. They are concepts, not systems deployed for a client.
Concept onlyFictional data. Not connected to any live form, CRM, inbox or automation.
Fictional sample enquiry, shown on day 3
They experienceSends a question by form, email or social message.
- Behind the scenes
- Every channel lands in one shared list.
- Sample enquiry
- Arrives through the website form and is acknowledged right away.
They experienceShares a name, contact details and a reason. Nothing more.
- Behind the scenes
- One record is created. The form asks for no health information.
- Sample enquiry
- Record holds a name, email and “healthcare coaching”.
They experienceHears back personally, with a reply that fits.
- Behind the scenes
- The enquiry type decides which reply and next step to use.
- Sample enquiry
- Personal reply sent, with a link to book a consultation call.
They experiencePicks a time that suits them and gets a confirmation.
- Behind the scenes
- The booking updates the record and schedules a reminder.
- Sample enquiry
- Not booked yet. A gentle reminder is due today.
They experienceKnows what to expect and who they will see.
- Behind the scenes
- Welcome information goes out in a set order.
- Sample enquiry
- Follows once a call is booked.
Choose a stage, or play the journey to follow the sample from first message to welcome.
Explore this demoEight fictional records. Play shows a simulated move, not a real CRM.
- ALNew patient
- JTCoaching programme
- MCGeneral question
- Sample · day 3HCHealthcare coaching
- SBNew patient
- KDConsultation booked
- RPAttended
- ENNot ready yet
Stage ruleEnters when an enquiry arrives through any channel.
- Next action
- Send a personal reply.
- Sample enquiry
- Arrived through the website form on day 0.
Stage ruleMoves here when a personal reply has been sent.
- Next action
- Wait for a reply or a booking.
- Sample enquiry
- Personal reply sent on day 1, with a booking link.
Stage ruleMoves here when there is no reply or booking by the agreed day.
- Next action
- A named owner sends a gentle reminder.
- Sample enquiry
- No reply or booking yet. Gentle reminder due today.
Stage ruleMoves here when a consultation time is confirmed.
- Next action
- Send a reminder before the call.
- Sample enquiry
- Only moves here if they choose a time.
Stage ruleCloses with a simple business outcome: attended, rescheduled, not ready yet or not a fit. No clinical notes.
- Next action
- None. The record is closed.
- Sample enquiry
- Recorded after the consultation.
Choose a stage, or play the scenario to watch the sample record move through the pipeline.
Explore this demoHypothetical messages. Stops as soon as they reply or book.
Hi [first name], thanks for getting in touch. I’ve received your message and will reply personally within one business day. Please don’t include health details by email.
- When it’s sent
- Right away. Every message is written and reviewed by a person.
- Sample enquiry
- Sent on day 0.
Hi [first name], thanks for your patience. Based on what you shared, the best next step is a short call. You can choose a time here: [booking link].
- When it’s sent
- Within 1 business day. Every message is written and reviewed by a person.
- Sample enquiry
- Sent on day 1, with the booking link.
Just checking you saw my last message. I’m happy to answer any questions before you book.
- When it’s sent
- If no reply or booking. Every message is written and reviewed by a person.
- Sample enquiry
- Due today. No reply or booking yet.
I’ll pause here so I don’t crowd your inbox. If the timing is better later, just reply to this email.
- When it’s sent
- If still no reply or booking. Every message is written and reviewed by a person.
- Sample enquiry
- Only if there is still no reply or booking.
No further messages. The record is marked “not ready yet” and stays in the pipeline in case they get in touch again.
- Rule
- Stops immediately when they reply or book. Never chases more than a few times.
- Sample enquiry
- Ends early the moment they reply or book.
Choose a day to preview its message, or play the sequence.
Explore this demoConcept only · fictional data
Enquiry journey
One consistent path from first message to first visit or session, so no enquiry depends on who picks it up.
The gap it solves
Enquiries arrived by form, email and social message with no shared list, so replies depended on who saw them first.
How it works
- EnquiryEvery channel lands in one shared list.
- DetailsName, contact details and reason only. No health information.
- ReplyPersonal, and fitted to the type of enquiry.
- BookingThey choose a time. A reminder is scheduled.
- WelcomeInformation goes out in a set order.
What you’re seeing
The sample enquiry on day 3: captured, replied to on day 1, not booked yet.
Example
Concept only · fictional data
CRM pipeline
One shared view of every enquiry, with a clear rule for each stage and an owner for each next step.
The gap it solves
Leads were tracked across inboxes and memory, so no one could see who needed a reply, who had booked or who had gone quiet.
How it works
- New enquiryEnters from any channel.
- ContactedA personal reply has been sent.
- Follow-up dueNo reply or booking by the agreed day.
- BookedA time is confirmed.
- OutcomeA simple business outcome. No clinical notes.
What you’re seeing
Eight fictional records. The highlighted card is the same sample enquiry as in the journey.
Example
Concept only · fictional data
Follow-up sequence
A predictable rhythm of personal messages that never chases more than a few times.
The gap it solves
Follow-up depended on someone remembering, so some people heard back twice and others not at all.
How it works
- Day 0Acknowledgment, right away.
- Day 1Personal reply with a booking link.
- Day 3Gentle reminder, if no reply or booking.
- Day 7Final check-in, only if needed.
What you’re seeing
The sample is on day 3, so the gentle reminder is due today. Messages are hypothetical samples.