PREVIEW + CONFIRM (WHY SMS IS TWO-STEP)

Every SMS broadcast goes through a Preview + Confirm modal before it actually sends. This is intentional and not optional.

Why

SMS is non-recallable. Once Twilio accepts the send, you can't take it back. So an accidental fan-out of "test test" to 25 band members at 3 AM costs you trust and Twilio dollars.

The preview-confirm dance is the safety net. You see what's about to happen, you click to confirm, then it fires.

What the preview shows

For each channel you enabled (SMS / Email):

• Ready count — how many recipients are deliverable on that channel
• Skipped count — how many will be dropped, with reason breakdown
• Sample names — the first ~8 recipients by name

For SMS specifically, skip reasons are itemized:

• no_phone — no SMS channel mapped
• opt_in_pending — opt-in invite sent but not confirmed
• opted_out — replied STOP at some point

Sending by text or voice note

If you have Full Access, you can text the band's number (or send a voice note) to have BandBrain text people for you:

• "Text everyone: lobby call moved to 9."
• "Text Joe and Caity that soundcheck is pushed to 4."
• "Email the production crew the load-in time."

BandBrain replies with exactly who will get it and the exact message, then waits. Reply yes to send it. What goes out is exactly what you approved; it's saved at preview time, so BandBrain can't reword it in between. To change something, just say what to change and you'll get a new preview. A preview expires after 30 minutes, and saying yes twice won't send it twice.

When you name people, BandBrain matches them to the roster. If a name matches nobody, or more than one person, it asks instead of guessing.

Only people on the roster who opted in to texts can receive them. BandBrain can't text promoters, venue staff or anyone else off the roster; phone carriers require that people opt in first. People who were picked but can't receive it (no phone, not opted in, or texted STOP) are listed in the preview.

This is enforced in code, not just in the prompt.

When you can't bypass

There is no "skip preview" toggle and won't be. The brevity loss is intentional. If you're sending the same broadcast twice in a row (say, after a typo), it's still two steps each time.

For scheduled automations, the preview-confirm doesn't apply — the automation pre-vetted at create time, so each fire is one-click. See Scheduled automations.

When sends happen instantly

The CONFIRM click is what triggers the actual send. Twilio processes each SMS sequentially (one per recipient, ~200ms each), so a 30-person broadcast takes 5-10 seconds end-to-end. You'll see "sent X" on the comms card when done.

If anything fails (Twilio rate limit, recipient unreachable), the comms history row surfaces the error count.