Call list preparation

Ahead of a dialing session, the agent reads the contacts your rule selects, checks each record for a valid phone number and consent status, and stages them in the PhoneBurner list the campaign names. Contacts missing a number, or marked do-not-call, are held back and reported to the rep. The agent notes why each contact was included so the list stays defensible. Records that look duplicated across two campaigns go to a person to decide which session should own the call, keeping reps from dialing the same lead twice in one day.

Disposition write-back

After each call, PhoneBurner records an outcome, and the agent reads that disposition and updates the matching CRM record with the result, the call time, and any note the rep left. Outcomes that map cleanly to your rule, like left voicemail or not interested, advance the contact to the next step. Dispositions that conflict, such as a sale marked on a contact already closed, go to a person to sort out. The agent keeps the raw PhoneBurner outcome beside the CRM update so nothing is lost in translation between the two systems.

Follow-up queue building

When a call ends with a promised next contact, the agent reads the outcome and the rep's note, then opens the follow-up task on the date your rule assigns. Callbacks requested for a specific time get placed on that slot; vague promises like next week go to the rep to pin down. The agent notifies the owner when a follow-up comes due and updates the contact record once it is handled. It leaves urgent or high-value callbacks for a person to confirm rather than auto-queuing them without a second look.