Campaign has no eligible leads: trace one contact through the gates

Define the decision

Counts from different screens often describe different populations. A list can contain many contacts while a campaign has few enrolled people, or a campaign can contain completed and paused enrollments alongside active ones. Treat the mismatch as a definition problem first; it may be expected rather than a failed import.

Work through the procedure

1. Select a contact you expected to receive a message and confirm that the intended address exists in the correct workspace and list.
2. Check whether that contact belongs to the campaign. Record the enrollment state separately from the contact's general lead status.
3. Inspect whether a message step remains and whether its due time has arrived inside an allowed window.
4. Review suppression, unsubscribe and bounce status. If exclusion is intentional, keep it in place and correct the campaign forecast rather than trying to bypass it.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Population reconciliation
Contacts in source list: 80
Actually enrolled: 50
Of those: 30 completed, 10 paused, 10 active
Active but not yet due: 10
Messages eligible right now: 0
Importing the 80 contacts again does not fix this state

Read the result

Each reduction needs a reason, not a workaround. The example shows how a large source list can legitimately yield zero immediate work. If the ten active contacts become due and still do not progress, the next investigation is schedule, sender and capacity—not whether the original CSV contained 80 rows.

Check before moving on

1. Use unique contact or enrollment identifiers when similar names appear more than once.
2. Reconcile a few records from each state instead of relying only on headline totals.
3. Document which exclusions are deliberate so another operator does not reverse them during troubleshooting.

Limits and next action

Do not change a suppressed contact back to active solely to increase an eligible count. Zintara checks blocklist and relevant lead states during sending. If the visible state does not explain exclusion, ask the operator for the affected enrollment's evidence rather than recreating the contact.

Source: Zintara sequence product context