One enquiry.
One accountable owner.

How should a clinic group route enquiries?

Start with one identifiable enquiry record, a relevant branch, a named owner and an agreed next action. Use the existing practice system's capabilities where they fit. Add a separate tool only when it solves a documented gap.

A shared inbox helps the team see requests. It does not establish who is responsible for completing a handoff.

Define the minimum useful record.

• Enquiry time, contact route and permitted contact details.
• Preferred branch, or a flag that the caller has no preference.
• Administrative request category and any approved escalation flag.
• Named owner, next action and due time.
• Current outcome, including whether contact or a booking is confirmed.

Keep clinical information in the clinic's approved systems. This guide describes administrative ownership, not clinical triage or a replacement for patient records.

Use stages that describe work.

Handle a branch transfer explicitly.

Do not close the first branch's task merely because someone forwarded an email. Record the receiving owner, preserve context and require acceptance. Until acceptance, the original owner needs clear responsibility for checking the handoff.

If the preferred branch cannot help, use agreed alternatives and confirm the person's preference. If there is no suitable route, create an exception task for a named person.

When should follow-up stop?

Stop or pause automatic follow-up when a reply needs attention, a booking is confirmed, the person opts out, contact details fail, the enquiry is resolved or staff mark it for review. Apply the rule across channels so a WhatsApp reply does not leave an email sequence running.

Choose timing from the enquiry context and the person's preferences. A generic series should not keep chasing everyone on the same schedule.

The ICO distinguishes purely administrative service messages from direct marketing. Adding promotional content can change the classification. Review message purpose and contact permissions before deploying a sequence.

What if your software already offers pipelines?

Pabau's first-party documentation describes location-based lead pipelines and lead cards with owners and activities. Check how your current setup uses these features before adding another CRM.

Documentation confirms the described capability, not how well a particular clinic has configured it or whether another supplier has integrated with it.

Measure the right outcomes.

• Unassigned enquiries and overdue next actions by branch.
• Time to a meaningful response, separately from automatic acknowledgement.
• Successful contacts divided by eligible enquiries.
• Confirmed bookings divided by the same eligible enquiry set.
• Handoffs accepted and resolved, including failed transfers.
• Correction work and staff time.

Agree exclusions and the comparison period before a pilot. Do not count duplicate enquiries as separate people or label all bookings as new revenue generated by automation.

Watch a hearing-care enquiry workflow example

A pilot you can evaluate.

Choose one handoff or channel. Map its current process, agree the owner and fallback, then test with clearly marked fictional enquiries. Review the records with reception before expanding.

Sources

• Pabau: lead pipelines, owners and activities
• ICO: service messages and direct marketing

The workflow and stage names above are implementation recommendations, not a published performance study.

Discuss a clinic-group review · Compare reception models