The campaign canvas has a side panel with a list of building blocks you drag onto the canvas to build your journey. The panel is organized into three groups: Actions, Rules, and Timings.
An Action is a step that operates on the guest when they arrive at it — either sending them a message, changing something on their profile, or pausing the journey to wait for them to do something. Each action is a single card on the canvas. When a guest's journey reaches that card, the action runs once for that guest, and then the journey moves on to the next connected card.
The Actions group contains the following six cards:
1. Send Email
An action card that sends a designed email to the guest when their journey reaches this step. The Send Email card has four fields and two design actions. They must all be filled in for the step to send successfully.
1.1 Subject line
The subject of the email that the guest will see in their inbox.
Free-text field.
Personalization tokens (e.g., guest's first name) are supported and rendered at send time.
An empty subject is allowed at design time, but is highly likely to push the spam score into the bad range.
1.2 Sender name
The "From" name shown to the guest (e.g., "Beambox" or "The Coffee House Team").
Free-text field.
This is purely the display name — the actual delivery address is the field below.
Sender email (must be verified)
Sender Email is a drop-down that lists all sender email addresses (either verified or unverified), and also includes an option to add a new sender email by clicking Add sender email.
Verified emails — addresses you've already proved you own (these have a ✔ next to them and are safe to send from).
Unverified emails — addresses you've added but haven't confirmed (these have a ✖ next to them).
Add sender email — a custom option that opens a quick form for adding a brand-new address.
If you pick an unverified address, a small warning appears under the field: "This sender email isn't verified. Click here to verify it." Clicking that link saves your campaign as a draft and takes you straight to the Sender Emails settings page so you can verify it without losing your work.
1.3 Email body
This is the actual content of the email. There are two ways to fill it in:
Option A — Start from a Template
Option B — Start from scratch
Option A — Start from a Template
Click the Template button on the card.
A pop-up appears showing all pre-existing email templates from the library.
Click any template card to select it. The pop-up closes, and the selected template's name appears on the card (e.g., "Welcome a new guest").
Option B — Start from scratch
Click the Design button directly without picking a template.
The BEE drag-and-drop email editor opens with a blank canvas.
Design the email — drag blocks, write copy, drop images, style buttons — and save.
The designed content is then owned by this email step.
1.4 Spam score (appears after the email is designed)
Once a template is selected (or a custom design is saved) and the required fields (Subject, Sender Name, Sender Email) are filled in, a Spam Score badge appears on the card.
What the badge tells you:
The score is calculated by sending the rendered email (subject + body + sender) to Postmark's SpamAssassin spam-check API.
The score is a number — lower is better.
The badge color-codes the score into three buckets:
Good — clearly under the threshold → safe to send.
Warning — close to the threshold → review recommended.
Bad — at or above the threshold → would be flagged by spam filters.
Re-checking the score manually:
Next to the score is a ↻ (recheck) action.
Clicking it sends the current subject, body, and sender to the spam-check service again and updates the badge with the fresh score.
Use this after you edit the email, change the subject, or change the sender address.
2. Send SMS
An action card that sends one text message to the guest's mobile number when their journey reaches this step. Unlike the Send Email card, the SMS card has no separate fields for subject, sender name, or sender address.
The only thing you configure on the card is the message body itself, through the Design action.
A few things to keep in mind
The message body is required. If you save the campaign with an empty SMS body, the journey will fail at this step when it reaches a guest, and the activity log will record "send_sms step has empty message body".
SMS messages have a character limit set by the carrier (160 characters per segment for standard SMS). Beambox doesn't block long messages, but each extra segment is billed separately.
An unsubscribe footer is appended automatically (so guests can reply STOP). You don't need to type one yourself.
3. Tag / Untag
An action that adds a label (tag) to the guest's profile, or removes one. The system either adds the tags you've chosen to the guest or removes them — depending on the card's mode. The journey continues immediately to the next connected step.
Within the card, you can configure whether a tag should be added or removed, and specify one or more tag values, such as "vip", "birthday-club", or "reactivation-2026". Tags serve as powerful labels that help organize and categorize guests for future targeting and automation. For example, you can add an "opened-welcome-email" tag when a guest engages with a campaign, then use that tag as a trigger condition in a separate automated flow. Tags are also available throughout Beambox and can be used for audience segmentation, reporting, filtering, and data exports, making them a valuable tool for managing and understanding your guest database.
4. Unsubscribe Guest
An action that indicates the guest has opted out of email communication. When a guest reaches this step in the journey, they are automatically marked as unsubscribed across Beambox. The guest immediately exits the current campaign, and no further emails will be sent to them from this campaign or any other email campaign moving forward. This ensures that the guest's communication preferences are respected and helps maintain compliance with email marketing best practices.
This action is commonly used at the end of an unsubscribe confirmation sequence, as the final step after a guest explicitly requests to opt out of email communications, or as part of a re-engagement strategy where guests who have shown repeated inactivity—such as not opening emails after multiple attempts—are automatically unsubscribed. By including this step in your automation, you can keep your mailing lists healthy and focused on engaged recipients.
5. Archive Guest
An action that archives the guest's record. When a guest reaches this step in the journey, they are automatically archived and removed from your active guest list. The guest immediately exits the current campaign, and because they are no longer considered an active guest, they are also removed from any other campaigns they may currently be participating in. This action affects the guest across the entire platform, not just within the current automation flow.
The Archive Guest action is commonly used for dormant guest cleanup campaigns, where contacts have shown no engagement for an extended period. It can also be used as the final step in a hard opt-out process for guests who wish to be completely removed from marketing activities, or for contacts that have been identified as invalid, fake, or permanently bounced and should no longer be evaluated in future campaigns.
Important: Archiving a guest is a more significant action than unsubscribing. While unsubscribing only prevents future email communications, archiving removes the guest from your active database and excludes them from ongoing campaigns and audience segments. For this reason, we recommend using this action carefully and only when permanent removal from active marketing efforts is intended.
6. Wait for Trigger
A pause card that holds the guest at this step until a specific thing happens — or until a time limit runs out. It has two outputs: Action Taken (green) and Timed Out (red), so the journey can continue down different paths depending on what the guest actually did. This is the card that makes a campaign behavior-driven instead of just timed. The card has two configuration areas: Wait Until (what to wait for) and Maximum time to wait before timing out (how long to wait).
6.1 Wait Until — the event to wait for
The Wait Until dropdown lists every event Beambox can watch for. The options are grouped into three categories:
Note on the email/SMS options: "Email Opened", "Email Clicked", etc., are automatically scoped to the most recent Send Email/Send SMS step that occurred before this Wait card in the journey. In other words, you don't have to point them at a specific email — Beambox figures out which earlier message to watch by walking back along the canvas. This means a Wait card placed immediately after a Send Email card will track engagement for that specific email, not for any other campaign's emails.
6.2 Maximum time to wait before timing out
This is the deadline. If the event hasn't happened by the time this period runs out, the guest goes down the Timed Out path instead.
A number input (e.g.
7).A unit dropdown with four options: Minutes, Hours, Days (default), Weeks.
The default value is 7 Days.
So "7 Days" means: "Watch for this event for up to 7 days. If it happens, take the Action Taken path. If 7 days pass and nothing happens, take the Timed Out path."
Heads up on the 10-minute check: because Beambox checks every 10 minutes, an "Action Taken" path won't fire the instant a guest opens the email — it'll fire at the next check after that. So a 5-minute wait window doesn't really make sense; the smallest useful wait time is at the 10-minute mark or more.
General rules that apply to every action
A few things behave the same way no matter which action runs:
Each action runs once per guest per arrival. If the journey loops back to this step (e.g., via re-entry), it will run again—fresh.
Failures don't lose the guest. If an action errors mid-run, the journey is marked failed for that guest, but the rest of the campaign — and all other guests' journeys — keep running.