About this agent
Ships in the FieldCamp agent marketplace — because a rejected estimate is a negotiation that hasn't started, not a deal that's dead.
Most rejected estimates die of silence, not rejection: the customer clicks decline, the shop shrugs, and nobody asks the only question that matters — what would have made it a yes? The answer is usually guessable from the estimate itself: a scary single line item, a scope mismatch, a price that needed options instead of a number.
The assistant does the guessing rigorously, the moment the rejection lands. It compares the dead estimate against your similar won deals — where was this one heavier, vaguer, less flexible — and names the likely objection with a proposed fix: tiered options, a split scope, a reframed line item, or the honest conclusion that this customer was shopping on price you shouldn't match. Your counter goes out while the customer is still in the market.
What it actually does
Trigger: Estimate rejected
- 1
Catches the rejection
estimate_rejectedFires on the decline, with the estimate and any reason the customer gave.
- 2
Compares against your wins
compare_won_dealsSimilar accepted estimates — where this one was heavier, vaguer, or less flexible.
- 3
Names the likely objection
diagnose_objectionPrice, scope, timing, or trust — with the evidence for the diagnosis.
- 4
Proposes the counter
propose_revisionConcrete revision strategy — tiers, split scope, reframed items — for your call.
What you get
Every rejection answered with a diagnosis and a proposed counter — sent while the customer is still deciding, not after they've hired someone.
A run, as you’d see it
Agent runs land on a timeline — what fired, what the agent found, and the action waiting for a human. This is that screen.
Estimate rejected
#EST-1190 · $4,800 fence replacement
Details
Diagnosis
Price shock — single line item
Summary
Rejected without comment 2 days after viewing twice. Versus similar won deals, this quote bundled everything into one $4,800 line. Proposed: three-tier revision (repair $1,900 / replace $4,200 / replace+gate $5,100) — your won deals at this size are tiered 80% of the time.
Proposes only — the revised estimate is drafted for your review, and nothing reaches the customer without you.
By trade
Same agent, configured to how your vertical actually works.
Repair-versus-replace tiering is the most common winning counter.
Phased-scope proposals revive big-ticket rejections more than discounts do.
Questions, answered
How does it know why the customer rejected?
When a reason is given, it uses it; when it's silence, it diagnoses from evidence — view patterns, comparison against your similar won deals, and the estimate's own structure. The diagnosis states its confidence and reasoning either way.
Won't a quick counter look desperate?
A discount would. A restructure — options where there was one number, phases where there was one lump — reads as listening. The assistant proposes structure changes first and flags when walking away is the right answer.
Does it send the revision automatically?
Never. It drafts the strategy and the revised estimate for your review; you decide what goes out and when.