Set a Realistic Enquiry Response Time for a Small Marketing Team

Executive summary

A business can publish a strong call to action and still lose trust if nobody responds to the resulting enquiry. The solution is not automatically “reply within five minutes.” A promise that a two-person team cannot keep creates repeated failure. Instead, set a realistic response standard for each channel, define what counts as a first response, and specify who covers the inbox when the usual owner is absent.

Allow about one hour to map current channels and agree the first version of the standard. Review performance after two weeks. The example targets below are starting points for discussion, not universal benchmarks.

Separate acknowledgement from resolution

A first response means the customer knows the enquiry arrived and understands what happens next. It does not mean the business has completed a quote, diagnosed a problem, confirmed stock or solved a complaint.

This distinction allows a small team to respond reliably without making promises it cannot honour. For example: “We’ve received your request. Our team checks new service enquiries during business hours and will reply by the next working day.” Use only a commitment the business can actually meet.

Set channel-specific expectations

Channel	Example service standard	Coverage owner
Website form	Acknowledge during business hours; substantive reply by next working day	Enquiry coordinator
WhatsApp business inbox	Check at agreed intervals, such as 10:30, 13:30 and 16:30	Duty staff member
Social direct messages	Review twice per working day	Content owner or backup
Email	First response within one working day	Shared inbox owner
Missed business call	Return the call during the next staffed period, where appropriate	Front desk

Adjust the standards for operating hours, service urgency and customer expectations. A business that accepts emergency requests needs a different process from a boutique that answers non-urgent product questions. If a channel is not monitored continuously, say so clearly and provide a more suitable contact method for urgent matters.

Design the coverage rule before writing the SLA

A response target without coverage is only a wish. Name a primary owner and a backup for each inbox. Define the handover point: for example, if the primary owner is away for more than half a day, the backup takes over new enquiries and flags anything requiring specialist input.

Do not share one person’s password to create coverage. Use the platform’s supported role or access features where available, and remove access when responsibilities change. Google Business Profile, for example, supports owners and managers with role-based capabilities; that is different from sharing a personal login.

The duty owner should know what they can answer independently and what needs approval. A simple escalation list might include pricing exceptions, safety complaints, refund requests, legal threats and requests involving sensitive personal information. The first responder can acknowledge the message while routing it to the authorised person.

Use a queue, not memory

A shared tracker can be as simple as:

received_at | channel | enquiry_ref | priority | assigned_to | first_response_at | next_action | status

Use a reference number in the marketing tracker and keep full conversation details in the appropriate customer-service system. Avoid copying private message histories into a general marketing sheet.

Define statuses carefully. “New” means nobody has acknowledged it; “acknowledged” means the customer received a first response; “waiting on customer” means the next move belongs to the customer; “escalated” means a named person owns the issue. Close an item only when the agreed next step has happened, not merely because someone sent an emoji.

Measure what the team can improve

At the end of each week, review:

• Number of new enquiries by channel.
• Share receiving a first response within the team’s own target.
• Oldest unresolved enquiry.
• Enquiries reassigned because the owner was unavailable.
• Common reasons a reply could not be sent.

Calculate response time using the timestamp when the enquiry arrived and the first meaningful acknowledgement. Separate business-hours time from overnight or holiday time if the distinction matters to customers. Do not use an average alone: a few very late replies can hide behind many fast ones. A median and the number outside the target often give a more useful picture.

The goal is not to create a leaderboard that shames staff. If messages arrive during a rush, change coverage or the advertised expectation. If one channel generates more work than the team can handle, reduce promotional volume or improve routing before increasing the promise.

Write customer-facing wording that matches the process

Publish only the response expectation the team has approved. Avoid “instant reply” if no one watches the inbox continuously. For out-of-hours messages, use a brief acknowledgement that explains the next staffed period and avoids implying that a person is monitoring emergencies.

Review the wording whenever opening hours, staffing or channel ownership changes. If a campaign is likely to generate a temporary spike, assign extra cover before launch and define who handles overflow.

Two-week implementation plan

Day 1: list inboxes, primary owners, backups and operating hours.
Day 2: review recent enquiries to understand realistic volumes and delays.
Day 3: agree targets and escalation cases.
Week 1: trial the queue and record misses without blaming individuals.
Week 2: adjust the target or coverage based on actual capacity.

Conclusion and next steps

A useful response-time standard protects customer trust by making ownership visible. Choose achievable targets, publish them honestly, and review misses as evidence about the process. A service-level agreement cannot guarantee a sale, but it can stop enquiries from disappearing between channels and staff shifts.

Official references

• Google Business Profile owners and managers — consult the current documentation for product-specific behaviour.
• Google Business Profile posts guidance — consult the current documentation for product-specific behaviour.