Outbound email dispatch

SMTP2GO relays transactional email such as receipts, password resets, and notifications. When an upstream event calls for a message, a Beam agent reads the recipient and template data, applies your approved rule for which template and sender address to use, and hands the email to SMTP2GO for delivery. The send is recorded against the related record so your team can see it went out. If required fields are missing, the address looks malformed, or the template is not approved for that audience, the agent stops and routes the case to a person for review.

Bounce and failure alerts

Every email either lands or bounces, and SMTP2GO reports the reason. A Beam agent reads these delivery events as they post back, separates hard bounces from temporary failures using your rule set, and updates the contact record accordingly. Hard bounces mark an address as undeliverable so it is not mailed again; soft bounces are noted for a later attempt where the connector allows. The agent notifies the owner when a key message fails to reach someone. Spam complaints and unusual bounce spikes are escalated to a human rather than handled silently by the agent.

Open and click tracking

SMTP2GO records when a recipient opens a message or clicks a tracked link. A Beam agent reads those engagement events and, following your approved rule, updates the related record with the activity and a timestamp. Repeated opens on a sales message can notify the assigned rep that interest is warm. Aggregate figures roll up so a campaign owner sees reach without manual counting. Where an event looks inconsistent, for example clicks with no matching open, or engagement from an address flagged internally, the agent passes it to a person for a closer look.