Master Blaster broadcasts

Master Blaster is how you take a journey that has already proven itself and fire it once, at scale, to a large audience, without leaving your guardrails. Most of TrailGuide is patient and personalized. Master Blaster is the deliberate opposite: a single, big, well-timed moment that everyone should see at roughly the same time.

The key word is proven. A blast is not a fresh idea sprayed at your whole list. It is the promotion of something that already earned its place in a smaller, measured setting, which is what makes sending it wide a calculated move rather than a gamble.

From a proven journey to a broadcast

Master Blaster starts from a winner. You take a multi-step journey that performed, or the winning variant surfaced by optimization lineage, and promote it into a one-time broadcast. The message that beat its alternatives on real lift is the one you scale, so the blast inherits evidence instead of hope.

A broadcast should be a victory lap for a message that already won, not the first time you find out whether it works.

For big, deliberate moments

Not every send should be a broadcast, and that is the point. Master Blaster is built for the handful of moments that genuinely warrant reaching everyone at once: a product launch, a seasonal push, a milestone worth celebrating across your whole base. A team at Fernwood Kitchen might reserve it for a fall menu launch to its weeknight cooks and use quiet, personalized journeys for everything else.

Deep links that resolve, not dead-ends

A broadcast is worthless if the tap goes nowhere. Master Blaster is careful about deep links: links in the message resolve to recent content, so when thousands of people tap at once they land on something live rather than a stale item that no longer exists. A dead-end tap at broadcast scale is thousands of small disappointments, so the send avoids them by design.

Recorded, and inside your guardrails

Scale does not mean escaping the rules. A blast still respects your frequency and engagement caps and holdouts, so even a large send honors the limits you set once. And every blast is written to a changelog: what went out, to whom, when, and with which links. A broadcast is a big action, so it leaves a big, legible record.

• Guardrailed: caps and holdouts apply to the blast like any send.
• Recorded: every blast lands in a changelog you can audit later.
• Verifiable: the preview shows the real deep links, not stand-ins.

Schedule it server-side through MCP

You rarely want a big moment to fire the instant you finish preparing it. Master Blaster sends can be scheduled server-side and driven through MCP, so you set the moment in plain language and TrailGuide holds it until then, no browser tab left open, no manual finger on the button at launch hour.

Schedule a Master Blaster from the fall-menu journey to the
weeknight-cooks audience for Sep 20 at 9am local. Show me
the preview with the real deep links before it is armed.

The result is a broadcast that behaves like the rest of the harness: proven before it scales, guarded on the way out, and recorded once it lands, so a big moment stays a deliberate one.