Make the first handoff visible
Persist the request, assign a responsible person, and record the next action. A receipt email can acknowledge submission, but it is not the first human response. Do not publish a response-time promise until the team can support it.
Base the next message on the current conversation
Before a follow-up, check whether the prospect replied, requested another date, received a proposal, or asked to stop. A schedule prepared yesterday may no longer be appropriate today.
The first response should ask only for missing details. Do not repeat a long qualification questionnaire when the prospect has already described the process and tools.
Treat suppression as durable state
Record requests to stop and confirmed hard bounces so a new import or project does not silently restart proactive email. Responding to an inquiry, sending a newsletter, and outbound prospecting are separate purposes.
When a provider times out, reconcile the result before sending again. A retry must not turn uncertainty into duplicate messages.
Measure contracts and receipts separately
Count valid inquiries, qualification, proposals, signed agreements, and payments as distinct occurrences. Email opens do not prove interest or authorize a stage change. No universal follow-up timer guarantees a sale; measure the operation you actually run.
