Small business outsourcing workflow guide
Set a two-touch rule for following up a quiet customer
A two-touch follow-up rule that gives a small-business assistant a clear reason, a fixed interval, and a stopping point.

Define what quiet means
A customer is quiet when the business has sent a question, a quote, or a promised update and the customer has not replied within the agreed window. Define that window by the type of request rather than by how the assistant feels. A quote may need three business days, while a delivery update may need one. Write the rule where the queue can see it.
Record the date of the last outbound message, the channel it used, and the person who sent it. A customer who replied in a different channel should not be treated as silent. Check the shared inbox and the phone notes before sending a follow-up. A mistaken follow-up makes the business look disorganized and wastes the customer's time.
Choose the two touchpoints
The first touch should repeat the question or the update in one short message and make the next step easy for the customer. The second touch should offer a clear choice, such as proceeding with the current quote, changing the delivery date, or closing the request for now. Space the touches by the interval in the rule and use the same channel unless the customer asked for another. Two touches are enough for most small-business requests.
Do not use the two touches to repeat the same reminder in the same words. Each touch should add a useful detail, such as a deadline, a delivery date, or the name of the person who can answer a question. The assistant should not invent urgency that the business has not approved. A calm, specific message is more likely to get a reply.
Write the message the assistant may send
Provide two approved message templates, one for a question and one for a quote. Leave a small set of fields the assistant may change, such as the customer name, the item, and the date. Do not let the assistant promise a discount, a refund, or a delivery date that is not in the record. The template should sound like the business, not like a collection notice.
Include a line that tells the customer what happens if the business does not hear back. For a quote, that might mean the price is held until a stated date. For a request, it might mean the file is closed and can be reopened later. The customer should never be surprised by the next step.
Record the promise and the date
Every follow-up should leave a record of what the business promised, when it promised it, and what happens next. Record the customer, the request, the owner, the last contact, and the next touch date. If the customer asks for more time, update the date and the reason. A promise without a date is hard to keep and harder to review.
Use the same field for the next action that the queue uses for other work, so the follow-up appears in the daily list. The assistant should be able to see the follow-up without checking a private reminder or a personal calendar. If the customer replies, close the follow-up and record the outcome and the date. The record should show whether the rule worked, not only that a message was sent.
Decide when to stop
Stop after the second touch unless the customer has asked for more contact or the request is still active. Record the stop and the reason so another person does not restart the sequence by accident. A stopped request can be reopened when the customer returns. Continuing to send messages after a clear stop damages trust.
If the request involves a safety issue, a legal deadline, or a large payment, the rule should route it to the owner instead of stopping. Name the exceptions in the written rule and keep the list short. The assistant should not decide that a legal letter is just a quiet customer. Escalation is part of the stopping rule.
Hand the conversation back to the owner
When a customer replies with a question the assistant cannot answer, hand the conversation back with the full context. Include the last message, the promise, the date, and the specific decision the owner needs to make. Do not forward a long thread without a summary. The owner should be able to reply without reading the whole history.
Record the handoff time and the owner who received it, and confirm that the owner has seen the summary. If the owner does not respond within the agreed window, escalate once to the backup. The customer should not experience a second silence after finally replying. A clean handoff is part of the follow-up rule, not an exception to it.
Review the replies monthly
Once a month, count how many follow-ups received a reply, how many were closed, and how many needed the owner. Read a sample of the messages and check whether they matched the approved templates and the recorded promise. Ask the assistant which template gets the most questions. The review should improve the message, not just the count.
Compare the reply rate with the age of the request and the channel. A low reply rate on one channel may point to a deliverability or timing problem. Change one variable at a time and keep the next month's sample comparable. A follow-up rule is useful only when the business can see whether it is working.
Sources and next steps
- Federal Trade Commission, business guidance
- U.S. Small Business Administration, manage your business
- U.S. Government Accountability Office, internal control standards
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.
Related guides
Build a supplier onboarding packet that survives the first invoice
A short supplier packet that captures the payment details, scope, and review owner before the first invoice reaches the queue.
Review shared inbox tags before the quarterly cleanup
A quarterly tag review that removes stale labels without losing the work, the ownership, or the reporting the team depends on.