zintara.io

Campaign operations · Practical guide

Campaign status lifecycle: separate the container from each contact

Campaign status describes the sequence container. Enrollment status describes one contact's progression. Read both before concluding that a campaign is ready, stalled or finished.

Reviewed · Examples are illustrative

Who this helps: Campaign owners preparing, monitoring or recovering an outreach sequence.

Define the decision

A dashboard badge compresses a complex workload into one label. It is useful for navigation but insufficient for diagnosing individual outcomes. Your operational record should include the campaign state, contact state, current step and last known outcome. This prevents broad actions from being applied to a narrow exception.

Work through the procedure

  1. Identify the campaign-level state shown in the current interface and the action that last changed it.
  2. Sample enrolled contacts from different outcomes: untouched, progressing, replied, paused and completed where those states are represented.
  3. Record whether each contact has a remaining step and a next due time. Avoid inferring future work from the campaign badge alone.
  4. Choose the narrowest justified change. A single uncertain attempt should trigger investigation of that contact, not automatic replay of the full campaign.

Worked example

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

State matrix
Campaign active + enrollment active + due now → candidate for further checks
Campaign active + enrollment completed → no remaining sequence work
Campaign active + enrollment paused → investigate the pause reason
Campaign paused + enrollment active → campaign gate still prevents normal progression

Read the result

The first row says candidate, not guaranteed send. Capacity, selected mailbox and recipient checks remain. The other rows explain why mixed outcomes inside one campaign are normal. A healthy campaign can contain finished contacts, while an apparently active campaign may have no currently eligible work.

Check before moving on

  1. Use the exact current UI labels in a support report; do not invent a state name from an assumption.
  2. Confirm that a completed contact has the intended history before deciding a missing follow-up is a defect.
  3. Record campaign-level changes alongside individual exceptions so a later audit can distinguish them.

Limits and next action

This is a diagnostic matrix, not a complete API enumeration or a promise about every transition button. Zintara's sending path requires active campaign and enrollment state. Use the product controls for state changes and retain the original reason when investigating a pause.

Source: Zintara sequence product context

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow