The full operational workflow for running an AI Outreach campaign — from lead selection in Salesforce through enrichment and sending in Clay and Smartlead, all the way to reply handling and data writeback. This page replaces tribal knowledge and is the single source of truth for teams, auditors, and security reviews.
| Jira | Owner | Status |
|---|---|---|
| KLN-32 | MARCOM Ops + CRM Admin | ✅ Active · March 2026 |
The campaign lifecycle runs in two directions — outbound (steps 1–4) and inbound/writeback (steps 5–7). Every step is connected through the native Clay ↔ Salesforce connector, eliminating manual CSV transfers.
📋 Note: The diagram below shows the full flow. Import this page into Confluence, then insert the Campaign Lifecycle Diagram (separate HTML snippet) into an HTML macro directly below this paragraph.

MARCOM Ops creates or updates a Campaign with AI_Outreach__c = TRUE. Campaign Members are added using a list view or report filtered by Cold_Lead_Eligible__c = TRUE. All eligibility criteria must be validated before proceeding.

Use only the approved 'SFDC Campaign Member Export for Clay Import' report. This report always includes CampaignMemberId and LeadId as stable mapping keys — critical to avoid writeback mismatches.

Clay runs enrichment against the imported lead list — adding Company Description, Industry signals, and other approved fields. Enrichment outputs are staged for writeback. MARCOM must confirm enrichment quality before proceeding.
DEMAND7 MARCOM TO DETAIL
Inbound replies are captured in Smartlead's Master Inbox. Clay classifies each reply as Positive, Neutral, or Negative. Has_Replied__c is set to TRUE on first response (set-once — cannot be reset). Hard bounces are flagged and queued for sync.
The native Clay → Salesforce connector automatically pushes reply data (Has_Replied__c, ReplyClassification__c) and enrichment fields to Campaign Members and Leads. Hard bounce status is also written back. No manual CSV involved. CRM Admin monitors the connector for errors — see the Integration page for the full runbook. KLN-5 · Owner: CRM Admin · Automated · near real-time
Positive replies surface in the SFDC Sales Visibility dashboard. Sales reps are notified and must follow up within the agreed SLA. MARCOM monitors the Funnel dashboard (Replies, Positive Replies, Converted Leads). AI-generated draft reply assistance is available for common inbound questions — P2 feature currently in planning. KLN-12 · Owner: Sales · Salesforce dashboard · SLA applies · P2 draft replies
⚠️ Action required: Two High risks must be confirmed before EVERY campaign run — customer/partner indicators and Legal/DPO approval for enrichment. These are not one-time gates.
| Dependency / Risk | Level | Description | Mitigation |
|---|---|---|---|
| Customer/partner indicators in SFDC | 🔴 High | If flags are missing or unreliable, ineligible leads may enter outreach | Audit SFDC flags before each campaign. Agree fallback exclusion logic with CRM team. |
| Legal/DPO approval for enrichment | 🔴 High | Company Description and Industry writeback blocked until approved | DPO review tracked as dependency. Fields provisioned but locked pending sign-off. |
| Stable IDs in Clay export | 🟡 Medium | Missing CampaignMemberId / LeadId causes writeback mapping errors | Enforce use of approved export report only. Report validated to always include both IDs. |
| Connector sync errors | 🟡 Medium | Silent failures could leave SFDC and Clay out of sync | CRM Admin reviews connector error logs weekly. Full runbook in Integration page. |
| Sending infrastructure at scale | 🟢 P2 | Scaling 5k → 50k emails without multi-IP setup risks deliverability | Infrastructure blueprint to be delivered in Scale Readiness epic (P2). |