Skip to main content

Outbound Campaigns & Dialer

9. The agent experienceโ€‹

How work arrives depends on the mode.

Preview โ€” the contact arrives as a card the agent reviews before dialing:

The agent's preview card with contact details and Call / Skip

The agent's preview card with contact details and Call / Skip

The preview card: who's next, their details and dial history, with Call and Skip. The agent stays Available for inbound while the card waits โ€” an inbound call simply withdraws the card and the contact returns to the queue.

Progressive / power / predictive โ€” there's no card: Orbit dials the customer and connects the agent the instant the customer answers, so the agent goes straight into a live call.

A connected campaign call in the agent softphone

A connected campaign call in the agent softphone

Connected โ€” a live campaign call, handled like any other call.

After the call, the agent picks a disposition code, which drives the callback / retry / DNC behavior automatically, then completes any wrap-up form.

The campaign disposition panel after the call

The campaign disposition panel after the call

After hangup: pick the disposition โ€” this drives the follow-up behavior.

Manual dialing from the dialpadโ€‹

Agents can dial any external number from the softphone Dialpad โ€” no campaign needed. Manual dials still pass the DNC and quiet-hours checks and are logged as manual attempts, so ad-hoc calling isn't a compliance blind spot.

Manual dialing is a desktop (CTI) action, not a dialer feature โ€” the same line the major platforms draw. A manual call is never attributed to a campaign (reports show it with no campaign and mode manual), and none of the dialer machinery applies to it: no pacing, no answering-machine detection, no abandon accounting, no contact-list disposition. What manual and campaign calls do share is the call plane itself โ€” flows, recording, transfer/conference and supervision behave identically on both. The agent-side experience is described in Handling Calls ยง7.