Set enquiry response capacity before buying more attention

Count the work after an enquiry arrives

A new request creates more than an inbox notification. Someone may need to review details, clarify scope, prepare a quote, schedule a call and record the next action. List the steps for your main service and estimate time separately.

Include requests that do not become jobs. Screening and explaining an unsuitable request still take time. Ignoring that work makes your response capacity look larger than it is.

Map real coverage hours

Write the periods when you can respond while also delivering existing work. Identify who monitors forms, phone messages and email. If one person covers everything, distinguish response time from time already committed to visits or production.

Use an honest expectation such as reply during the next working day when that matches the process. Do not promise instant answers because a website form is available all day.

Calculate an initial handling limit

Divide the available response minutes by an estimated average handling time to get an initial planning limit. Leave room for unusually complex requests and existing customer questions. Label the result an estimate and update it with observed work.

A mathematical capacity is not a reason to fill every minute. Interruptions, unanswered clarification questions and multiple contact attempts can make daily workload uneven.

Create an overflow route

Decide what happens when the main responder is unavailable or the queue exceeds the limit. Assign a backup, reduce acquisition or send a clear acknowledgement with a realistic next response time. Ensure that acknowledgement does not falsely imply a quote or appointment is confirmed.

Keep one place where each enquiry has an owner and next action. Multiple inboxes without a shared record can create duplicate replies and missed requests.

Connect marketing changes to coverage

Before starting a campaign, check that the advertised contact methods route to the assigned responder. Test a form, call and reply path using clearly identified test details. Verify useful delivery rather than counting a click as a handled enquiry.

Set a review trigger for aged unanswered requests. If coverage fails, repair the process and adjust acquisition before spending more to create the same backlog.

Measure useful response, not just speed

Track the time to a meaningful first answer, requests awaiting clarification and overdue follow-ups. An automated receipt may be quick while the customer's actual question remains unanswered. Review a sample of responses for usefulness.

Interpret the results alongside daily workload. A small burst may expose a scheduling problem; it does not by itself show that the service lacks demand or that every late response caused a lost sale.

Illustrative solo-owner response limit

A hypothetical owner has 90 minutes each weekday for new requests. Estimated review, first answer and recordkeeping take 15 minutes per enquiry. The simple limit is six, but the owner starts with a planning ceiling of four to leave room for complex cases and follow-up.

A campaign is reviewed when two requests remain unanswered beyond the promised working-day window. The owner reduces acquisition and restores coverage. These numbers illustrate workload planning; they are not a benchmark for response speed or a forecast of campaign results.

Questions about this task