Broadcasts

A broadcast is a one-off campaign sent to a live segment. You pick the audience, write a one- or two-line brief, and Zubby generates a unique message for every recipient grounded in that brief and in what it knows about each shopper. There is no shared template and no merge tags — each shopper gets copy written for them. Broadcasts are for ad-hoc moments (a flash sale, a restock, a thank-you); recurring lifecycle automation belongs in journeys.

Where it lives

Dashboard → Broadcasts. The page has two halves: a composer on the left to queue a new broadcast, and a list of your last 50 campaigns on the right with live delivery counts.

Plan gate

Broadcasts are a Growth-and-up feature. The composer surfaces an Upgrade planlink if your plan doesn’t include them — the API returns a 402 and the UI handles it gracefully.

Composing a broadcast

The composer has exactly three inputs:

Segment— a dropdown of your live segments. The selected segment’s description shows underneath so you know who you’re about to message. Counts are computed in real time, so the audience is whoever matches the moment you send.
Channel — EMAIL or SMS. Pick the one your audience is reachable on; SMS requires shoppers to have a usable phone number and consent.
Brief — up to 2,000 characters, minimum 10. This is the grounding instruction for the AI: the offer, the tone, the must-mention details. Example: “20% off all summer dresses this weekend with code SUN20 — urgency, friendly tone, mention free returns.”

Hit Queue broadcastand the campaign is handed to the broadcast-send worker, which writes and sends a message per recipient. You’ll see the new campaign appear in the list with live counts.

The brief is a hard boundary

The AI never invents offers beyond your brief. If you don’t put a discount in the brief, it won’t promise one. Be specific about codes, percentages, and conditions — vague briefs make vague copy.

Reading the campaign list

Each row shows the target segment, the channel, the brief, a status badge, and a delivery summary. Status moves through:

Status	Meaning
Queued	Accepted and waiting for the worker to pick it up.
Sending	The worker is generating and dispatching messages.
Completed	Every recipient has been processed.
Failed	The campaign could not complete.

The delivery line reads sent / recipient count, plus a failed count when any sends bounced or errored, and the timestamp the campaign was created.

Why per-recipient copy beats a template

Relevance— the message can lean on the shopper’s history and interests rather than a one-size body.
Deliverability — many near-identical sends look like a blast to inbox filters; varied copy reads more like real mail.
Grounding— the brief keeps every variant truthful and on-offer, so “unique” never means “made up.”

Gotchas

Broadcasts are one-off. There is no schedule field — the campaign sends when you queue it. For timed, repeating, or behavior-triggered sends, use journeys.
The audience is the segment’s live membership at send time. A shopper who ages out of the segment a minute later was still in scope when you queued.
Channel availability depends on your connectors and on each shopper’s contactability and consent — SMS sends skip shoppers without a usable number.
The brief minimum is 10 characters and the maximum is 2,000. The Queue button stays disabled until the brief is long enough and a segment is selected.

Segments — define and inspect the audiences broadcasts target.
Journeys & sequences — automated, multi-step, triggered sends.
Cart & browse rescue — the highest-ROI automated campaigns.
Shoppers, lifecycle & VIP — the profiles that power per-recipient copy.

Broadcasts

Where it lives

Dashboard → Broadcasts. The page has two halves: a composer on the left to queue a new broadcast, and a list of your last 50 campaigns on the right with live delivery counts.

Plan gate

Broadcasts are a Growth-and-up feature. The composer surfaces an Upgrade planlink if your plan doesn’t include them — the API returns a 402 and the UI handles it gracefully.

Composing a broadcast

The composer has exactly three inputs:

Segment— a dropdown of your live segments. The selected segment’s description shows underneath so you know who you’re about to message. Counts are computed in real time, so the audience is whoever matches the moment you send.

Channel — EMAIL or SMS. Pick the one your audience is reachable on; SMS requires shoppers to have a usable phone number and consent.

Brief — up to 2,000 characters, minimum 10. This is the grounding instruction for the AI: the offer, the tone, the must-mention details. Example: “20% off all summer dresses this weekend with code SUN20 — urgency, friendly tone, mention free returns.”

Hit Queue broadcastand the campaign is handed to the broadcast-send worker, which writes and sends a message per recipient. You’ll see the new campaign appear in the list with live counts.

The brief is a hard boundary

Reading the campaign list

Each row shows the target segment, the channel, the brief, a status badge, and a delivery summary. Status moves through:

Status

Meaning

Queued

Accepted and waiting for the worker to pick it up.

Sending

The worker is generating and dispatching messages.

Completed

Every recipient has been processed.

Failed

The campaign could not complete.

The delivery line reads sent / recipient count, plus a failed count when any sends bounced or errored, and the timestamp the campaign was created.

Why per-recipient copy beats a template

Relevance— the message can lean on the shopper’s history and interests rather than a one-size body.

Deliverability — many near-identical sends look like a blast to inbox filters; varied copy reads more like real mail.

Grounding— the brief keeps every variant truthful and on-offer, so “unique” never means “made up.”

Gotchas

Broadcasts are one-off. There is no schedule field — the campaign sends when you queue it. For timed, repeating, or behavior-triggered sends, use journeys.

The audience is the segment’s live membership at send time. A shopper who ages out of the segment a minute later was still in scope when you queued.

Channel availability depends on your connectors and on each shopper’s contactability and consent — SMS sends skip shoppers without a usable number.

The brief minimum is 10 characters and the maximum is 2,000. The Queue button stays disabled until the brief is long enough and a segment is selected.

Broadcasts

Where it lives

Composing a broadcast

Reading the campaign list

Why per-recipient copy beats a template

Gotchas

Related

Broadcasts

Where it lives

Composing a broadcast

Reading the campaign list

Why per-recipient copy beats a template

Gotchas

Related