What has not worked?
Detail
The most useful question of all. Every real deployment has adjustments, bad weeks and things that had to be redone. If the answer is "everything is perfect", keep asking.
Cases and references
We do not publish named cases yet. We put you in touch with people who can tell you.
We could fill this page with "a leading clinic in Barcelona cut no-shows by 40%". We are not going to: an anonymous case cannot be checked, and a named one needs permission we do not yet have from our customers. What we can do is arrange a call with someone who has been running it for months.
Reference call
How a reference works
It is the fastest way to find out whether this works, and the one we have least control over.
- 01
You ask
Tell us your sector and the size of your operation. We look for the closest match we have, because a three-room clinic and a hospital have nothing in common.
- 02
We ask them
We never hand out anyone’s contact details without permission. We ask the customer and, if they agree, we introduce you directly.
- 03
You talk without us
The call is between you. We do not ask to be present or to be told what was said afterwards. If they tell you something does not work, that is information you need too.
What to ask
The questions that get real information
If you are going to speak to a customer of ours, make it count. These are the ones we would ask.
How long did it take you?
Detail
Our estimate is half an hour for the goal and an hour or two of technical session. Check it against someone who has been through it.
What do your customers or patients say?
Detail
It is almost everyone’s underlying worry, and someone months into a deployment has data rather than intuitions.
Did you have to change your process?
Detail
Automating usually forces you to write down rules that lived in people’s heads. Sometimes that is the most uncomfortable part of the project.
What happened when something broke?
Detail
Ask about a specific incident and how long we took to respond. Contract response times show up better that way than in an SLA.
Would you do it again?
Detail
And above all: would you do it the same way, or start with a different flow? The answer saves you the mistake they already made.
What we can tell you
What we see across deployments, without identifying anyone
Patterns that repeat often enough to be worth saying, and that you can check on the reference call.
None of these is a promise of results for your case. They are observations from live projects, and every one started from different conditions. Your project’s metric is agreed against your data before we start.
See how it worksWhat repeats
- The first flow is nearly always appointment or booking confirmation, because it returns fastest
- Internal resistance usually comes from reception, and disappears within two weeks — it is their repetitive work that goes
- Complaints from customers or patients are far fewer than the team fears before launch
- The biggest rollout delay is not technical: it is getting access to the scheduling system
- Centres that start several flows at once take longer to see results than those that start with one
- The automatic waiting list is the feature that surprises people most, and almost nobody asks for it up front
Want to speak to someone already using it?
Tell us your sector and the size of your operation and we will find the closest reference. If we have nothing like your case, we will say so rather than put you with just anyone.