Reviving a cold furniture quote at day 30 and day 60
Give an old quote a useful reason to return to the conversation, then close the loop cleanly when the project has moved on.
The OrderPilot team·
Day 31, in this example. The walnut dining-table quote has been quiet for a month, and a vendor price-increase letter arrived last week. You could send “just checking in.” Or you could find out whether the customer still needs the table and bring them something worth answering.
Use day 30 and day 60 as suggested review points, not universal deadlines. The earlier message helps with an unfinished decision. The later one asks whether to keep the conversation open. If the customer already gave you a return date, follow that instead.
What gives the day-30 message a reason to exist?
A helpful revival starts with the last real conversation. Perhaps the customer took finish samples home, needed a doorway measurement, or was waiting for their designer. Read that note before choosing your opening.
Try this sample message when the finish was unresolved:
How did the walnut sample look beside your floor? If it felt too dark, we can compare the lighter finish before you make a decision. I can bring your table quote up to date when you're ready.
For a room still being planned:
Are the dining-room measurements settled yet? If you'd like, send the room dimensions and we can revisit the table size together. I'll confirm the current price and timing before we go ahead.
Neither needs an unsolicited discount. Start with the obstacle, then decide whether price is actually the issue. There are enough finishes named “natural” without adding another mystery to the conversation.
The be-back playbook helps identify what the customer needed to decide. Your follow-up plan should retain that detail through the quiet weeks.
What if the vendor changed the price or fabric?
Review the original quote and the store's stated terms before proposing a different price. A vendor increase alone doesn't answer what the store has already promised the customer. Have the person authorized to make that decision settle the commercial position before an associate sends an update.
If the store chooses to honor the quoted price, say so plainly. If a fresh price is needed, identify the affected item and the difference. Don't hide a change inside a new grand total. The tariff-surcharge guide covers explaining a separately identified charge when that is the actual reason.
For a discontinued fabric, show a replacement as a choice. Describe the difference in texture, color, price, and expected timing, then let the customer decide. The discontinued-fabric guide explains the catalog side; the customer conversation still needs its own care.
How do you revive the record in OrderPilot?
Find the quote through the salesperson filter and status tabs, then review the latest conversation and viewing information. A recorded view helps with context, but the unfinished decision remains the reason to write.
Update the piece and price deliberately, and send the current version from the order's email composer. Saved template prices don't automatically follow later catalog price changes.
The composer's Include what changed option lists customer-requested changes that staff applied and haven't sent. A store-initiated price increase needs your own explanation in the message. The revised-quote guide shows how to make that distinction clear.
Resending does not reset the printed validity date, which counts from creation. Read the document before sending and resolve any stale date with the OrderPilot team so the customer receives a coherent quote.
What should the day-60 message say?
Close the loop without making the customer defend a change of plans:
Would you like me to keep the dining-table quote open, or close it for now? If the room is on hold, you're welcome to return to the choices later and we'll reconfirm them.
If the customer has moved on, use your store's closing status and record the reason in the quote's activity or notes. A custom status can support that process; don't assume every store has a built-in Lost status or a required loss-reason field.
Record the useful distinction: project postponed, different size needed, bought elsewhere, or no reply after the agreed follow-up. “Not interested” often erases the very detail that would help a colleague later.
| Suggested review point | Staff action |
|---|---|
| Day 30 | Bring a useful detail; review price, fabric, and timing |
| Day 60 | Ask whether to keep the project open; record the outcome |
For the next live conversation, return to the day-by-day follow-up plan with the customer's actual decision and timing attached.
Revive the project, not just the old email.