Bell AI
Constant Contact → Mojo

Section 3 · CC unsub → Mojo DNC

CC unsubscribe → Mojo DNC: the compliance fix

Every week, your email list and your dial list drift. Below: the contact who unsubscribes at 11:18 AM is off your dial queue before your next session. Click Unsubscribe inside the email — or the button above the panes — to run it.

Idle — armed
This scene is wide — open it on a desktop to see the CC → Bell AI → Mojo flow in full.

What this would actually be in your account

"This is the loop closing in ten seconds for the demo. In your account it runs on a 2–15 minute latency, which is correct — the SLA is ‘before the next dial,’ not ‘instant.’"

The scene above is scripted locally — no real CC, no real Mojo, no live Zapier. The real wiring is one multi-step Zap, one Airtable base, and one smart-filter tweak on your dial list.

Wall-clock latency in production: Constant Contact’s New-Unsubscriber webhook fires within ~5 minutes; Zapier polls at 1–15 minute intervals depending on plan. The point is not sub-second; the point is that it happens at all, every time, without you in the loop.

Production wiring
CC: New UnsubscriberZapierAirtable: Lead RegistryMojo: Update ContactMojo: Add to DNC group

One Zap, one Airtable base, one smart-filter rule. ~4–5 hours of build time once your accounts are connected.