Behavior-triggered campaigns

Messages here fire from what a subscriber does, like signing up or abandoning a step. A Beam agent watches for the source event in your systems, reads the subscriber record, and applies your rule to enroll the person into the matching Vero flow. It writes the enrollment and any custom fields Vero needs, then confirms the trigger fired. Subscribers who match more than one competing flow, or who recently received a similar message, are surfaced to a marketer so people are not hit with overlapping sends by mistake.

Multi-channel message routing

Vero can reach the same person by email or push, and this decides which. When a message is queued, a Beam agent reads the subscriber's channel preferences and consent flags, then applies your rule to pick the allowed channel. It updates the record with the chosen route and the send status Vero returns. Contacts with missing consent, or whose preferred channel recently bounced or failed, are handed to a person, who confirms whether an alternate channel is acceptable before anything goes out to that subscriber and keeps the messaging compliant.

Subscriber list updates

Lists in Vero drift as people subscribe, change details, or opt out. A Beam agent picks up these changes from your source of truth, reads the current subscriber record, and applies your rule to add, update, or unsubscribe the person in Vero. It writes back Vero's confirmation and timestamps the change on your side. Opt-out requests that conflict with an active paid relationship, or duplicate records that appear to be the same person, are escalated to a marketer for a decision rather than being merged automatically, so no legitimate contact is silently lost.