Campaign Response Tracking

GiantCampaign records when a contact opens, clicks, or replies to a sent campaign. A Beam agent reads these response events and applies the customer's approved rule, for example tagging a contact as engaged after a second click or moving them into a follow-up sequence once they open a pricing email. It works from the data GiantCampaign already recorded rather than guessing at intent. Anything involving a reply with a direct question, a complaint, or a request to unsubscribe is routed to a human on the sales or support team, since those replies need a person's judgment, not an automatic tag.

Lead Tagging and Segmentation

Contacts in GiantCampaign carry tags and list memberships that decide which sequences they receive next. A Beam agent checks a contact's activity against the approved rule, for example adding a tag once someone attends a linked event or removing them from a cold list after three unopened sends, then writes that tag change back to the contact record. It only adjusts tags and list membership the account permissions allow. Anything involving a contact asking to change their own information, or a tag that would affect billing or contract terms, is routed to a human to confirm before it goes ahead.

Sales Handoff Notifications

When a contact crosses a threshold GiantCampaign can measure, such as opening several emails in a pricing sequence, that's a signal a sales rep would want to act on quickly. A Beam agent watches for that threshold and applies the approved rule, for example notifying the assigned rep with the contact's recent activity or adding them to a callback list. It bases the notification only on the events GiantCampaign recorded. Anything where the next step is unclear, such as a contact showing mixed signals or a duplicate record, is routed to a human to sort out before a rep reaches out.