Campaign statuses

StatusMeaning
draftCreated but not dialing. Editable.
runningCXB Dialler can pick pending/retryable calls.
pausedDialling is paused. Some in-flight calls may still complete.
completedCampaign is stopped or all contacts reached terminal state.
failedCampaign hit a failure condition. Escalate if unclear.

Actions

ActionAvailable whenWhat it does
Startdraft / pausedMakes campaign eligible for CXB Dialler.
PauserunningStops new dialing.
ResumepausedContinues dialing.
Stoprunning / pausedMarks campaign completed.
Restartcompleted / failedPrepares a new run using same campaign identity.
CloneMost statesCopies setup into a new campaign.
Attempt ReportAny campaign with attemptsDownloads attempt-level CSV.

Call attempt states

Non-terminal (waiting or active) states:
StateMeaning
pendingReady for first attempt.
scheduled / retry_scheduledWaiting for retry time.
callback_scheduledCustomer-requested callback is waiting for its scheduled time. Dialled with top priority once due.
leasedCXB Dialler has claimed the row for work.
ringingSIP invite is ringing.
amd_screeningAnswered call is being screened for machine/human.
attachingAnswered call is being attached to CXB Core.
diallingDial attempt is being placed.
in_progressCustomer is connected to bot.
_processingAttempt result is being finalized.
Terminal states:
StateMeaning
completedConversation finished and result stored.
exhaustedRetries used up (or non-retryable outcome) — no more attempts.
abandonedAnswered but no CXB Core worker was free; counts against abandon rate.
amd_machineDetected as an answering machine and torn down.
window_closedSingle-day campaign window ended while the contact was still waiting.
manual_stoppedOperator stopped the campaign while the contact was waiting.
If non-terminal states remain old for too long, escalate to engineering. CXB Dialler has stale recovery, but stuck states are an operations signal.

Metrics

Campaign detail shows:
  • total calls
  • attempted count
  • answered count
  • completed count
  • failed count
  • retries remaining
  • attempt answer rate
  • completion rate
  • average handle time
  • abandon rate
  • machine detected count (machine_detected_count)

Callback stats

When callback detection is in use, the campaign tracks callback counters separately:
StatMeaning
callback_pendingCallbacks scheduled and still waiting to be dialled.
callback_completedCallback attempts that reached a terminal state.
callback_cancelledCallbacks cancelled (e.g. single-day window closed before they were due).
callback_exhaustedCallbacks that ran out of attempts.
See Callbacks for the full lifecycle. Always compare campaign metrics with SIP/carrier reports when reconciling billing.

Attempt report

Use Attempt Report to export attempt-level details for audit and client sharing. The report is useful for:
  • final campaign reconciliation
  • checking SIP status patterns
  • diagnosing retry behavior
  • finding numbers with repeated failures
  • confirming dispositions sent back by bot analysis