When someone contacts a private clinic, I don't think the goal should be to respond within an arbitrary number of seconds.

The goal should be simpler.

Respond as soon as reasonably possible and make that response useful.

Someone who has taken the time to enquire has already shown intent. Leaving that person waiting unnecessarily creates friction at exactly the point where the clinic should be making the next step easier.

But response speed is only one part of the problem.

A fast automated message followed by poor communication isn't a good enquiry process. Neither is a quick phone call with no follow-up when the person doesn't answer.

The better question is not just how quickly your clinic responds.

It is what happens from the moment an enquiry arrives until that person either books, tells you they are not interested, or enters an appropriate follow-up process.

So, how quickly should a clinic respond?

As soon as reasonably possible.

I wouldn't give every private clinic the same response-time target without understanding how the business operates.

A clinic with a dedicated patient coordinator has different resources from a small practice where the same people may be dealing with patients, calls and administration.

The source of the enquiry matters too.

Someone who has just completed a consultation request may expect a different experience from someone who downloaded a guide and is still researching their options.

What I would avoid is unnecessary delay.

If an enquiry arrives during opening hours and nobody sees it for several hours because forms are checked manually, that is a process problem.

If an enquiry arrives in the evening and sits unnoticed until someone remembers to check a spreadsheet the next afternoon, that is also a process problem.

The target should be a response standard that is both fast and realistic for the clinic.

Then the systems around the team should help them meet it consistently.

Why response time matters

Think about what happens immediately before someone enquires.

They may have searched for a treatment.

They may have compared several clinics.

They may have read reviews, looked at a clinician's profile, checked pricing or spent time understanding whether a service is right for them.

Eventually, they decide to take action.

That moment matters.

The clinic now has an opportunity to turn interest into a conversation.

If nothing happens, the patient is left waiting.

They may continue researching. They may contact another clinic. They may become distracted. Or the urgency that made them enquire may simply disappear.

That doesn't mean every delayed response loses a patient.

It means delay introduces avoidable friction into a journey where the person has already taken the first step.

A response is not the same as an acknowledgement

This distinction matters.

Imagine someone completes a form and immediately receives:

"Thank you for your enquiry. A member of our team will contact you shortly."

Technically, the clinic has responded.

But the patient hasn't necessarily moved any closer to booking.

An acknowledgement can still be useful. It confirms that the enquiry has been received and can set expectations about what happens next.

But I would separate two things:

Acknowledgement: confirming that the clinic has received the enquiry.

Meaningful response: helping the person take the next appropriate step.

That next step might be answering a non-clinical question, arranging a call, collecting useful information, directing them towards booking or handing the conversation to the right person.

A good enquiry system needs to think about both.

What should happen during opening hours?

I would start by mapping what happens today.

A new enquiry arrives.

Who receives it?

Where does it appear?

Who owns the next action?

How quickly do they normally see it?

What happens if that person is busy?

What happens if the patient doesn't answer?

These questions often reveal more than choosing a response-time target.

If three members of staff assume somebody else is handling the enquiry, ownership is unclear.

If enquiries arrive through forms, email, Instagram, WhatsApp and telephone but there is no central view of them, opportunities can be missed.

If the team only follows up when somebody remembers, the process depends on memory.

The aim should be to create a defined route from enquiry to next action.

Technology can support that route.

It shouldn't be required to compensate for a process nobody has defined.

What about enquiries outside opening hours?

This is where automation can become useful.

A clinic doesn't necessarily need a member of staff answering every enquiry late at night.

But the patient also doesn't need to feel as though their message has disappeared into a black hole.

An immediate acknowledgement can confirm that the enquiry has arrived.

It can explain when the clinic is open.

It can tell the person when they should expect a human response.

Depending on the clinic and the type of enquiry, it may also be appropriate to provide a booking option or gather some basic non-clinical information.

The important part is setting the right expectation.

If automation tells someone that a team member will contact them the next morning, the process needs to make sure that actually happens.

Otherwise, automation has simply created another promise for the clinic to break.

Missed calls need a process too

Forms aren't the only enquiries worth measuring.

Someone can call while the reception team is busy.

They may leave a voicemail.

They may hang up without leaving one.

They may try again later.

Or they may call another clinic.

I would want to understand what happens to those missed opportunities.

Does someone receive an alert?

Is there clear ownership?

Is the call returned?

Is there a process for contacting the person through another appropriate channel where permission and systems allow it?

A clinic can spend a significant amount of time improving advertising and landing pages while paying far less attention to what happens when the telephone actually rings.

The patient journey doesn't stop when the marketing generates the enquiry.

That is where another part of the journey begins.

Speed should not create a worse patient experience

There is a danger in treating response time as the only metric that matters.

You can make a system faster and still make it worse.

A patient doesn't benefit from receiving five automated messages in ten minutes.

They don't benefit from being pushed towards a consultation before their basic questions have been addressed.

And they don't benefit from an AI system pretending to provide clinical advice that should come from an appropriately qualified professional.

Healthcare requires boundaries.

Automation can help with approved information, administrative questions, routing, reminders and appropriate non-clinical qualification.

There should also be a clear route to a human when one is needed.

The goal is not maximum automation.

The goal is a better patient journey.

Where AI can help

AI can be useful when it solves a specific problem.

For example, a clinic may receive enquiries outside normal working hours.

Instead of only sending a generic confirmation email, a carefully designed conversational system could potentially answer approved non-clinical questions, gather useful context and explain the next step.

That could make the experience more useful while reducing repetitive work for the team.

But I wouldn't begin by asking:

"How can we add AI?"

I would ask:

"Where is the current enquiry process failing?"

If the problem is slow acknowledgement, simple automation may be enough.

If the problem is poor ownership, the clinic may need a better workflow.

If the problem is missed follow-up, CRM automation may be more useful.

If patients repeatedly ask the same appropriate non-clinical questions before booking, conversational AI may become relevant.

The technology should follow the problem.

Not the other way around.

Measure more than response time

Response time is useful.

But on its own, it doesn't tell you whether the enquiry process is working.

I would also want to understand what happens afterwards.

How many new enquiries does the clinic receive?

How many receive a response?

How many people does the team successfully contact?

How many appropriate enquiries become booked consultations?

How many don't respond to the first attempt?

How consistently are those people followed up?

How many enquiries are eventually marked as lost?

Why are they being lost?

You may discover that response speed is the main constraint.

You may discover it isn't.

For example, a clinic could respond quickly but still struggle because its booking process is difficult.

Another could have strong initial conversations but almost no follow-up.

Another could generate plenty of enquiries but attract people who are not suitable for the service.

This is why I prefer to diagnose the patient journey rather than optimise one metric in isolation.

Build a response system, not just a response target

A target can be useful.

A system is more useful.

If a clinic decides that new enquiries should normally receive attention quickly during working hours, the next question is how that will happen consistently.

That means defining things such as:

Who owns new enquiries?

Where do they appear?

What happens when the usual person is unavailable?

Which enquiries can receive an automated acknowledgement?

When should a human take over?

What happens when the patient doesn't answer?

How many follow-up attempts are appropriate?

When does an enquiry move into longer-term nurture?

How is performance measured?

The exact answers will vary between clinics.

The important part is that there are answers.

Start with the patient journey

Response speed matters because it sits at an important point between acquisition and booking.

But it shouldn't be treated as an isolated trick for increasing conversion.

It is one part of a connected patient journey.

At Evolte, I think about that journey across seven broad stages:

Acquire → Engage → Qualify → Book → Nurture → Retain → Reactivate

Response time sits mainly within Engage.

But what happens there affects everything that follows.

A fast response cannot fix poor qualification.

Good qualification cannot fix a confusing booking process.

A booking process cannot recover every patient if there is no follow-up.

The stages need to work together.

That is why, before spending more money generating enquiries, I would want to know what happens to the ones the clinic already receives.

Sometimes the answer is simple.

Sometimes it requires better processes, automation or technology.

But the starting point is the same.

Make it easy for a person who has shown interest to take the next appropriate step.