// DEFINITION
A recovered opportunity file is a structured export of eligible abandoned paid-search visitors prepared for CRM suppression, compliance review, intake routing, and follow-up decisions.
//Why law firms may prefer data-only recovery first
Many firms want to inspect the recovered layer before any outreach. A data-only delivery — a file or webhook drop — lets compliance, intake, and partners review the volume, geography, and suppression coverage before any activation choice is made.
//What a recovered opportunity file can include
// recovered_opportunities.schema
| record_id | Stable, deduplicated identifier |
| observed_at | Session timestamp (UTC) |
| source | Paid-search channel |
| campaign | Campaign reference |
| keyword_class | Normalized intent class |
| landing_page | Entry URL |
| funnel_step | Furthest step reached |
| geo_region | City / state / ZIP |
| recovery_status | Eligible / pending / excluded |
| intent_score | 0–100 modeled score |
| suppression_status | Clean / suppressed / hold |
| recommended_routing | CRM / mail / webhook / SFTP |
| crm_match_status | Match / no-match / conflict |
| outreach_disposition | Pending / approved / declined |
//CRM suppression and existing-client filtering
- Existing-client matches are removed before delivery.
- Prior leads in CRM are flagged or suppressed per client policy.
- Conflict checks (for legal use cases) run before any activation.
//Why the client controls follow-up decisions
TierZero structures the layer. The client decides what to do with it — internal review, intake outreach, direct mail, or no action at all. Recovery is infrastructure, not a campaign mandate.
//How this supports a 30-day leakage audit
During a 30-day audit, the recovered opportunity file is the primary artifact: a measurable, suppression-ready record of the abandoned paid-search layer beneath current spend.
// SUPPRESSION & COMPLIANCE NOTE
Recovered records are eligible, not guaranteed. All outreach decisions remain with the client and their approved workflows.