Journey step transitions

When a contact meets an entry condition, a Beam agent reads the contact record and its current journey position in Pingback. It applies your approved rule to advance, hold, or exit the contact from a step, then writes the new stage and any tags back onto the record. Standard moves that match your criteria happen on their own. A contact with conflicting signals, a missing consent flag, or membership in overlapping campaigns is set aside, and the agent notifies a marketer to decide the right path before the journey continues, so no one advances on an unclear signal.

Campaign send triggers

Sends should fire only when a contact truly qualifies. On a triggering event, the agent reads recent activity and suppression state, checks it against your approved send rule, and queues or times the message through Pingback. Qualified, unsuppressed contacts move ahead automatically. Anyone near a frequency cap, recently bounced, or flagged for manual outreach is pulled from the automatic path, and the agent hands that contact to a person with the reason noted, so nobody gets a message that your own rules would have blocked from going out in the first place.

Contact list membership

Lists drift as people subscribe, convert, or go cold. Watching for activity changes, the agent reads the contact and applies your segmentation rule to add or drop list memberships, then writes the update in Pingback. Clear matches adjust without anyone stepping in. When a contact fits several conflicting segments, carries an unclear status, or would leave a list tied to compliance, the agent leaves membership unchanged and asks a marketer to confirm, keeping your audiences accurate without letting an automated rule quietly reshape a regulated list behind your back.