If you already use Cliniko, the goal is not to replace a working system. It is to remove the repetitive customer conversation that happens before and around the booking while keeping Cliniko in its proper operational role.
Do not replace Cliniko just to add AI
Automation should cover administration, not diagnosis or triage.
The strongest architecture is usually a conversational layer in front of the system the team already trusts. That means the customer gets faster answers while staff keep the scheduling, service and practitioner logic they already know.
Where the manual work happens today
For Cliniko practices, the repetitive work often happens before a booking is created. Customers ask which service they need, what it costs, whether a particular person is available, how long the appointment takes, and what they should do next. Those questions are easy to underestimate because they are scattered across website chat, WhatsApp, Instagram and staff inboxes.
What the AI layer should handle
A useful Cliniko workflow can answer “which appointment do I need?” from approved practice information, collect non-clinical booking context, match the requested service to configured availability, and escalate symptoms and clinical judgement. The assistant should ask only for the missing information required to move the customer forward, rather than forcing every enquiry through the same script.
- answer “which appointment do I need?” from approved practice information
- collect non-clinical booking context
- match the requested service to configured availability
- escalate symptoms and clinical judgement
Build the knowledge before the automation
Start with the information a good receptionist would confidently answer: service names customers actually use, published prices or ranges, appointment durations, practitioner or staff responsibilities, opening hours, location details, preparation steps and cancellation policy. Review every line before it becomes customer-facing.
Map customer language to the right appointment
Customers rarely use the exact labels configured in Cliniko. They ask in natural language. The front-desk layer needs to recognise those intents and map them to the correct service or next step without silently changing the booking rules. This is where a generic booking widget often creates friction.
Keep availability authoritative
Automation should cover administration, not diagnosis or triage.
When direct booking is supported, times should come from the configured source of truth. The assistant should not cache or invent availability, and staff should not need to reconcile a second diary after the conversation.
Handle the non-happy path too
Test what happens when the preferred practitioner is unavailable, the requested time is full, the customer wants multiple services, a booking needs changing, or the question moves beyond routine reception. Those are the situations that determine whether automation genuinely removes work.
Know when a person should take over
Clinical, regulated, sensitive, complaint-related and judgement-heavy questions belong with people. Even in non-regulated businesses, bespoke quotes and policy exceptions may need staff. The handover should carry the conversation context so the customer does not start again.
Where Vallamo fits
Vallamo currently answers on website chat, WhatsApp and Instagram DM from approved business information. It connects to supported booking systems and keeps the booking platform or calendar as the source of truth. Voice is coming soon, so the present-day use case is digital front-desk coverage.
A practical rollout checklist
- Review the customer-facing knowledge and remove anything uncertain.
- Map the highest-volume enquiry types to the correct Cliniko service or next step.
- Test booking, no-availability, cancellation and handover scenarios.
- Launch first on the channel producing the most repetitive enquiries.
- Review real conversations weekly and approve improvements deliberately.
Roll out one channel before every channel
Even when the final goal is consistent coverage across website chat, WhatsApp and Instagram, it is sensible to begin with the channel that creates the most repetitive enquiries. That gives the team a smaller set of real conversations to review and makes mistakes easier to isolate. Once the service mapping, knowledge and handover behaviour are reliable, the same approved logic can be extended to the other live channels without rebuilding the process from scratch.
Ownership still matters after launch
Assign one person to own the customer-facing knowledge and booking rules. When a service is renamed, a price changes, a practitioner leaves, opening hours change or a policy is updated, that owner should know exactly where to make the change and how to test it. Good automation becomes less reliable when nobody owns the source information. A short monthly review of unanswered questions and failed booking attempts is often enough to keep the workflow accurate.
What the integration should not try to do
Do not use the conversational layer to recreate every feature already handled well inside Cliniko. The value comes from improving the customer-facing gap before and around the booking, not from duplicating practice management, reporting or diary administration. Keeping the roles clear makes the setup easier to maintain and reduces the risk of staff having to check two competing versions of the same information.
What success should look like
Measure completed bookings, qualified handovers, after-hours coverage, average response time, common unanswered questions and staff interruption rather than chat volume alone. The purpose is not to generate more conversations. It is to convert more of the conversations you already earned into useful outcomes.
Frequently asked questions
Which Vallamo channels are live today?
Website chat, WhatsApp and Instagram DM are live today. Voice is described publicly as coming soon.
Can Vallamo book appointments?
Vallamo supports booking through configured and supported scheduling workflows, with the existing calendar or booking system kept as the operational source of truth. Calendly is currently described as a scheduling-link workflow.
What happens when Vallamo does not know the answer?
It should not invent business-specific information. The conversation can be captured or handed to a person when the answer is not in approved knowledge or needs judgement.
Should AI replace the front desk?
Not necessarily. The strongest use case is often AI for repetitive first-response and booking work, with people keeping control of sensitive, unusual and judgement-heavy conversations.
Further reading
Want to see Vallamo on your own customer questions? Book a demo or see how the product works.