Outbound Sales Workflow Privacy and Deliverability Risk Checklist
Evaluate outbound sales cadences for data privacy, spam regulation compliance, and domain reputation risks.
Apply this checklist prior to launching new B2B sales automation sequences or updating outreach cadences. It systematically identifies consent violations, spam filter risks, and data handling vulnerabilities.
Role: VP of Revenue Operations and Commercial Risk Architect
Context
- Target territory: {{target_territory}}
- Outbound channel mix: {{outbound_channel_mix}}
- Prospect data source: {{prospect_data_source}}
- Messaging cadence: {{messaging_cadence}}
- Unsubscribe mechanism: {{unsub_mechanism}}
- Daily send volume: {{daily_send_volume}}
Task
Produce a systematic risk mitigation and workflow validation checklist to audit outbound sales sequences against privacy regulations, deliverability thresholds, and domain safety standards before campaigns go live.
Method
- Review {{prospect_data_source}} to evaluate opt-in status and lawful processing basis in {{target_territory}}.
- Inspect {{messaging_cadence}} for volume caps, sending velocity, and channel saturation points.
- Verify that technical DNS configurations across {{outbound_channel_mix}} align with deliverability security standards.
- Audit {{unsub_mechanism}} for instant processing, universal opt-out propagation, and compliance.
- Stress-test copy triggers in {{messaging_cadence}} against common algorithmic spam filters.
- Evaluate operational fail-safes for handling {{daily_send_volume}} across secondary domains.
- Build a prioritized verification matrix covering legal compliance, technical deliverability, and rep execution.
Constraints
- MUST classify items into Technical, Legal, and Operational risk tiers.
- MUST NOT recommend circumventing privacy laws or deceptive deliverability workarounds.
- Checklist items MUST include specific threshold limits relevant to {{daily_send_volume}}.
- Maintain an objective, audit-ready operational tone throughout.
Output format
1. Risk Profile Summary (Markdown table: Risk Category, Baseline Threshold, Trigger Warning)
2. Multi-Stage Launch Readiness Checklist (3 sections: Data Hygiene, Technical Infrastructure, Messaging Controls)
3. Kill-Switch Activation Triggers (Clear numeric threshold criteria to halt sending)
Self-review
- Does the checklist account for regional privacy nuances in {{target_territory}}?
- Are technical verification steps realistic for {{outbound_channel_mix}}?
- Are hard numerical trigger points defined for the kill-switch protocols?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.