Set Clear Local Enquiry Response Expectations Across Phone and WhatsApp

A “Message us” button can create an expectation of a quick answer even when the business is serving customers, driving between jobs or closed for the day. If the customer receives no acknowledgement, they may contact another provider. The fix is not to promise instant replies; it is to explain when the business normally responds and to assign responsibility for follow-up.

Separate acknowledgement from resolution

An acknowledgement confirms that the enquiry arrived. A resolution answers the question or completes the booking. These should not be confused.

For example, a small service firm might say: “Messages received during business hours are normally reviewed within two working hours. A confirmed appointment depends on technician availability.” This is an example only; publish a window your team can meet consistently.

Build a simple channel queue

Use one shared log or approved business inbox with:

• Time received.
• Customer's preferred channel.
• Locality or branch.
• Requested service.
• Preferred language, if provided.
• Person responsible.
• Next action and due time.
• Status: new, awaiting details, quoted, booked, closed.

Avoid placing sensitive information in a shared sheet unless access is controlled and the information is necessary. Do not ask customers to send identity documents or private data when a simpler enquiry will do.

Decide when a phone call is better

Some enquiries are easier to clarify by phone, such as a complicated repair or a job with several site constraints. Ask permission before calling and summarise the agreed next step in writing. If a customer prefers messages, do not repeatedly call without a clear reason.

For multilingual teams, record the language the customer asks to use rather than assuming it. A short, clear acknowledgement in that language is better than a long machine-translated explanation that could misstate price or timing.

Publish the promise where the enquiry begins

Put response hours near the contact button, not only in a policy page. State what happens outside those hours. If the business is not monitored at night, avoid language implying continuous support. Keep the website, Business Profile information and automated replies consistent with actual staffing.

Review the missed-enquiry pattern

Once a week, compare enquiries received with first responses and completed bookings. Look for periods when nobody owns the queue, repeated questions that could be answered on the website, and localities that need a clearer service-coverage answer. Business Profile reports can show certain interactions, but a click or message count does not automatically prove that the enquiry was answered.

The purpose of a response promise is to help the customer choose a suitable contact route and help the business keep its word. A modest, reliable window is more useful than “instant reply” language that staff cannot sustain.