Operational constraint
One customer journey across disconnected systems.
An enquiry may begin on WhatsApp, continue by phone and become an appointment in another calendar. When those steps separate, reception loses context and managers cannot see which administrative follow-up is waiting.
System blueprint
What the operating layer connects and prepares.
Signals brought together
- WhatsApp and form enquiries
- Appointment availability
- Consent and contact history
- Visit and follow-up status
Work prepared
- Available appointment options
- Reception follow-up queues
- Reminders and administrative messages
Human decision
Reception confirms the appointment. Clinicians retain all responsibility for clinical advice, assessment and treatment decisions.
Crosvia CRM · Purpose-built booking workflow · Approved messaging connections
Example workflow · Review required
From signal to a reviewable next move.
- 01 · Signal
A returning patient asks for an afternoon follow-up and two appropriate appointment slots are open.
- 02 · System reading
This is an appointment-coordination task with enough administrative context to prepare a response.
- 03 · Prepared move
Prepare both time options and place the enquiry in the reception review queue.
- Responsible person
- Reception team
- Status
- Awaiting review
Implementation questions
Before system mapping begins.
- Does Crosvia make clinical decisions?
- No. Crosvia can prepare administrative work and surface context; qualified clinicians remain responsible for clinical decisions.
- Can the system connect WhatsApp and appointments?
- Yes, where the clinic uses supported channels and provides the required access and consent. The exact connection is defined during system mapping.
- What should a clinic start with?
- Start with one measurable hand-off, such as enquiry to confirmed appointment or attended visit to follow-up.