Lightmeter Beam

Beam is Lightmeter’s campaign workspace for growth teams running outbound at startup speed.

Use Beam to build multi-step sequences, manage A/B variants, monitor performance, and act quickly when a variant underperforms.

• Create campaigns, prepare leads and sequences, and submit them for review when ready.
• Prepare and review campaign wording in Creative before choosing what the campaign should use for future sends.
• Use Unibox for one-to-one follow-up through Interactive Replies.
• Pause or resume sending for active campaigns and individual variants.
• Drill down from Reports directly into campaign analytics for action.

1. Reply Rate: replies ÷ (leads contacted − all bounces).
2. Positive Reply Rate: positive replies ÷ (leads contacted − all bounces). See Positive Reply Definition for what counts as positive.
3. Positive Reply Share: positive replies ÷ total replies.
4. Campaign Reply Counting: campaign-level reply totals are deduplicated by sender within a campaign (a sender contributes at most one reply unit).
5. Interactive Replies (Unibox): outbound one-to-one replies sent manually by your team from Unibox in Beam.
6. Threaded Steps: scheduled campaign steps configured as thread. These are different from Interactive Replies.
7. Completed Contacts: contacts in a terminal state (all steps sent, or undeliverable).
8. Size: average email body size for the step or variant, measured in bytes.
9. Infra Health: mailbox deliverability/reputation score for the selected report period.

A positive reply is a human reply to a campaign that shows buying interest or moves the sales conversation forward.

1. Create a campaign and assign leads.
2. Set your sending schedule and mailbox limits.
3. Prepare wording in Edit Campaign → Creative.
4. Approve and mark a Creative snapshot Ready when the campaign should use it for future sends.
5. Preview and test message content.
6. Submit the campaign for review when it is ready to send.
7. Once the campaign is active, monitor results in Edit Campaign → Analytics and Reports, then optimize.
8. Pause or resume active campaign sending when campaign-level control is needed.
9. When a lead replies and needs human follow-up, send an Interactive Reply from Unibox.

Use Edit Campaign → Creative to prepare the campaign's editable working copy. Creative changes do not alter an immutable snapshot already selected for sending.

Working copy, snapshots, and Ready Creative

• Creative is the single editable, autosaved, collaborative working copy.
• A snapshot is an immutable saved version. Historical snapshots are Not approved or Approved.
• Ready identifies the approved snapshot selected for future campaign sends. When another approved snapshot becomes Ready, the earlier one is Replaced.
• Approve and mark ready performs both actions together for now. Approval records acceptance; Ready records which approved snapshot the campaign will use.
• Restoring a snapshot copies its content into Creative for editing. It does not modify the snapshot.

Separate status meanings

• Creative version: working copy or historical snapshot.
• Snapshot approval: Not approved or Approved.
• Snapshot readiness: Ready or Replaced. An approved snapshot that has never been Ready needs no readiness label.
• Component eligibility: Enabled or Disabled. In Creative this plans eligibility for the next Ready snapshot; in Ready and Analytics it changes current eligibility.
• Campaign runtime: Draft, Active, Paused, or Completed. Ready Creative does not mean that the campaign is active.
• Editor connection: Live or Offline. This describes collaboration only, never sending.

Comments and Versions

• Comments stay with Creative and do not change campaign sending behavior.
• Save a snapshot before larger edits, review milestones, or handoff to Steps.
• Actual sending is established by campaign activity and message history, not by Ready or Replaced labels alone.

Generated Creative and Privacy

Use Generate… to convert marketing materials into a three-step Creative draft using AI. Describe the audience and offer, then paste source text or choose or drag and drop a TXT, Markdown, or PDF file. If needed, open Additional prompt for AI copywriter to change copy style, length, punctuation, greeting layout, or sign-off format. Those optional instructions cannot change privacy, source grounding, threading, supported variables, or the fixed three-step structure. Review or retry individual components in the preview, then insert the draft and edit it in Creative. By default, generated bodies use {{senderFirstName}} for the sending mailbox identity in the sign-off.

Use Email Inventory to see how your sending domains and mailboxes are distributed across campaigns and which inventory is currently unused.

• Domains shows each domain’s current status, total active mailbox count, recent mailbox activity, and linked campaign assignments.
• Mailboxes shows each mailbox’s warming indicator, assignment status, linked campaigns, and Last activity time.
• Distribution shows inventory usage by campaign so you can see assigned versus recently used domains and mailboxes at a glance.
• Use Last 24 hours or Last 5 days to change the recent-activity window across all three pages.
• Click counts, chips, or inventory pills to open the matching filtered view or jump straight to campaign analytics.

Use Team to see who has workspace access, invite new members, review setup status, and manage workspace roles.

• Open Team from the main navigation, or open Settings → Team.
• Use the search box, role filter, setup filter, and access filter to find the right person quickly.
• Use the sortable columns to review members by name, role, setup status, safeguard status, or last activity.

Invite a Member

1. Click Invite Member.
2. Enter the person's email address, first name, and last name.
3. Choose a role if the role selector is shown.
4. Click Invite Member.
5. Copy the setup link and send it to the person through a channel your team trusts.

Roles and Permissions

Role	What they can do on Team
Member	Invite another normal workspace member and view the team list.
Admin	Invite members or admins, change Member/Admin roles, remove workspace access, and create fresh setup links for pending members.
Owner	Appears in the team list as a workspace manager. Owner role changes and owner access removal are not handled from Team.

Manage Existing Members

• Use the Role column to change a member between Member and Admin when you have permission.
• Use Setup to see whether first-time setup is complete or still pending.
• Use Safeguards to review visible account protection signals such as password or multi-factor authentication status.
• Use the setup-link action for pending members who need a fresh setup link before first sign-in.
• Use the remove-access action when someone should no longer be able to use the workspace.

Use the UniBox reply sentiment and category filters to find campaign reply threads by their current reply classification.

• Sentiment is the broad bucket: Positive, Neutral, or Negative.
• Category is the specific reason within that bucket, such as Meeting scheduled, Follow up later, or Direct rejection.
• The filters apply to threads, not individual messages. A matching row opens the full thread.
• The filter uses the current stored reply classification for the campaign lead. It is not limited to the first email in the thread, and it does not hide other messages in a matching thread.
• If both sentiment and category are selected, both must match. For example, Negative plus Direct rejection shows threads currently classified as Negative and Direct rejection.
• A thread has one current Positive/Not positive reply status for reporting. Automatic updates keep a positive thread positive if a later reply is neutral or negative; manual changes made in UniBox remain authoritative.

Message history can contain more than one classified reply over time. The UniBox list filter uses the current stored lead classification for the thread.

Beam can notify your CRM, workflow tool, or internal application automatically when important events happen.

A webhook is an automatic notification that Beam sends to a URL you choose. Your system can listen for these notifications and take action immediately, for example by creating a CRM task, updating a pipeline stage, or alerting a sales rep.

• Use webhooks when you want Beam to push information out in real time.
• Webhook setup is available in Settings → Webhooks.
• Beam supports both Beam-native webhooks and Instantly-compatible webhook events for customers migrating from Instantly.

Start Here

Most teams use Beam webhooks to send reply notifications into Slack. Start with the direct Slack setup below, then use the rest of this section as a reference.

• Quick Start: Slack reply notifications
• General webhook setup
• Signed delivery verification
• Available events
• Available delivery formats
• Short webhook examples
• Direct Slack details
• Instantly-compatible events

Quick Start: Slack Reply Notifications

If you want Beam to notify a Slack channel when leads reply, this is the fastest path.

1. In Slack, create a simple app in the workspace where you want the notifications to appear.
2. Open Incoming Webhooks in the Slack app settings and turn them on.
3. Click Add New Webhook, choose the Slack channel, and copy the generated https://hooks.slack.com/services/… URL.
4. In Beam, open Settings → Webhooks and create a new webhook.
5. Choose positive_reply if you want newly positive replies and follow-up replies in already-positive conversations.
6. Choose reply_received only if you want every qualifying human reply, including replies that Beam does not classify as interested.
7. Set the format to Slack, paste the Slack incoming webhook URL, save, and send a test notification.

How To Set Up A Webhook

1. Open Settings in Beam.
2. Go to Webhooks.
3. Select the event you want Beam to send.
4. Paste the destination URL that should receive the event.
5. Save the webhook and test it with a known reply or campaign action.

We recommend using an HTTPS endpoint that your team controls.

Verify Signed Webhook Deliveries

Standard JSON + HMAC and Instantly-compatible webhook deliveries include HMAC headers so your endpoint can verify that the request came from Lightmeter before processing it.

1. Create a webhook in Settings → Webhooks.
2. Copy the signing secret shown after creation. It is shown once.
3. When your endpoint receives a webhook, read the raw request body before parsing JSON.
4. Build the signed content as Webhook-Id.Webhook-Timestamp.raw_body, using the header values exactly as received.
5. Compute an HMAC-SHA256 digest with the signing secret and compare it to the v1 signature using a constant-time comparison.
6. Reject deliveries with old timestamps, invalid signatures, or duplicate Webhook-Id values.

Header	Value
Webhook-Id	Stable delivery event identifier. Use it as an idempotency key.
Webhook-Timestamp	Unix timestamp in seconds.
Webhook-Signature	v1, followed by the Base64-encoded HMAC-SHA256 digest.

signed_content = Webhook-Id + "." + Webhook-Timestamp + "." + raw_request_body
expected = "v1," + base64(hmac_sha256(signing_secret, signed_content))

You can rotate a webhook's signing secret from Settings → Webhooks. Copy the new secret immediately after rotation, then update your receiving endpoint before relying on future deliveries.

Webhook Events You Can Use

Event	Ways Beam can send it	Use it when	What happens
positive_reply	standard, slack, slack_native	You want sales to see the replies that matter most	A lead replies in a way Beam sees as positive. This also includes later replies in a conversation that is already positive.
campaign_created	standard, slack, slack_native, instantly_compatible	You want another system or team to know a new campaign exists	A campaign is created. Beam includes the workspace, campaign link, and campaign details that are available.
campaign_submitted	standard, slack	You want to track campaigns submitted through the API	A campaign is submitted through the Beam API.
reply_received	slack, slack_native, instantly_compatible	You want every human reply, not only positive ones	A real person replies to a Beam campaign thread.
email_sent	instantly_compatible	You are moving an Instantly-style send workflow to Beam	Beam sends and stores a campaign email.
email_bounced	instantly_compatible	You want to react when a campaign email bounces	A sent campaign email bounces and Beam can match the bounce back to the campaign.
lead_interested	slack, slack_native, instantly_compatible	You want to move or qualify a lead when they become interested	Beam marks the lead's current reply state as interested.
lead_not_interested	slack, slack_native, instantly_compatible	You want to route or suppress leads who say no	Beam marks the lead's current reply state as not interested.
lead_wrong_person	slack, slack_native, instantly_compatible	You want to clean up contacts or find the right person	Beam marks the lead's current reply state as wrong person.

Positive Reply, Reply Received, And Lead Interested

These three sound similar, but they answer different questions.

• Use positive_reply when you want people to look at the replies most likely to turn into sales conversations.
• Use reply_received when you want every human reply, including neutral and negative replies.
• Use lead_interested when another system should run only when a lead moves into the interested state.

When you use standard, the JSON also tells your endpoint whether this is the first positive reply or a later reply in an already-positive conversation.

What you want	Use this event	Works with	Plain-English note
Only the replies your team is most likely to care about	positive_reply	standard, slack, or slack_native	This is Beam's focused positive-reply event. It does not use the Instantly-compatible format.
Every human reply, even when it is not positive	reply_received	slack, slack_native, or instantly_compatible	Choose this if you do not want Beam to filter reply notifications down to only positive conversations.
A lead becoming interested, not every later reply from that lead	lead_interested	slack, slack_native, or instantly_compatible	Choose this for handoff rules that should run once when the lead becomes interested.

Ways Beam Can Send Webhooks

Format	Good for	In plain English
standard	Your own app, CRM, or workflow endpoint	Beam sends a structured JSON message. Your endpoint can verify the signature before trusting it.
slack	Zulip	Beam sends a short chat message that Zulip incoming webhooks can display.
slack_native	Slack channels	Beam sends a Slack-friendly message with the layout Slack expects. Use a direct Slack incoming webhook URL.
instantly_compatible	Existing Instantly-style automations	Beam sends flat JSON fields that are easier to plug into automations that already expect Instantly-style webhooks.

Short Webhook Examples

These examples show the basic shape of each option. Real webhook tests use the same shape, with your actual campaign, lead, and message details.

Standard JSON + HMAC

Choose standard when you are sending webhooks to your own system and want to check that the message really came from Beam.

{
  "id": "evt_019ce214-f5f1-7806-b1b3-a6e02f403819",
  "version": "1",
  "timestamp": "2026-03-06T09:15:00Z",
  "event_type": "positive_reply",
  "campaign": {
    "id": "campaign_123",
    "name": "Spring CTO Outreach"
  },
  "lead": {
    "email": "alex@example.com",
    "first_name": "Alex",
    "company": "Example Inc"
  },
  "event_data": {
    "message_preview": "Sounds good, please send times.",
    "classification": {
      "primary_category": "positive",
      "subcategory": "meeting_requested",
      "confidence": 0.95
    },
    "is_first_positive_reply": true,
    "is_positive_conversation_follow_up": false
  }
}

Zulip-Compatible Chat Message

Choose slack for Zulip. The saved format name is slack because Zulip accepts Slack-style incoming webhooks. Beam also adds the Zulip topic to the delivery URL.

{
  "text": "**Lead:** Alex Rivera (alex@example.com)\n**Message** [🔗](https://app.example.com/beam_ui/unibox/thread_123): Sounds good, please send times."
}

Slack-Native Chat Message

Choose slack_native for Slack. Beam sends plain text plus Slack blocks so the message looks clean in a Slack channel.

{
  "text": "Spring CTO Outreach\nalex@example.com\n\nStep: 2\nVariant: 1\n\nReply:\nSounds good, please send times.",
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "Spring CTO Outreach\n<mailto:alex@example.com|alex@example.com>"
      }
    },
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "<https://app.example.com/beam_ui/unibox/thread_123|Reply>:\nSounds good, please send times."
      }
    }
  ]
}

Instantly-Compatible JSON

Choose instantly_compatible when you already have an automation built around Instantly-style fields.

{
  "timestamp": "2026-03-06T09:15:00Z",
  "event_type": "reply_received",
  "lead_email": "alex@example.com",
  "campaign_id": "campaign_123",
  "campaign_name": "Spring CTO Outreach",
  "email_id": "019ce214-f5f1-7806-b1b3-a6e02f403819@beam.test",
  "reply_text": "Sounds good, please send times.",
  "unibox_url": "https://app.example.com/beam_ui/unibox/thread_123",
  "step": 2,
  "variant": 1
}

Direct Slack Details

If you want Beam notifications to render cleanly in Slack, send them directly to a Slack incoming webhook URL.

• Use the slack_native format in Beam for direct Slack delivery.
• Do not put Zapier in the middle if you care about message formatting. Zapier often rewrites or flattens the payload, which breaks the Slack layout Beam sends.
• Your team does not need a Slack Marketplace app from Lightmeter. You create a simple Slack app inside your own Slack workspace and use its incoming webhook URL.

Which Beam Events Support Direct Slack

Slack-native delivery is currently available for campaign-created and reply-related events.

• campaign_created
• positive_reply
• reply_received
• lead_interested
• lead_not_interested
• lead_wrong_person

email_sent and email_bounced currently use the instantly_compatible format only.

What The Slack Message Includes

Beam's direct Slack format is designed for human-readable campaign and reply notifications.

• Campaign name
• Reply sender email
• Step and variant when available
• A Reply link that opens the matching Unibox thread when Beam has a Unibox URL
• A truncated reply preview so long quoted email chains do not flood the Slack channel

Instantly-Compatible Events

Beam currently supports seven Instantly-compatible events. These are the recommended choices if you already have downstream automations that expect Instantly-style webhooks.

• campaign_created is sent whenever a campaign is created and includes workspace details, campaign details, and a campaign edit link.
• email_sent is sent for each successfully persisted outbound campaign send.
• email_bounced is sent for each campaign-matched bounce after Beam marks the original outbound message as bounced, stores the inbound bounce, and updates the campaign lead to bounced.
• reply_received is sent for each qualifying human reply.
• lead_interested, lead_not_interested, and lead_wrong_person describe the lead's current supported reply state.
• Only campaign-matched bounces emit email_bounced. Orphan or unmatched bounce traffic does not emit a customer-facing webhook.
• Beam keeps campaign analytics separate from webhook delivery, so receiving more than one reply does not inflate your campaign reply counts.

email_id is included on email_sent and reply_received. It is Beam's outbound email message_id in stored form (uuid@domain, without angle brackets). Use it as a stable correlation key across send, reply, retry, and debugging workflows. Beam does not currently expose a public API endpoint that accepts email_id, so treat it as an identifier for reconciliation rather than as a reply token.

Example: email_sent

{
  "timestamp": "2026-03-06T09:15:00Z",
  "event_type": "email_sent",
  "workspace": "workspace_123",
  "campaign_id": "test-campaign-1234",
  "campaign_name": "Test Campaign",
  "email_id": "019ce214-f5f1-7806-b1b3-a6e02f403819@beam.test",
  "lead_email": "test@example.com",
  "email": "test@example.com",
  "firstName": "John",
  "lastName": "Doe",
  "companyName": "Example Inc",
  "email_account": "campaign@beam.test",
  "email_subject": "Re: your invite: AI event in Munich",
  "email_html": "
John,

Can I reserve you a seat?
",
  "is_first": false,
  "unibox_url": null,
  "step": 2,
  "variant": 1
}

Example: email_bounced

{
  "timestamp": "2026-03-06T09:15:00Z",
  "event_type": "email_bounced",
  "workspace": "workspace_123",
  "campaign_id": "test-campaign-1234",
  "campaign_name": "Test Campaign",
  "lead_email": "test@example.com",
  "email": "test@example.com",
  "firstName": "John",
  "lastName": "Doe",
  "companyName": "Example Inc",
  "email_account": "campaign@beam.test",
  "unibox_url": null,
  "step": 2,
  "variant": 1
}

Example: reply_received

{
  "timestamp": "2026-03-06T09:15:00Z",
  "event_type": "reply_received",
  "lead_email": "replying.sender@example.net",
  "workspace": "workspace_123",
  "campaign_id": "test-campaign-1234",
  "campaign_name": "Test Campaign",
  "email_id": "019ce214-f5f1-7806-b1b3-a6e02f403819@beam.test",
  "email": "replying.sender@example.net",
  "firstName": "John",
  "lastName": "Doe",
  "companyName": "Example Inc",
  "unibox_url": "https://app.beam.test/beam_ui/unibox/thread_test_123",
  "email_account": "campaign@beam.test",
  "email_subject": "Re: your invite: AI event in Munich",
  "email_html": "
John,

Can I reserve you a seat?
",
  "reply_subject": "Re: Test Campaign",
  "reply_text": "Thanks for reaching out. This looks relevant for our team.",
  "reply_text_snippet": "Thanks for reaching out. This looks relevant for our team.",
  "reply_html": "
Thanks for reaching out. This looks relevant for our team.
",
  "step": 2,
  "variant": 1,
  "is_first": true
}

In the example above, the matched lead is still John Doe from Example Inc, but the reply arrived from a different sender address. That difference is expected for reply_received.

Example: lead_interested

{
  "timestamp": "2026-03-06T09:15:00Z",
  "event_type": "lead_interested",
  "lead_email": "test@example.com",
  "workspace": "workspace_123",
  "campaign_id": "test-campaign-1234",
  "campaign_name": "Test Campaign",
  "email": "test@example.com",
  "firstName": "John",
  "lastName": "Doe",
  "companyName": "Example Inc",
  "unibox_url": "https://app.beam.test/beam_ui/unibox/thread_test_123",
  "reply_subject": "Re: Test Campaign",
  "reply_text": "Thanks for reaching out. This looks relevant for our team.",
  "reply_text_snippet": "Thanks for reaching out. This looks relevant for our team.",
  "reply_html": "
Thanks for reaching out. This looks relevant for our team.
",
  "step": 2,
  "variant": 1
}

Choosing Between Beam-Native And Instantly-Compatible Events

• Choose Beam-native positive_reply if you are starting fresh with Beam and want notifications for interested conversations without receiving every non-positive reply.
• Choose Instantly-compatible events if you are replacing existing Instantly webhook automations and want to minimize downstream changes.

Use Settings → Blocklists to set which email addresses and domains should never receive emails.

When Beam processes an explicit unsubscribe reply successfully, it keeps that lead unsubscribed in the current campaign and also adds the recipient email to the workspace email blocklist with source Auto Unsubscribe.

What You Can Do

• Manage two independent lists: Email Address Blocklist and Domain Blocklist.
• Add values manually, import values from CSV, remove selected values, and export the active list to CSV.
• Filter and sort values by source and block time.
• Review blocklist change history in Settings → Activity.

Send Behavior

• Blocklists are scoped to your workspace.
• When a recipient matches an active blocklist value, Beam skips the send for that lead.
• Skipped blocklist sends are tracked in campaign analytics as blocklisted outcomes.
• Remove an Auto Unsubscribe entry from Settings → Blocklists if you intentionally want to contact that recipient again.

Matching Rules

• Email addresses must match exactly. Upper/lowercase differences are ignored.
• Domain names must match exactly. Upper/lowercase differences and Unicode variants are handled automatically.
• Subdomains must each be specified separately (example.com does not block sd.example.com).
• Unicode/IDN domains are normalized safely before matching.

CSV Import Rules

• Beam uses the first non-empty column in each row as the value.
• The first row is treated as a header when it looks like Value, Email, or Domain.
• Duplicate values inside the same CSV file are ignored.
• Preview shows valid, invalid, duplicate, and already-existing values before apply.

Beam lets you decide how broadly duplicate leads should be filtered before new leads are added to a campaign.

The setting lives in Edit Campaign → Leads → Add Leads to Campaign and applies to both Existing Audience imports and Upload CSV top-ups.

What It Does

• Beam always skips leads that are already in the same campaign.
• The deduplication policy controls whether Beam should also skip leads found elsewhere in your workspace.
• Preview shows how many leads are already in the campaign, how many are skipped by deduplication, and how many remain importable.

Available Policies

Policy	What Beam skips
None	Only leads already present in the same campaign.
Active and paused campaigns	Leads with active membership (pending, started, or paused) in other active or paused campaigns, in addition to same-campaign duplicates.
All campaigns	Leads already present in any campaign, including completed campaigns.
All audiences	Leads already present in any audience, even if that audience is not attached to a campaign.

What You Will See In The UI

• Already in campaign counts same-campaign duplicates.
• Skipped by dedupe policy counts leads excluded by the selected policy outside the current campaign.
• Importable after dedupe is the number Beam can still add before blocklist/send-time checks are considered.
• Blocklisted leads can still be imported; Beam blocks them later at send time.

Use Edit Campaign → Leads → Add Leads to Campaign → Upload CSV when you want to add more leads to an existing campaign from a spreadsheet.

Beam imports every valid unique lead it can and reports rows that could not be added. Duplicate rows do not block the whole upload.

How Beam Counts Uploaded Rows

• A row needs at least one usable email address before Beam can add it to a campaign.
• If multiple CSV rows point to the same lead, Beam keeps the first matching row and reports later matching rows as duplicate CSV rows.
• Rows for leads already in the campaign are counted as Already in campaign; Beam does not create a second campaign entry for the same lead.
• The selected lead deduplication policy can also skip leads that already exist elsewhere in your workspace.
• The campaign lead total counts distinct leads added to the campaign, not the raw number of rows in the uploaded CSV file.

What Happens After Upload

• Valid unique leads are added to the campaign.
• Non-blocking row messages identify rows that were duplicates, already present, skipped by dedupe policy, or missing required contact data.
• If some rows are reported but other rows are valid, Beam still adds the valid rows instead of failing the entire upload.

Re-uploading A Lead You Removed From This Campaign

• If you manually removed a lead from this campaign before sending began, uploading that same lead back into the same campaign returns the lead to Pending.
• This also applies when you remove affected leads from the launch-readiness repair flow after reviewing missing template values.
• Re-uploading does not reopen leads that already ended for another reason, such as a reply, unsubscribe, bounce, blocklist, campaign completion, or a manual removal after sending had already started.

If The Campaign Total Looks Lower Than The CSV Row Count

• Check the upload result for duplicate CSV rows, rows without a usable email address, leads already in the campaign, and dedupe-policy skips.
• Use Edit Campaign → Analytics to review actual sends after the leads are added. Analytics reflects delivered campaign activity, not the original raw CSV row count.

Use Edit Campaign → Leads to remove an individual lead from a live campaign when they should stop receiving future emails from that campaign.

Beam shows these leads as Removed on the Leads tab. Removed is a campaign-level terminal status. It is not the same as Unsubscribed or Do Not Contact.

When To Use It

• The lead progressed elsewhere and should stop receiving this campaign.
• You discovered the lead is a duplicate in an already-running campaign.
• The contact is wrong or invalid for this campaign.
• You have an operational reason to stop this lead without suppressing them globally.

What Happens

• Beam stops future emails for that lead in that campaign only.
• The lead remains visible in the campaign lead list with status Removed.
• You must choose a removal reason. If you choose other, add a short note.
• You can optionally override the attributed step and variant if the default attribution is misleading.

Re-uploading Corrected Leads

• If a lead was removed manually while still waiting in the campaign queue, uploading that corrected lead back into the same campaign returns the lead to Pending.
• The launch-readiness workflow for missing template values uses this same manual removal behavior when you choose to remove affected leads.
• If the lead had already started sending before removal, re-upload does not resume that sequence automatically.

Removal Reasons

Reason	Use it when
Progressed	The lead moved forward outside Beam and should stop receiving this campaign.
Meeting Booked	The lead booked a meeting or equivalent CTA outcome.
Not Interested	You know the lead is not interested in this outreach, but they are not being globally unsubscribed.
Wrong Contact	The lead is the wrong person or wrong target for this campaign.
Invalid Contact	The address or contact data is unusable, stale, or otherwise invalid.
Duplicate	The lead is duplicated in the current campaign and one record should be removed.
Other	The lead should stop receiving the campaign for another reason. Add a short note so the reason is clear later.

Step and Variant Limits

• Up to 10 steps per campaign.
• Up to 6 variants per step (A-F).

Delay and Threading

• Delay is configured in days for each step.
• From Step 2 onward, each variant can be configured as threaded to send as a reply in the same email thread.

Variant Controls

• Preview & Test opens the exact variant content for review.
• Pause / Unpause Variant is available per variant row.
• Delete Variant is disabled when the step has only one variant.

Deleting Sequence Steps

• Beam keeps step numbers contiguous after a delete. If you remove Step 4 from a five-step campaign, the remaining sequence becomes Steps 1-4.
• Step 1 cannot be deleted from an existing campaign. Edit the first message instead of removing it.
• Middle-step deletion is only available while Beam can safely compact the remaining steps. In practice, this means the campaign must still allow step reordering.
• If Beam cannot safely renumber later steps, it disables middle-step deletion instead of leaving the campaign in a partially updated state.
• Deleting the final step is still allowed when it does not require renumbering earlier steps.

When Middle-Step Deletion Is Available

• Middle-step deletion is intended for draft campaigns before sending or lead progression has started.
• When available, Beam deletes the selected step and automatically renumbers the later steps in the same save flow.
• If a delete action is disabled, edit the existing step, delete only the final step, or duplicate the campaign and restructure the sequence before activation.

Save Behavior

• Autosave is on and shows explicit save state (Saving, Saved, Failed, Unsaved).
• You can still use Save All Sequences for a manual checkpoint.

Use template variables in campaign subjects, campaign bodies, reply snippets, and Unibox replies to personalize messages with lead and sender data.

Common Variables

• {{firstName}}, {{lastName}}, {{companyName}}, and {{email}} use standard lead profile fields.
• {{senderFirstName}} and {{senderLastName}} use the sending mailbox identity.
• {{attr.key}} uses a custom lead attribute named key. For example, {{attr.aiIcebreaker}} uses the aiIcebreaker attribute.

Fallback Text for Missing Values

• Add fallback text after a pipe so the message still reads naturally when a value is blank: {{companyName | your company}}.
• Spaces before or after the pipe are supported and behave the same way: {{ companyName | your company }} is equivalent to {{companyName|your company}}.
• Fallbacks work for custom attributes too: {{attr.aiIcebreaker|quick note}} and {{ attr.aiIcebreaker | quick note }} both render quick note when that lead has no aiIcebreaker value.
• You can chain candidates from left to right. {{firstName|companyName|there}} uses first name when present, then company name when present, then there.
• Spaces that are part of fallback text are preserved only when that fallback is used. For normal greetings, prefer Hi {{firstName|there}} so spacing is correct whether Beam uses the lead value or the fallback. Use a fallback such as {{firstName| there}} only when the fallback itself should begin with a space.
• A literal pipe character inside fallback text is not supported. Avoid fallback text such as {{firstName|ACME | Partners}} because Beam treats each pipe as another fallback candidate.

Random Text Variations

• Use {{RANDOM|Hello|Hi|Hey}} to let Beam choose one option when rendering the message.
• Spaces around random-option pipes are ignored too. {{ RANDOM | Hello | Hi }} is equivalent to {{RANDOM|Hello|Hi}}.
• Random options are trimmed at the edges, so keep sentence spacing outside the RANDOM block when each option should share the same surrounding spaces.

Literal Braces

• Escape the opening braces when you want to include literal template syntax in an email: \{{example}} renders as {{example}}.
• Unescaped template-like text must resolve safely. If Beam would leave {{example}} in the rendered email, readiness checks and live sending block it before the message is sent.

Campaigns and Unibox Replies

• Campaign editors keep variables as template text while you write because each campaign can send to many different leads. Use campaign preview and readiness checks to review rendered examples before activation.
• Unibox replies are one-to-one. Variables inserted directly or through snippets resolve to the selected thread's lead and sender values in the reply draft.
• Resolved Unibox values are highlighted in the editor so you can see which words were personalized. The preview shows the final message without editor-only highlighting.
• If a Unibox variable is missing or empty and has no safe fallback, the draft shows a visible missing-value marker and sending stays blocked until you fix the value or edit the text.

Missing Variable Values

• A variable value is the actual lead or sender information used to replace a variable such as {{firstName}} or {{senderFirstName}} before a message is sent.
• If a required value is unavailable and there is no fallback text, Unibox shows a missing-value marker and blocks sending so the message does not go out with a blank or unresolved variable.
• To fix a missing value, update the relevant lead or sender information, choose a different variable, add suitable fallback text where reusable content is edited, or replace the marker directly in the draft for that one reply.

Activation Readiness Behavior

• Required lead and sender variables without values or fallback text block activation.
• Custom attributes without values also block activation when they would render as raw template syntax. Add a fallback, fill the lead attribute, escape the braces if the literal text is intentional, or remove affected leads from the campaign.
• Use an explicit empty fallback such as {{attr.aiIcebreaker|}} only when a blank value is acceptable. Beam warns about the affected leads but does not block activation.
• Adding non-empty fallback text removes the missing-value warning for that variable because Beam has safe text to render.

Beam spaces sends automatically and applies limits before every email. This keeps outreach steady and lowers deliverability risk.

How Beam Decides Whether A Campaign Can Send Right Now

1. Beam checks whether the campaign is allowed to run right now: active status, completion deadline, and schedule window.
2. Beam checks whether a lead is actually due for its next step.
3. Beam checks which mailbox that lead is allowed to use.
4. Beam checks whether that mailbox is currently eligible to send, including cooldowns and daily limits.
5. Beam only sends when both the lead and a mailbox are ready in the same processing cycle.

Automatic Delay Between Emails

• Per mailbox cooldown: Beam enforces a baseline pause between sends from the same mailbox.
• Natural variation: Beam adds randomized jitter so sends do not follow a rigid fixed interval.
• Outcome: each mailbox sends at a human-like cadence instead of a predictable machine pattern.

Batching Rules

• Beam evaluates active campaigns continuously in recurring processing cycles.
• Each cycle processes a bounded subset of eligible leads instead of flushing everything at once.
• Started leads keep their sender mailbox for follow-up consistency.
• If multiple mailboxes are assigned, Beam distributes sends across currently available mailboxes instead of concentrating everything on one sender.
• If one mailbox is busy with started leads but another mailbox is idle, Beam can still use the idle mailbox for other eligible leads in the same cycle.
• If multiple campaigns share the same mailbox, that mailbox's overall daily capacity is shared rather than reserved per campaign.
• A campaign can send multiple emails in one cycle, but one mailbox cannot send again until its cooldown is complete.

How Mailbox Assignment Works

• Started leads: Beam keeps follow-ups on the same mailbox whenever possible.
• New Step 1 leads: Beam can use any active eligible mailbox assigned to the campaign.
• Mailbox removed from the new-lead pool: Beam can still let already-started leads finish on that mailbox if it is still structurally valid and has send capacity.
• No reserved share: when multiple campaigns share a mailbox, Beam uses the mailbox's remaining daily capacity as it becomes available rather than reserving a fixed slice for each campaign.

Other Timing Controls You Configure

• Step Delay (days): each sequence step waits the configured number of days before it is eligible to send.
• Schedule Window: sends only run on selected days and times in the campaign timezone, or in each lead's timezone when use_lead_timezone is enabled and the lead has a valid timezone.
• Campaign Limit: Beam enforces the campaign-wide max/day using the campaign timezone for the daily reset.
• Mailbox-wide Capacity: if a mailbox-wide daily capacity is configured for a mailbox, Beam enforces that shared cap across all campaigns using the mailbox.
• Missing Mailbox-wide Capacity: if a mailbox does not have a mailbox-wide daily capacity configured yet, Beam shows Not configured and does not apply a mailbox-wide daily cap until one is set.
• No Reserved Mailbox Share: shared mailbox capacity is not automatically split or reserved per campaign.

What Stops Future Sends For A Lead

• The first qualifying human reply stops future campaign sends for that lead in that campaign.
• An explicit unsubscribe reply also stops future sends immediately and adds the recipient to the workspace blocklist.
• Remove from campaign stops future sends only in that campaign and does not create workspace-wide suppression.
• Automated non-bounce replies such as out-of-office messages are tracked separately and do not by themselves mark the lead as replied.

Common Reasons A Campaign Waits Instead Of Sending Immediately

Reason	What it means
Outside schedule window	The campaign is active, but the current time is outside the allowed send days or hours.
Campaign daily max reached	The campaign has already used its allowed sends for the current campaign day.
No lead is due yet	Sequence delays or lead-local schedule rules mean no lead is ready for the next step yet.
Mailbox cooling down	The mailbox has sent recently and must wait before it can send again.
Mailbox limit reached	The mailbox-wide daily capacity has been exhausted for that mailbox.
Lead already stopped	A qualifying reply, unsubscribe, manual removal, or completion deadline has already stopped future sends for that lead or campaign.

Use Completion Deadline when a campaign must stop sending after a specific cut-off.

How Beam Applies The Deadline

• The deadline is treated as an exact cut-off time.
• In the Beam UI, the deadline is edited in the campaign timezone shown in the schedule settings.
• When the deadline has elapsed, Beam stops any remaining sends for that campaign immediately.

What You Will See

• An active campaign whose deadline passes is moved to Paused with reason Deadline reached.
• Campaign list and campaign overview show a Deadline passed badge so the stop is visible without opening logs.
• Beam does not mark the campaign completed just because the deadline passed. Leads may still remain untouched.

What Happens To In-Flight Sends

• Beam re-checks the deadline immediately before each SMTP handoff.
• If the deadline passes during a processing cycle, any sends that have not yet been handed to SMTP are blocked.
• Only messages that were already accepted for delivery before the deadline check can still leave the system.

How To Continue After A Deadline

• Extend the deadline or clear it in the campaign settings.
• Then resume the campaign manually.
• If the deadline is still in the past, Beam will block resume until it is moved forward or removed.

Changing the mailbox pool on an active campaign can affect any leads that already started the sequence. Switching sender identity mid-campaign can hurt deliverability and thread continuity, so Beam now makes that impact explicit before the change is applied.

Pool And Continuity Mailboxes

The campaign mailbox screen shows all mailboxes still connected to the campaign. The Use column explains why each mailbox is present:

• Pool: the campaign can use this mailbox for future leads and future sends that do not already have a fixed sender.
• Continuity: the mailbox is no longer in the sender pool, but started leads are still linked to it so their sequence can continue from the same sender.

Continuity mailboxes are not used for new leads. They remain visible so you can see how many started leads are still attached, how many are ready now, and whether those started leads should keep their current sender, be reassigned, or be paused.

When Beam Shows A Warning

• If you remove a Pool mailbox that still has started leads associated with it, Beam opens a confirmation step instead of silently applying the change.
• The warning shows the removed mailbox addresses, how many started leads are affected, and how many are ready to send now.

Resolution Options

• Keep started leads on current mailboxes; future leads stop using these mailboxes: safe default. The mailbox leaves the sender pool, but started leads keep using their current sender. The mailbox then appears as Continuity until those started leads finish or are otherwise resolved.
• Reassign started leads to replacement mailboxes: move affected started leads to a replacement mailbox. Future sends for those started leads come from the replacement sender.
• Pause affected started leads: pause affected started leads and fully detach the removed mailbox from that campaign.

Resolving Continuity Mailboxes Later

• Select one or more Continuity mailboxes and choose Reassign selected started leads to move their started leads to replacement mailboxes.
• Use Auto-match replacements to pre-fill likely replacements based on similar mailbox names, then review the choices before applying.
• If those started leads should not continue sending, choose the pause option instead.

What You Can See After The Change

• The campaign mailbox screen marks Continuity mailboxes separately from Pool mailboxes.
• Each retained mailbox shows its address, active started lead count, ready-to-send count, and a shortcut to view the affected leads.
• The affected-leads shortcut opens the existing campaign lead list with a sender-mailbox filter applied. Beam does not add a separate mailbox-history page in this release.

Campaign pause/resume controls sending for the entire campaign after it is active. Draft campaigns are submitted for review instead of being activated directly.

• Pause is available on active campaigns and stops new emails from being scheduled and sent.
• Resume is available on paused campaigns and returns the campaign to active status once any blocking issue has been addressed.
• Sending restarts on the next processing cycle after resume succeeds.

Operational Timing

Beam processes sends in batches. In rare cases, a small number of in-flight emails may complete just after pause is clicked.

• The exact number depends on how many sends are already in progress at the moment you pause.
• New work is blocked immediately after pause takes effect.

Variant pause/unpause controls only one variant in one step.

Exact Scope

• Pause applies to one specific variant in one specific step.
• It does not pause the whole campaign and does not pause same-letter variants in other steps.

What Happens to Lead Flow

• If a step still has at least one active variant, leads continue through those active variants.
• If all variants in a step are paused, leads wait at that step until a variant is unpaused.
• Reassignment happens at send time, so you do not need to bulk-move leads manually.

Where You Can Take Action

• Sequences tab: full variant editing and pause/unpause controls with confirmation copy explaining lead-flow impact.
• Analytics tab: quick action buttons for pause/unpause/delete at the variant row level.

Safety Guards

• Analytics quick actions prevent pausing or deleting the last active variant in a step.
• Deleting a variant is blocked when it would leave the step without a valid active path.

Unpause requires explicit confirmation and includes an experiment-validity warning.

Historical analytics for a variant remain visible even if that variant is currently paused.

The Analytics tab is optimized for operational decisions: you can inspect performance and take action in the same table.

Campaign Summary

• Shows topline progress, engagement, list quality, and deliverability.
• Displays both percentage bars and hard counts for contacted and completed leads.
• All Replies and Pos Replies remain human-reply metrics only.
• Auto Reply Rate is a deliverability-oriented rollup that combines human replies with automated non-bounce replies such as out-of-office messages.

Deliverability Summary Metrics

• Content Health: overall deliverability content score from Beam deliverability testing.
• Infra Health: overall mailbox/reputation health score from Beam deliverability testing.
• Auto Reply Rate: total reply rate including autoresponder replies such as out-of-office messages.
• On Google and Microsoft, only messages that land in inboxes can generate these auto replies, so this metric is treated as a deliverability signal.
• The lead count under Auto Reply Rate is the number of deduplicated leads who generated either a human reply or an automated non-bounce reply.

Reply Counting Rules

• All Replies and Pos Replies stay human-only.
• Auto Reply Rate combines the deduplicated human-reply count with the deduplicated automated non-bounce reply count.
• A sender with both an automated non-bounce reply and a later human reply still counts once in the combined Auto Reply Rate.
• Multiple auto replies from the same sender still count as one lead in campaign summary metrics.

Step Performance Analytics

• Engagement: Sent, Replies, Reply Rate.
• Replies in analytics are inbound campaign replies from leads, not outbound Interactive Replies sent from Unibox.
• Content Health: Size, Google Score, MS365 Score.
• Infra Health: deliverability score for the selected report period.
• Actions: Preview, Pause/Unpause, Delete (variant rows).

Metric Timeframes on this Table

• Content Health uses the most specific available test result: exact message results when available, then campaign step-and-variant results, then campaign-level results, then recent workspace-level sampled content tests.
• Infra Health reflects deliverability during the selected report period.
• Size is average email body size measured in bytes.

Beam includes a shared reply snippet library for Unibox so your workspace can reuse common follow-up copy without leaving the thread.

Where to Manage Snippets

• Open Settings → Snippets to view and edit the shared workspace library.
• From the campaign editor, open the snippets manager modal when you want to update reusable reply copy without leaving campaign setup.

How to Insert Snippets and Variables

• Open a Unibox reply or forward draft.
• Type / to open the insert menu. Variables appear first, followed by saved snippets where snippets are supported.
• Type # to open the snippet-only picker.
• Use the search field in the insert menu to narrow the list, then press Enter or select an item to insert it at your cursor position.
• Inserted snippets append into the draft. Existing draft content is not replaced.
• Variables inside inserted Unibox snippets resolve to the current thread's lead and sender values and are highlighted in the draft.
• Use Preview to review the final reply without editor-only highlighting before sending.
• If a snippet contains a variable that is missing or empty for the selected thread, Unibox shows a visible missing-value marker and blocks sending until the draft is fixed.

How to Insert Content While Editing a Snippet

• In the snippet editor on Settings → Snippets or in the New snippet dialog from Unibox, type / to open the insert menu.
• Type # to open the snippet-only picker while editing a snippet.
• Variables appear first in the / menu. Other snippets appear below them when they are available.
• Use the search field in the insert menu to narrow the list, then press Enter or select an item to insert it into the snippet body.
• This works in both the plain text and rich text snippet editors. The snippet currently being edited is not shown in its own insert menu.

Create a New Snippet From Draft Text

• Highlight the part of the reply you want to reuse.
• Click New snippet in the composer toolbar.
• Name the snippet and save it to the shared workspace library.

Rich Text and Plain Text Behavior

• A snippet can have a plain text version and a rich text version.
• Campaign editors insert plain text only. Rich text snippet content is never inserted into campaign copy.
• Unibox inserts the version that matches the active composer mode: rich text in rich mode, plain text in plain text mode.
• Use Generate Plain Text from Rich or Generate Rich Text from Plain to create or refresh one version from the other, then review and save it before inserting.
• When generating rich text from plain text, Markdown-style bullets and links are converted into rich formatting for review before saving.
• If the generated version would replace existing content, Beam asks you to confirm before overwriting it.
• Plain text contexts show only plain text. Add visible URLs to the plain text version when a URL should appear in the plain body.
• Variables such as {{firstName}} are preserved using Beam’s existing template rendering rules.

Beam includes a dedicated Activity Log so teams can verify who changed what, and when.

It is the primary product surface for auditability and audit log review.

Where to View It

• Open Settings → Activity.
• By default, Beam shows account-level campaign events in reverse chronological order.
• Use Include lead-level events when you need per-lead membership outcomes.

What You Can Verify

• Campaign status changes (including pause/resume transitions).
• Sequence and variant changes, including variant paused and variant unpaused.
• Team member invites, role changes, access removals, and fresh setup-link creation.
• Deduplication policy changes and dedupe-based lead skips during audience import or CSV top-up.
• Audience import outcomes (lead added vs skipped) when lead-level events are enabled.
• Actor identity and source (for example UI, API, system, worker).

How to Use It Operationally

• Validate experiment changes before reviewing performance shifts.
• Confirm exactly when a variant was paused/unpaused relative to KPI movement.
• Resolve team handoff questions with a shared, timestamped timeline.

UI Behavior

• The Activity page is paginated (30 events per page by default).
• Events are displayed as a timeline table with time, event type, campaign, summary, actor, and source.

“I paused a variant but leads still moved”

That is expected when other variants in the same step are still active. Leads are reallocated to active variants in that step.

“Why is Pause/Delete disabled in Analytics actions?”

Analytics quick actions enforce at least one active variant per step. This avoids accidentally blocking sends from the analytics table.

“Why can I delete the last step but not a middle step?”

Deleting a middle step requires Beam to renumber every later step safely. If the campaign can no longer support that compaction flow, Beam disables middle-step deletion instead of risking a partially updated sequence. Final-step deletion can still stay available because it does not require renumbering earlier steps.

“Why is a report row not clickable?”

Some legacy rows may not have a direct campaign ID. Beam uses a safe fallback by campaign name, and disables linking if the match is ambiguous.

“Why did report metrics shift?”

Some report definitions can evolve over time (for example reply counting or deliverability calculations). Compare like-for-like time windows and check your Activity Log before drawing conclusions.

“Why do reply counts look lower than raw reply-email volume?”

Campaign-level reporting deduplicates by sender in each campaign, so multiple reply emails from the same sender do not all increase the campaign reply count.

“Do campaigns stop sending after a lead replies?”

Yes, after the first qualifying human reply. When Beam receives the first human reply for a campaign lead, it stops future campaign sends to that lead in that campaign.

Explicit unsubscribe replies also stop the lead immediately and add the recipient to the workspace blocklist. Automated non-bounce replies such as out-of-office messages are tracked separately under Auto Reply Rate and do not by themselves mark the lead as replied.

“Why is Auto Reply Rate separate from Reply Rate?”

Beam keeps the raw automated non-bounce reply signal separate so human reply metrics keep their existing meaning. Auto Reply Rate is the deliverability-oriented rollup that combines human replies with automated non-bounce replies.

“What is an Interactive Reply versus a threaded step?”

Interactive Replies are manual one-to-one messages sent by a user from Unibox. Threaded steps are scheduled campaign steps configured to send in an existing email thread. They are different Beam concepts.

“Can I verify who paused or unpaused a variant?”

Yes. Go to Settings → Activity to view the Activity Log with timestamp, actor, and event summary (including sequence pause/unpause events).

Missing Features or Controls

If features you expect to see are missing, check that browser privacy or ad‑blocking tools are not blocking PostHog.

• Disable adblockers for the Beam site.
• In Firefox, turn off Enhanced Tracking Protection for the site and reload.