Verified lead lists, built for Instantly.

Support boundary

Run it in this order

1. 1

   Verify destination configuration

   Select the intended campaign, inspect copy, subject variants, fallback variables, and timezone schedule before pushing.

   Expected: The feeder targets a correct campaign rather than a stale or previously sent one.
2. 2

   Produce an eligible queue

   Require valid verification, normalized names, no links in first-email variables, suppression clearance, and no prior membership.

   Expected: Every queued record satisfies data and campaign policy.
3. 3

   Push and record

   Use the direct provider with a stable idempotency key and store the destination lead ID and status.

   Expected: Exactly-once campaign membership under normal retries.
4. 4

   Reconcile scheduling

   Compare accepted leads with campaign count and confirm the active schedule resolves in the correct regional timezone.

   Expected: Leads are both present and eligible to schedule.

Confirm the audience before handoff

The matching count is visible before contact output. Check it and a masked sample before a paid export or destination push is allowed.

Current source pages