One workflow.
A pilot you can judge.

Start with the last real example.

Ask your team to walk through the most recent enquiry, callback or administrative handoff. Where did it arrive? Who accepted it? What happened next? Which record proves the outcome?

The useful starting point is a specific sequence the team recognises. “We need more AI” is too broad to test. “A request changes branches and nobody can see who owns the next action” gives you something concrete to investigate.

Make the first scope small.

Choose one workflow and define its trigger and end state. That might be an unanswered-call callback, an enquiry assigned to a branch, or a recurring task passed to managed support.

These are examples of possible pilots, not findings about your business. Use your records to choose the work worth changing.

Write down what is excluded. An enquiry-routing pilot does not automatically include clinical triage, a replacement booking system, every marketing channel or a complete CRM migration.

Measure the starting point.

Choose an observation period that includes the working patterns you need to understand. Decide which records are eligible and how duplicate enquiries are handled. Keep the same definitions when reviewing the pilot.

• Response: time to a meaningful response, separate from an automatic acknowledgement.
• Ownership: unassigned work and handoffs accepted by a named person.
• Outcome: completed next actions and confirmed bookings or resolutions.
• Effort: measured staff time, corrections and rework.

You can begin with a modest, well-defined sample. If you cannot measure a result yet, record that limitation; do not turn an estimate into a baseline.

Design the failure route before the happy path.

A pilot needs an authoritative system and an accountable person. Specify what happens when the preferred branch is busy, an integration fails, a record is duplicated or the request needs human judgement.

The owner of a handoff must accept it. Sending a notification is only a delivery event. It does not establish that someone is doing the work.

Agree contact permissions, access, retention and stopping rules before enabling follow-up. Sensitive or clinical requests belong with the appropriate staff and approved systems.

Test with fictional requests first.

Run the normal route and the exceptions. Include a busy branch, wrong branch, duplicate, reply, opt-out and a failed system connection. Have the people receiving the work inspect the resulting records.

Do not treat a successful demonstration as a confirmed production integration. Delivery feasibility, access and operational sign-off still need agreement.

Make the commercial decision inspectable.

List implementation, recurring fees, expected usage, additional integrations, training and internal effort. Agree who approves the spend and who can stop or roll back the pilot.

A booking-only break-even calculation can give you a threshold. It does not tell you how many additional bookings the change will produce. Count staff time recovered separately from cash saved.

Use the clinic-group break-even calculator for a transparent example using your own inputs.

Agree the review before going live.

Write down the review date, service-quality requirement, result being tested and acceptable cost or rework. At review, choose continue, revise or stop against those definitions.

A better process might help reception without producing a new booking immediately. A new booking might have happened without the pilot. Keep both possibilities visible when deciding what to do next.

One clear workflow gives the team something they can test, own and improve.

The practical next step

Download the brief and fill in the workflow, current owner and next action. You do not need to complete every field before a first conversation; the unknowns help define what the review needs to establish.

Discuss your business workflow · Review a clinic group’s enquiry process

This framework is an implementation proposal, not a completed performance study. Vertex Research is part of SJ Vertex Group; the commercial affiliation is disclosed.