One estimate + permitted contact history. Everything else stayed outside the request.
Field Runtime / simple demonstration
Opportunity Engine
The AI produced an answer. Field Runtime made it safe, accountable, and measurable. See the difference in three simple steps.
DETERMINISTIC REPLAYSynthetic data · no live provider calls
THE SCENARIO
An $18,400 estimate has been sitting untouched for 19 days.
Cascade Heating & Air has hundreds of leads and estimates across its CRM, inbox, calendar, and accounting system. The Martinez family's HVAC replacement estimate is valuable, stale, and at risk of disappearing.
YOUR JOB Decide whether this opportunity deserves action and what the salesperson should do next.
Follow the three steps. Use the large orange button to move forward.
BEFORE / ONE MODEL, ONE ANSWER
The answer sounds useful—but creates risk.
Without Field Runtime, this is what the company might do:
“No action. The estimate remains buried until the customer chooses another contractor.”
×No deterministic stale-estimate detection exists.
×The team cannot see which follow-up is worth doing first.
×Revenue outcomes never improve the next recommendation.
NEXT STEP Ask Field Runtime to review the answer.
How Field Runtime did it
The context, intelligence, record, and outcome behind the story.
Route: Local rules → cache → specialist → frontier. Failover: Frontier draft → specialist template → human-written follow-up.
Provider: Approved drafting model / template failover. Cost: $0.72. Authority: Assigned salesperson. Provenance: CRM · inbox · calendar · estimate v2.
Accepted outcome: Yes. Cost per accepted outcome: $0.72. Pipeline recovered: $18,400.