Rehash Queue

The Rehash queue is the residential win-back workspace for unsold quotes. It is live in Clean Estimate V2 at /rehash, ported closely from V1's own /admin/rehash workflow: the same sequence stages, disposition codes, discount guardrails, and Red Line room badges. Rehash in the sidebar shows quotes saved with an active unsold disposition as they move through the follow-up sequence. This article uses V1's terms and workflow as the baseline and calls out the specific places V2 behaves differently.

The web queue also adapts to smaller browser widths. This is a responsive web behavior, not a native-mobile workspace.

What Rehash Requires

Rehash is only available when all three of these are true:

• Red Line is enabled in Pricing Manager
• Enable Rehash Department is turned on in the Red Line settings
• The logged-in teammate has Rehash access turned on

If any of those are off, the Rehash page stays hidden from the sidebar and the analytics page shows a disabled-state message instead of queue data.

Direct visits to the Rehash route follow that same access model cleanly. If the route is available to your role and your Rehash access toggle is on, the queue opens normally instead of bouncing back to the dashboard.

In Clean Estimate V2, Rehash access is a per-teammate toggle on the member's Permissions tab under Settings > Team, not one of the versioned permission flags. Any teammate with Manage team access to that member can turn it on or off; it is not restricted to an all-location owner the way most individual permission grants are. A change applies on the teammate's next request. See Team Management.

Required Dispositions

Residential quotes now capture a Rehash disposition as part of the save flow. The main options are:

• HOT
• WARM
• PRICE
• TIMING
• COLD
• NO CONTACT
• DEAD
• SOLD

These notes are required before save:

• HOT -- objection details
• PRICE -- target price or pricing note
• TIMING -- timing details
• DEAD -- do-not-contact reason

Those saved notes carry into the queue so the sales manager sees the original objection before making the next touch.

Sequence Stages

The built-in sequence moves through these stages:

• Day 1
• Day 3
• Day 7
• Day 14
• Day 21
• Day 30
• Day 60
• Day 90
• Day 180

Day 7 is the main manual-touch stage. The queue page opens with that stage selected by default so the manager can work the human follow-ups first.

The automated touches use the saved Rehash templates behind the scenes. CE Pro seeds those templates for the workspace automatically, then sends or suppresses them based on the saved quote context.

If Enable Rehash template A/B testing is turned on in Pricing Manager, CE Pro alternates between the seeded Variant A and Variant B templates automatically on a per-template basis.

Pending production: The next release records the selected A or B variant with each outbound cadence message. A retry keeps that recorded choice even if the pricing setting changes later. Queued or failed Day 21 and Day 90 messages still obey the current offer and Red Line gates; a previously sent message may recover its recorded outcome without a second send. Customer message delivery remains paused under the current production boundary.

In Clean Estimate V2, every automated cadence stage sends by email today. Day 3, 21, and 90 carry over the same copy V1 sent by SMS, as the email body, because V2 does not yet have a separate SMS channel wired into the Rehash cadence. Day 180 has no V1 template to port at all (V1 never auto-sends there), so it uses its own plainly-generic fallback copy. The assigned template label does not yet show in the V2 drawer or a message history, since neither exists there today (see Working the Queue below); the discount gate that decides whether day 21/90 promise a discount still applies before that copy is chosen.

Discount Guardrails

Day 21 and Day 90 can include the built-in win-back offers, but they still respect Red Line:

• Day 21 uses the optional 10% auto-discount message
• Day 90 uses the optional 15% final-offer message

If either offer would push any service below its saved Red Line floor, CE Pro suppresses that automated offer instead of sending a below-floor discount by accident.

Working The Queue

The top of the Rehash page shows:

• active quote count
• active pipeline value
• manual touches due
• recovered revenue MTD
• recovered revenue YTD
• recovered-close count that could not be tied to one verified accepted proposal amount
• recent conversion rate

Below that, the stage pills let you switch between the live active stages. The table gives the fastest day-to-day tools:

• Text
• Call
• Email
• Touched
• Re-Quote
• Dead

Each queue row now also shows a Red Line room badge based on the saved residential service totals versus the saved Red Line floors on that quote:

• Green room badge -- the quote is still above floor and has discount room left
• Amber at floor badge -- the quote is already sitting on the floor
• Red below floor badge -- the quote is already below floor and should be treated like an override case

Opening a row slides out the Rehash detail drawer with:

• saved disposition and notes
• a quote summary card with each service's list price, current quoted price, and saved Red Line floor
• parent quote link
• disposition and manual-touch controls (Text, Call, Email, Touched, Re-Quote, Dead)

When you switch between cases, the drawer keeps the displayed case and its actions together while the next case loads. Actions stay unavailable until the selected case's details are ready, so a delayed response cannot apply a touch or re-quote to a different case than the one on screen.

The drawer keeps the List, Red Line, Room, and Quoted numbers side by side so it is easy to see how much safe discount room is left before the floor.

V2 note: the Quoted column renders as a read-only value in Clean Estimate V2, the same as List, Red Line, and Room. V1's inline quoted-price editing is not built here; a line pointing at the full quote editor is shown instead for an actual price change. V2's drawer also does not show customer contact info, suggested SMS/email drafts, assigned template labels, or message history -- none of those have a V2 data source yet (no message or call table feeds Rehash), so they are left out rather than shown empty or faked. Call logging is likewise not part of the V2 drawer; use the separate Phone workspace for call history.

If the quote is a proposal package, maintenance-plan quote, or another shape that depends on a fuller pricing graph, the same card stays visible in a read-only state and points the manager to the full quote editor instead of a partial or unavailable edit path.

The Rehash popup is now also more fault-tolerant around older or imperfect data. If a saved quote has a broken parent-estimate link, malformed old rep ids, a bad Rehash template row, or an older workspace that is still missing legacy estimate pricing columns like minimum_adjustment or taxable_amount, the drawer still opens on the quote summary instead of failing the entire request.

If the page opens with a setup warning instead of queue data, the workspace is still missing the Rehash estimate/disposition schema rollout itself. Older template storage no longer blocks the queue by itself, CE Pro falls back to the built-in Rehash message copy when needed, and the setup warning now names the exact missing Rehash schema fields instead of collapsing unrelated schema errors into the same generic rollout message.

Re-Quote Flow

The Re-Quote action duplicates the selected estimate and links the new quote back to the original Rehash chain. That keeps the original quote record intact while letting the office work a revised scope or updated pricing cleanly. If the customer accepts an earlier proposal after a newer working quote exists, the recovered close uses the option the customer actually accepted; the newer working quote remains available for follow-up.

Once a proposal closes, CE Pro saves the recovered-close attribution and uses the accepted proposal option's booked total for recovered-revenue reporting.

Recovered-Close Attribution

Recovered residential closes save a Rehash commission split based on how long it took to close. The default bands, matching V1's fixed values:

• 0-6 days -- original rep keeps the full commission
• 7-14 days -- 50 / 50 split
• 15-89 days -- 25 / 75 split toward the closer
• 90+ days -- closer takes the full commission

That saved attribution shows up in:

• the estimate detail page
• the Rehash analytics page
• the rep's own Commissions/earnings view, labeled as a split recovered-close payout so a lower commission on that job is not mistaken for an error

This makes it easier to review recovered revenue and compensation without rebuilding the timeline manually after the close.

Recovered revenue is based on the option the customer accepted in the proposal revision that won. Older closes are included in known recovered revenue only when one accepted proposal and amount can be verified unambiguously. If the history is missing that proof or contains more than one possible accepted proposal, the report includes the close in its aggregate Unverified count and leaves its amount out of known recovered revenue; the close count and existing attribution records remain available. It is not shown as a made-up $0 sale or as a per-close label in the drawer.

The closer is whoever most recently touched or re-quoted the case; if nobody did, it falls back to whoever the case was assigned to, then to the estimate's assigned rep. If the original rep and the closer are the same person, or either is missing, the original rep's side of the split pays 0 and the closer side is not artificially inflated to fill the gap -- there is exactly one payee in that case, not two.

Editable commission bands (Clean Estimate V2)

V1 never had an editor for these bands; they were fixed constants. In Clean Estimate V2, an owner or manager with Manage team and all-location access can edit them at Settings > Rehash commission bands: four rows, day 0 fixed on the first row, the last row always open-ended, with the three day boundaries between rows and each row's Original rep share percentage editable. The bands stay structurally valid by construction -- always four rows, always contiguous, and each row's two shares always sum to 100%.

A band edit only affects cases that close after the change. The split is resolved from the organization's saved bands at the moment a recovered close is finalized and then frozen on that case permanently; editing the bands later never rewrites an already-closed case's saved split. The same-person/missing-party rule above is a fixed business rule, not an editable percentage.