The field contract behind a missed-lead recovery system.
Lead Recovery OS is not a prompt pack and it is not a CRM replacement. This spec defines the data fields, handoff states, stop rules, and owner report contracts that the Stack Leak Audit checks before any implementation recommendation.
1. Capture Event
Every lead source should normalize into a single event shape before follow-up starts.
event_id source received_at channel service_type urgency contact_method
2. Route State
The system must show who owns the next action and when the first response is due.
owner dispatcher first_response_due_at assigned_at current_queue
3. Recovery Attempt
Follow-up should be visible, timed, and tied to one active lead record.
attempt_number attempted_at message_type result next_attempt_at
4. Stop Condition
The strongest recovery systems know when to stop. That protects reputation and prevents duplicate work.
booked replied not_serviceable duplicate opted_out stale
Owner report fields
The owner report is the proof layer. It should let a buyer see whether the recovery workflow produces callbacks, estimates, bookings, or clean lost reasons.
| Field | Purpose | Audit question |
|---|---|---|
source | Preserve where the lead came from. | Can the team see whether the leak came from phone, form, ads, after-hours, or repeat customer paths? |
first_response_minutes | Measure speed-to-lead. | Does the current stack expose response time without manual digging? |
estimated_value_usd | Prioritize high-ticket recovery. | Are emergency/high-value leads routed differently than low-value requests? |
status | Make follow-up state explicit. | Is the lead new, assigned, contacted, booked, lost, or stopped? |
lost_reason | Improve the system over time. | Was the lead lost to slow response, out-of-area, duplicate, price, no reply, or no capacity? |
Implementation rule
The audit recommends the smallest path that satisfies the contracts. Sometimes that is a cleanup inside the current CRM. Sometimes it is a lightweight recovery workflow. Sometimes volume justifies AI receptionist or answering-service coverage. The spec forces that decision to be evidence-based instead of platform-first.
- No client credentials needed for the first review.
- No CRM migration assumption.
- No revenue guarantee.
- Every paid setup starts from a mapped leak and a measurable owner report.