← Reports Hub 📚 Library

STOP Do Not Service List P1 · HCP Authoritative

Single source of truth. Merges HCP CSV (Do Not Service = true) + local manual overrides from titan.dns_overrides. Daniel AI + Customer 360 + campaign tools check here before any contact/dispatch.
💎
Implications (per memory rule 1)
🎯 Bucket touchedALL THREE
⚠️ ProblemCustomers flagged 'Do Not Service' in HCP have to be re-flagged in ST or they get re-engaged inadvertently via the 247 Pure-HCP campaign.
💰 $ at stakeIndirect — protects from re-burning a relationship that already cost a service truck.
✅ Action unlockedSync the DNS list from HCP into ST custom field before the Reactivation Email Campaign fires.
📊 Full bucket diagram + 4 data-integrity findings: BSP HCP Intelligence Report (📊 The Buckets · 📅 Timeline · 💸 LTV · 🔍 Why this matters · 🎯 The 4 Findings)
—
Total DNS
—
From HCP (authoritative)
—
Manual Overrides
—
Total LTV Excluded
DNSNamePhoneEmail Last ServiceLTVReason / NotesFlagged BySourceActions
Loading...
Page 1

Manually flag a customer Do Not Service

This writes to titan.dns_overrides (local). HCP-sourced DNS must be edited in HCP directly.