Automation

Why enquiries go cold in the first hour

An enquiry that waits is an enquiry that keeps shopping. The fix is rarely faster humans: it is one intake surface, an immediate acknowledgement that sets an expectation, and enough qualification captured up front that the first real reply can be useful.

Drasyo

Updated

1 min read

A tarnished brass counter bell on an ochre ground beside a cream envelope closed with a violet wax seal, two worn leather tags lying nearby.

The failure is structural, not personal

When we audit a journey end to end, the enquiries that disappear almost never disappear because someone was careless. They disappear because the enquiry arrived somewhere nobody was watching: a second inbox, a social message, a form that emails one person who was on leave.

Nobody dropped it. There was no single place from which it could be picked up.

One surface, then a record

The first fix is consolidation: every route a customer can use ends in the same place, and every arrival creates a record with a state. Not a notification — a record. Notifications get read and forgotten. A record with an unresolved state is still there tomorrow.

Acknowledge immediately, qualify while you have attention

The moment after someone submits an enquiry is the only moment you are guaranteed their attention. Use it for two things: confirm what you received, and ask the two or three questions your first reply would have needed anyway. Which service. Roughly when. Roughly what size.

That is not a form to make the customer work. It is the difference between a first reply that asks for details and a first reply that answers.

Set an expectation you will meet

A named window — one working day, say — is worth more than “we get back to you fast”, and far more than silence, but only if it is true. An expectation you miss is worse than one you never set, so pick the number you can hold on your worst week, not your best.

Article FAQs

Still have questions?The short answers.

Is an automatic reply not just an obvious robot response?

It is, and that is fine when it does a job. A short acknowledgement that confirms what was received and says when a person will reply is useful information. What reads badly is an automatic message pretending to be a person, or one that says nothing beyond thank you.

Do we need a chatbot on the website?

Not necessarily. A chat widget adds another inbox to watch, and an unwatched one is worse than none. Start by making sure the channels you already have — form, email, phone, social messages — all land in one place with a record.

If you want this done

Automation

Automation here means the path an enquiry takes after it arrives: captured in one place, qualified by an agent asking what you would ask, routed to the right person with context attached, and followed up on a schedule rather than from memory.

See the service

Related reading