Hard rule
A human can correct evidence, but cannot create a billable opportunity without source-system proof.
Trust architecture
Audit the machine before paying the bonus fee
RoofPipeAI trust is not a soft promise. Billing depends on approval controls, suppression, unsubscribe, source evidence, CRM/calendar/email trace, duplicate detection, exclusion windows, dispute workflow, reversal workflow, and human correction.
Approval controls
High-risk messages stay in approval. Humans can approve, reject, edit, or exclude before send.
Suppression and unsubscribe
Suppression, unsubscribe, do-not-contact, and sender boundaries are operating controls, not optional settings.
Source-system evidence
Calendar, campaign, contact/account, CRM, email, and attendance traces decide whether a fee can pass.
Duplicate and exclusion review
Duplicates, residential-only leads, internal tests, missing records, and cancellations are excluded or disputed.
Dispute and reversal workflow
Booked and attended events remain reviewable. Failed events become pending, excluded, or reversed.
No manual fee creation
A human can correct evidence, but cannot create a billable opportunity without source-system proof.
Control matrix
What the contractor controls and what RoofPipeAI must prove
| Control | Contractor can do | RoofPipeAI must prove |
|---|---|---|
| Outreach approval | Approve, reject, edit, or exclude | Draft, campaign source, sender trace |
| Suppression | Suppress domains, contacts, owners, markets | Suppression respected before send |
| Unsubscribe | Keep unsubscribed contacts out of outreach | Unsubscribe and suppression trace |
| Meeting qualification | Dispute, correct, exclude | Calendar, contact, CRM, and RoofPipeAI campaign evidence |
| Attended status | Confirm, dispute, or reverse | Attendance evidence and no exclusion |
| Billing ledger | Review booked and attended events | Clean ledger with fee class and dispute window |
Allowed integration categories only
The current site lists generic systems only. Roofing-specific connector support is not claimed unless implemented.