Ren Álvarez sees a notification beside a replacement quote. "They've viewed the proposal. We can count that job." When you're trying to keep two install crews scheduled, a sign of interest feels useful. A viewed proposal is not a booking.
Ren is an illustrative owner, not a client case study. Her nine-technician business has already supplied the blog's two-screen problem: 94 June inquiries on the marketing report and nine idle install-crew days on the calendar.
Follow-up creates another place to confuse activity with work. A proposal sent, opened, discussed, or accepted can still leave the installation date unresolved.
Ren needs something more useful than another reminder to call the customer. She needs to know what decision is waiting, who should help with it, and which future dates the answer could actually fill.
What decision is the homeowner trying to make?
At the consultation, ask what the customer needs to decide and when. Someone replacing a failed system now has a different timeline from someone comparing options for next season.
Record the unresolved question in plain language: comparing installation scopes, checking payment information, waiting for another household decision-maker, choosing a date, or postponing the project. "Follow up" is a task label. "Explain the ductwork difference before Thursday's decision" tells a person what to do.
Make the proposal useful before sending it. ENERGY STAR's contractor-hiring guidance encourages homeowners to compare written, itemized estimates, including cost, efficiency, and warranties. Supply a clear scope and supported information rather than expecting a reminder sequence to repair a vague quote.
If the technical recommendation changes, involve the person responsible for the assessment. Do not let an automated sales message invent a new system recommendation or suggest an unnecessary replacement.
Use what homeowners look for when hiring an HVAC company to check whether the next contact supplies clarity and trust. A repeated "ready to book?" rarely answers an unresolved scope question.
Ren can see why the viewed notification is incomplete. It says nothing about which comparison the customer is making. Her next useful question is the one she should have recorded before the proposal left the office.
Who owns the next contact, and when should it happen?
Give each open proposal one named owner and a backup. The owner might be the estimator, comfort adviser, or another trained employee who can explain the scope and coordinate with dispatch.
At the end of the conversation, ask: "Would a follow-up be useful? Which channel and day work for you?" Record that preference and the reason for the contact. Honor a request to pause or stop.
A sample routine could be delivery confirmation on day zero, an agreed clarification on day two, and a decision check on day seven. Those are example dates, not a rule for every homeowner. If the customer asks for next Thursday, use next Thursday. If urgent circumstances need a faster answer, agree that directly.
Keep the task attached to the proposal. Record the due date, last meaningful contact, unresolved question, next action, and current outcome. When ownership changes, transfer the notes instead of making the customer repeat the story.
Before an automated reminder runs, check whether someone already spoke with the customer. Stop a generic sequence when the next step has changed. A call from the estimator and a contradictory text from the office make the company look less coordinated.
For service and install work, the time horizon matters. A planned replacement can need a considered discussion. An urgent repair request needs the appropriate service response, not a week-long replacement sequence.
Ren puts an employee's name next to the next contact. The proposal now has someone responsible for answering a question, rather than several people responsible for sending reminders.
What can you actually say after sending the proposal?
Use the customer's agreed channel. These messages are examples to adapt to the actual discussion, not a sequence to send indiscriminately.
Confirm delivery and the next step:
"Hi [Name], it's [Rep] from [Company]. I've sent proposal [reference] for the work we discussed. Can you open the scope and price pages? Our next check-in is [agreed day]. If anything is missing or unclear before then, reply here and I'll help."
Help with the comparison:
"Hi [Name], you mentioned comparing [specific issue]. Our proposal includes [actual included work]; [specific item] is separate or excluded. Would a brief explanation or a revised written comparison help? I can speak at [available time], or we can use your preferred time."
Close or pause the loop:
"Hi [Name], this is the check-in we agreed for [day]. Would you like help with the next step, a later follow-up, or for us to close the proposal for now? If you've chosen another option, thank you for considering us. Let me know what works for you."
When payment information is the unresolved issue, supply the actual financing and proposal options, with full terms and appropriate scope. Do not treat a payment question as permission to enlarge the project.
When the customer wants dates, check today's board first: "I can confirm the current install windows with dispatch. No appointment is reserved until we agree and confirm the booking." If your business offers a genuine hold, explain its actual conditions.
Ren does not need a more dramatic final message. She needs the one that addresses the real decision. The customer can say yes, no, or later without being pushed by an invented deadline.
Why aren't six viewed proposals six bookings?
Use a separate hypothetical intake cohort to keep the stages clear. These numbers are not additional June results for Ren. Follow twenty eligible install inquiries received during days 1–30 through a day-90 cutoff.
| Stage or signal | Count | What the count means |
|---|---|---|
| Eligible install inquiries | 20 | Distinct requests that fit the business |
| Completed consultations | 12 | Visits or consultations actually completed |
| Proposals issued | 8 | Written project offers delivered |
| Recorded proposal views | 6 | Optional interest signal, not acceptance |
| Accepted projects | 4 | Customer accepted the project, whether dated yet or not |
| Booked installations | 3 | Installation dates agreed and saved |
| Completed installations | 2 | Booked work actually performed |
The counts are stages and overlapping signals, not numbers to add together. Six recorded views do not create six appointments.
The example leaves eight inquiries without a completed consultation and four completed consultations without a proposal. Of the eight proposals, four are not accepted at the cutoff. Of four accepted projects, one has no confirmed date. Of three bookings, one is still scheduled and two are complete.
That is a set of different next actions. Find out whether the undated acceptance needs customer timing, equipment confirmation, or an office handoff. Review why the other proposals have not advanced without labeling every case unqualified.
Proposal-to-acceptance is 4 ÷ 8 = 50%. Inquiry-to-booking is 3 ÷ 20 = 15%. Neither is a promised outcome from better follow-up. It is the arithmetic of this small example.
Ren leaves the viewed count in the report as a signal. She puts only the three actual bookings on the schedule. The six notification marks no longer get to stand in for available work.
Which future install windows can the pipeline actually fill?
Start with your team's true weekly capacity, using crew-days rather than a general count of technicians.
In another explicit planning example, Ren's two dedicated crews working five days provide ten gross crew-days for a future week. Suppose reserve and other known constraints reduce that to eight usable crew-days. Five are already committed. Three remain.
If the relevant installations each need 1.5 crew-days, 3 ÷ 1.5 leaves room for two installs. A crew-day means one crew working one day. It is not one technician-day.
Review the open pipeline against those exact windows. An accepted project waiting for its date may fill one opening once the customer and office confirm it. An unresolved proposal for a homeowner who wants work next spring does not fill next month's gap.
Keep committed work separate from an assumption-based forecast. In the preceding small cohort, three bookings came from eight proposals, or 37.5%. If no relevant pipeline existed and you assumed that same rate, two bookings would require 2 ÷ 0.375 = 5.33, rounded up to about six proposals for planning. Six proposals would not guarantee two bookings.
Eight proposals are too little evidence to turn into a dependable universal rate. Use larger comparable cohorts, current availability, and the customer's stated timing. How many leads your company needs starts with the capacity gap, but you must subtract the likely contribution of relevant existing opportunities before buying more.
Ren can now distinguish a crew opening from a proposal that might fill it. She can also see why calling for more leads while an accepted project waits for a date is the wrong first repair.
When should the follow-up stop or change?
Stop the sales sequence when the customer books, declines, asks for no further contact, or chooses another company. Pause when they request a later date, and record the agreed next contact rather than quietly restarting the sequence.
If the final agreed check-in receives no answer, close or pause the active task under your documented process. Keep the record without making silence permission for endless reminders. A later customer reply can reopen the conversation.
Change the route when the need changes. A homeowner now requesting repair needs service intake. A homeowner with a scope concern needs a technical answer. A new installation date requires a fresh availability check. Do not keep sending the old proposal message after the underlying question has changed.
Use inquiry-to-invoice tracking to preserve the record, while leads don't matter if they don't book supplies the operating test. Follow-up is useful when it helps a suitable decision become deliverable work, not simply when it generates more messages.
An open proposal needs a useful next action. A calendar needs a confirmed date.
In Ren's illustrative example, the two screens show different things again. One has open decisions, with owners and agreed next steps. The other has real installation commitments.
She no longer needs to make the viewed column look like the board. She needs the next conversation to help the right project earn a place on it.