“Not now” isn’t always
the end of the story.
A prospect asked for an estimate. Your team did the work. Then the conversation stopped. Sometimes the project was delayed; sometimes a question went unanswered; sometimes the customer chose another business. Your CRM may not tell you which.
Rehash is a deliberate way to revisit suitable opportunities with a relevant question. It gives your team a chance to learn whether the project is still active, rather than treating every quiet record as lost—or contacting everyone again.
For home services, that may mean unaccepted estimates. For an agency, proposals awaiting a decision. For a professional-services firm, a discovery conversation that never progressed. Each group needs its own reason for follow-up.
Reopen the conversation.
Keep the context.
- Current status
- Estimate not accepted
- Before contact
- Owner confirms eligibility and permitted channel
- Open question
- Is the project still being considered?
Hi Morgan, are you still considering the replacement project we discussed? If you’d like to revisit it, we can arrange a time to answer questions and confirm whether the estimate needs updating.
We put it on hold. Could someone explain the options again?
Pending attempts stop. The owner receives the original estimate, the new question, and a task to arrange the conversation. The opportunity is not marked sold.
Use the actual service and inquiry history. Do not invent a discount, imply a personal review that did not happen, or suggest an old price is still valid. For text or AI calls, the approved contact channel and message requirements belong in the scope.
The best list is
a list you can explain.
Start with a small, defined group: for example, estimates in a chosen date range with no recorded decision. Compare that group with current CRM activity before anyone is contacted. A month-old export cannot tell you who booked this morning.
| Record condition | What happens next |
|---|---|
| Still relevant; contact allowed; no active conversation | Candidate for review and a bounded pilot. |
| Already booked, completed, or actively discussing the work | Exclude from the sequence; preserve the existing owner’s conversation. |
| Opt-out, wrong number, or no required contact permission | Do not contact through the proposed channel. |
| Conflicting identities, unclear status, or unresolved complaint | Hold for staff review. Never guess the match. |
| Reply arrives after selection | Recheck current state and stop the queued attempt. |
Each record should have one clear disposition: selected, excluded, or needing review. That makes the list auditable and gives your team a chance to catch a bad rule before it reaches customers.
Start small.
Follow the actual outcome.
First run the proposed selection without sending messages. Review the included records and exclusions. Then agree a limited pilot, a contact window, an attempt cap, and a person who can pause it. The right size depends on the team and the quality of the records.
Review
Check current records and preview the proposed contact.
Reconnect
Use the agreed channel and recheck eligibility before each attempt.
Hand over
Pause on a reply and give a named person the next action.
Your existing CRM owns the opportunity. n8n, Make, or Zapier may coordinate the workflow. A voice platform such as Retell is considered only when AI calls fit the use case. Provider access and channel requirements must be verified for the actual account.
A reply is useful. A delivery receipt is not revenue.
Track attempted contact, delivered messages, replies, qualified conversations, confirmed appointments, and paid work separately. Attribute later sales carefully and deduct the cost of software, usage, and staff time. This guide makes no response-rate or recovered-revenue claim.
If a message is accepted but a CRM update fails, repair the record using the existing attempt reference. Do not restart the outreach just to make the CRM look complete.
Scope the data work.
Then the follow-up.
A clean, single-source workflow is different from years of duplicated contacts, conflicting estimates, and multiple sales pipelines. Data cleanup, matching rules, number of channels, and AI voice determine how much work is involved.
Complex cleanup, migrations, and voice implementations need their own quote. These ranges are GoodHandoff’s planning prices, not a promise to recover an entire database for the entry fee.
You own the delivered workflows and control the provider accounts. GoodHandoff sets up the agreed systems and compares the operating cost before choosing tools. You pay providers directly for subscriptions and usage; implementation and optional support are separate.