Channel Selection

eSputnik can send a message through email, SMS, Viber, web push, or mobile push, and a customer typically has a stated preference or a channel they actually respond to. A Beam agent reads that preference alongside the event that triggers a message, such as an order update, and applies the approved rule for which channel to use first. It sends through eSputnik and notes which channel carried the message. If the message doesn't reach the contact on the first channel, the agent can fall back to an approved second channel. Contacts with no usable channel on file get routed to a person to update.

Triggered Campaign Sending

Beyond scheduled newsletters, eSputnik supports messages fired by a specific event rather than a calendar date. A Beam agent watches for an approved trigger in the connected system, such as an abandoned cart or a completed order, reads the relevant record, and sends the matching eSputnik message with the customer's own data filled in. It notes when the message went out against the originating record. An event that matches more than one trigger, or a record missing data the template needs, gets routed to a person to resolve before anything sends.

Cross-Channel Reporting

eSputnik reports engagement, such as opens or clicks, per channel rather than only in aggregate. A Beam agent reads this per-channel data on a schedule, applies the approved rule for what counts as a disengaged contact, and updates the contact's preferred channel or suppresses a channel that consistently fails to reach them. It writes a short note explaining why a channel was adjusted. A pattern that doesn't clearly fit the approved rule, such as a sudden drop across every channel at once, gets routed to a person to investigate.