Cross-channel contact updates

SendPulse holds one contact across email, SMS, and chatbot channels with the details and consent for each. A Beam agent reacts to activity on any channel, reads the shared contact, and applies your approved rule to update fields or consent status so every channel works from the same record. The change writes back across SendPulse. Where consent differs between channels, or an update would contact someone who opted out on one of them, the agent halts and refers the case to a person so your messaging stays within the permissions each contact granted.

Automation flow membership

SendPulse runs automated flows that guide contacts through email and messaging steps. An agent reads a contact's recent behavior, checks it against the entry rules your team set, and adds or removes the contact so the right people move through each flow. It records the membership change on the contact for reporting. When a contact matches two flows that should not run together, or an addition would exceed the send frequency you allow, the agent notifies the owner and leaves the decision to them rather than enrolling anyone on its own.

Subscriber list maintenance

Mailing lists in SendPulse gather subscribers with their status, source, and custom fields. A Beam agent watches for new signups, bounces, and unsubscribes, reads the affected subscriber, and applies your rule to correct a field or drop an address that can no longer receive mail. The list writes back so counts and segments stay accurate. A subscriber who appears on conflicting lists, or whose status disagrees with recent channel activity, is set aside for a person to resolve, so cleanup never removes an active contact by accident.