Every appointment request, in one place
How a practice can see every inquiry and appointment request, whichever channel it came from, with someone responsible for each one.
This is a demonstration, not a client system. All names and details are invented. It holds no patient health information.
The kind of business
A multi-practitioner physiotherapy practice with a small front-desk team.
What often happens
Requests arrive by phone, WhatsApp, Facebook and the website. Each is checked by a different person, at different times.
What isn't working
Some requests get two replies, some get none, and nobody can say how many people asked this week.
One list, an owner, a next action
Every request lands here automatically or is logged in one step. Personal health details stay out of it.
Scroll sideways to see every column →
This week: 6 asked · 1 booked · 1 waiting on a patient · 2 due today
| Received | Channel | Request | Owner | Next action | Status |
|---|---|---|---|---|---|
| Mon 09:12 | Website | New patient, first assessment | Front desk: R. | Offer two times | Due today |
| Mon 10:40 | Reschedule Thursday visit | Front desk: R. | Confirm new time | Waiting on patient | |
| Mon 13:05 | Phone | Question about home visits | Practice manager | Call back with answer | Due today |
| Tue 08:30 | Fees for a sports injury plan | Front desk: S. | Send fee guide | Done | |
| Tue 11:15 | Website | Follow-up after third session | Physio: M. | Book review session Follow-up task created | Scheduled |
| Tue 15:50 | Phone | Referral from a GP | Front desk: S. | Request referral letter | In progress |
How the team would use it
Requests arrive in one list
Website forms flow in automatically; calls and messages are logged in one step.
Each request has an owner
Nobody wonders whether someone else has replied.
Confirmations and reminders go out on their own
Once a time is agreed, the patient gets a confirmation and a reminder.
Follow-ups don't depend on memory
After a visit, a follow-up task is created for the right person.
The owner sees the week at a glance
How many people asked, how many were booked, what's waiting.
Nothing measured yet
This is a demonstration, so there are no results to report. In a real engagement we'd agree a baseline, then track unanswered requests, time to first reply and follow-ups completed.
Ownership matters more than software
Most missed requests aren't caused by a missing tool. They happen because nobody is clearly responsible for the next step. The list makes ownership visible.