What happens after you miss an inquiry?

01 / Respond

Set a prompt, honest response target

Acknowledge an inquiry as soon as the team can, even when a complete answer needs more time. When possible, aim for a human response within one business hour. That is an operating target, not a promise that every request can be resolved in an hour. Harvard Business Review's 2011 audit found that 37% of 2,241 U.S. companies answered a test web lead within an hour; a separate lead study cited in the article found that companies trying within an hour were nearly seven times as likely to qualify a lead as those waiting at least another hour. The two findings describe different study samples and should not be treated as a guaranteed outcome. (Oldroyd, McElheran & Elkington, 2011)

For planning an after-hours queue, 8 a.m.–6 p.m. local time can be a sample staffing window only. Replace it with the business's actual hours and promised callback timing; it is not a universal schedule.

02 / Continue

Choose the next touch by urgency and context

Handle urgent service inquiries the same day or faster, using the business's actual coverage and escalation rules. After sending an estimate, answering a question, or leaving a voicemail, set a next step within 1–2 business days when a useful follow-up is still needed. Those are practical service targets, not universal response-rate findings.

• Make each reminder useful. It should advance an agreed next step, supply missing information, or answer a likely question. Skip a reminder that only says “just checking in.”
• Keep the sequence bounded. One purposeful reminder is a sensible default when the person has not replied and there is a real open question.
• Stop at a clear signal. End follow-up after a decline, completed interaction, opt-out, or a reasonable period of inactivity based on the service and the person's stated timing.

A Yesware analysis of more than 200,000 sales-rep and account-executive email data points from one quarter reported 75% opened and 42% replied to within an hour. Those figures describe that sales-email sample, not inbound inquiry handling or an ideal response target for every business. (Yesware, publication date not stated)

03 / Write

Use A.C.T. and match the trigger

Use A.C.T. as a practical writing pattern: Acknowledge receipt, Clarify what happens next and when, then Transition to one clear action. Adapt these short SMS examples to the business's actual hours and response promise.

Character counts include the bracketed placeholders as shown. Replace each one before use and recount if the business name or timing makes the text longer.

04 / Route

Define fit before deciding who gets priority

Start by writing an ideal customer profile (ICP) in terms of the problems the business can solve, its service area, delivery capacity, and other criteria it has actually approved. Then ask a few conversational questions across BANT: Need (what problem needs solving?), Budget (is there an approved budget or range?), Authority (who will decide?), and Timeline (when is a solution needed?). These are qualification dimensions, not a script every prospect must complete. (Salesforce, BANT guide)

Consider urgency separately from fit. A strong-fit person with an immediate need deserves same-day human attention under the team's coverage rules. An early-stage inquiry may need a helpful explanation and a later check-in. A poor-fit request should get a courteous, appropriate alternative when one is known, rather than an automated sales chase.

Booking and resource links here are configurable examples, not existing Rookmason product features. Use only live destinations the business has chosen.

05 / Track

Make the handoff visible to the whole team

Use a connected CRM or another shared tracking process so the next response does not depend on someone remembering. For every inquiry, keep a compact record that answers “where did it come from, what does the person need, and who acts next?”

Record

Inquiry source, service requested, city, customer need, and time received.

Assign

A responsible person, current status, next action, and due time.

Review

Response times, unassigned inquiries, overdue next actions, and recovery or booking outcomes.

Response time, assignment coverage, and overdue actions are process measures. Replies, recovered conversations, and bookings are outcomes to observe. Neither category is a promised revenue or conversion result; use the team's own records to see whether the workflow is helping.