Rehash Analytics
Review V2 Rehash recovery, stage load, and pending template-performance reporting, with V1 reference below.
Rehash Analytics
Pending production: The V2 Rehash card on Business > Reports already shows windowed, location-scoped recovery metrics and stage load. The next release adds template performance by cadence stage and saved A/B variant, queue aging, disposition mix, and recovered-by-closer detail. Those additions are not available in production until their app release completes.
In V1, Analytics > Rehash opened a separate residential win-back reporting surface focused on recovery outcomes, template performance, and follow-up pressure.
If the analytics page opens with a setup warning instead of chart data, the workspace is still missing part of the latest Rehash database rollout. CE Pro now fails soft with that message instead of leaving the analytics tab on a server error.
Current V2: Rehash Report (Reports Page)
Open Business > Reports, then the Rehash card, or go straight to /reports/rehash. It has its own page and report-tab entry, and shows, for the selected range and location. If the report fails to load temporarily, select Try again to reload with the same filters; a successful load clears the previous error. Reports the current user cannot access remain hidden.
- Recovered closes: rehash cases that closed won in the range
- Recovery rate: recovered closes divided by every case that closed
(won, lost, or archived) in the range, V1's own formula
- Recovered revenue: booked value of the option the customer accepted for
each recovered close
- Unverified recovered closes: historical closes without one unambiguous
accepted proposal amount; these remain in the close count but are excluded from known recovered revenue
- Avg recovery days: average days between a case entering the queue and
closing, for cases closed in the range
- Original rep share and Closer share: the recovered revenue split by
each closed case's own frozen commission share, the exact split the commission system already locked in at close time, not recalculated here
For complete saved split bands, the displayed shares conserve every accepted cent; the closer receives any rounding remainder.
Below that, Active stage load shows how many cases are active right now in each of the rehash queue's day-based stages (Day 1 through Day 180). This is a current snapshot, not windowed by the date range, since a queue's composition is a point-in-time fact.
The pending update adds Template performance for successful cadence sends in the selected period, grouped by stage and the A or B variant saved with the message. Older sends with no saved variant appear as Unknown variant. Each group shows later replies, later won cases, verified recovered revenue, and unverified won cases. A won case's revenue is credited only to its last successful cadence send before close, so multiple earlier touches do not duplicate the recovery amount. Replies and closes must occur before the selected period ends. These are observational counts, not proof that a variant caused a recovery. The CSV export includes the same groups and their attribution note.
The pending card update also adds queue aging, disposition mix, and recovered-by-closer detail. Export the current card (rehash_report) with the page's CSV/Print controls; see Reporting Overview.
What The V1 Report Shows
The top cards summarize:
- active Rehash quotes
- recovery rate
- recovered revenue MTD
- recovered revenue YTD
- average recovery days
These numbers are based on the saved Rehash state and recovered-close attribution stored on the estimate.
Stage Load
The Active stage load panel shows how much quote value is still sitting in each active Rehash stage, along with how many of those quotes are due right now.
Use this panel to answer two questions quickly:
- Where is the active Rehash value concentrated?
- Which stage is starting to backlog?
Disposition Mix
The Disposition mix panel rolls up how quotes are entering Rehash. This is the fastest way to spot whether the office is mostly losing on price, timing, low interest, or missing the decision-maker during the appointment.
If one objection category starts to dominate, fix that issue in the field script before the queue grows larger.
Recovered By Closer
The Recovered by closer panel attributes won Rehash quotes back to the person who actually closed them. It shows:
- recovered quote count
- recovered revenue
- recovered commission dollars
This is the cleanest manager view for seeing who is actually converting win-back work.
Template Performance
The Template performance panel shows how the automated Rehash templates are actually landing:
- sends per template
- reply rate per template
- conversion rate per template
- recovered revenue tied to those converted sends
If A/B testing is enabled, Variant A and Variant B are broken out separately so managers can compare which copy gets more replies and closes.
Queue Pressure
The Queue pressure panel groups active Rehash quotes by overdue age:
- current or upcoming
- 1-3 days overdue
- 4-7 days overdue
- 8+ days overdue
Use this panel to see whether the queue is staying healthy or whether a backlog is starting to build behind the manual-touch stage.
Split Bands
The Commission split bands panel groups recovered wins by the saved Rehash timing band:
- Day 0-6
- Day 7-14
- Day 15-89
- Day 90+
This helps owners see whether recovered work is mostly closing immediately after the first follow-up or only after long-tail manager effort.
Recent Recovered Closes
The final table shows the latest recovered wins with:
- quote / customer
- timing band
- original rep share
- closer share
- recovered revenue
- recovered commission
Use it during payroll review or sales-manager check-ins when you need the exact saved split instead of a rough estimate.
Was this article helpful?
Still need help? Contact support