Behavioral Trigger Campaigns

Customer.io fires a message the moment a customer does, or fails to do, something specific, like abandoning a cart or skipping a first login. A Beam agent reads the incoming behavior event, checks it against the approved trigger rule, such as no purchase within 48 hours of a cart event, and confirms the right campaign fired for the right person. Where the rule allows it, the agent can pause a trigger for a customer who no longer qualifies, such as one who already converted through another channel. Ambiguous cases, like an event that partially matches two different triggers, are routed to a person to resolve.

Customer Segments

Segments in Customer.io group people by attributes and past events, such as plan type or days since last visit. A Beam agent reads updated attribute and event data, applies the team's approved segment rule, and moves a customer between segments when the data supports it, for example shifting an account from active to lapsed after a set period of inactivity. The agent notifies the lifecycle team when a segment shift affects an in-flight campaign. Customers with conflicting or incomplete signals, where the rule can't clearly decide, are left in place and flagged for a person to sort out.

Campaign Broadcasts

One-off broadcasts in Customer.io go out to a list built from current segment and attribute data. A Beam agent reads the recipient list before a scheduled send, applies the approved suppression rule, such as excluding anyone who unsubscribed or bounced in the last cycle, and updates the list accordingly. It notifies the marketing owner once the list is confirmed and ready. Any recipient whose suppression status is unclear, such as a recent complaint still being reviewed, is held out of the send and routed to a person for a final call.