Blasts for events, conferences, festivals and races
Add a direct communication channel to the attendee journey for updates before, during and after your event: parking, weather, schedule changes, venue instructions and the notices that can't wait for an inbox.
Built on Blasts. Connection-based, encrypted, no subscription, credits never expire.
Event communication fails at the exact moment it matters most: on the day, when everyone is moving and few people are reading email.
Ballroom B flooded overnight and the opening session is now in the exhibit hall. It is 7:50 a.m., the doors open at 8:00, and the only tools on the table are an email that will be read at lunch, an app that a third of attendees never installed, and a volunteer with a bullhorn.
A storm cell is 20 minutes out and the field has to clear. Twelve thousand ticket holders are on the grounds and in the parking lots, and the message needs to reach them on the phone in their hand, not in an inbox under yesterday's promo emails and a group text half of them silenced.
The start line moved because of a road closure, the corral times shifted, and the shuttle pickup is at a different lot. Runners are already in cars. The confirmation email from three weeks ago cannot help them now, and neither can the website they are not looking at while they drive.
There's another way
Blasts is built around persistent connections between parties who already know each other. An attendee connects with the event once, at registration or ticketing. From that point on, the organizer has a direct, encrypted channel that shows the message on the attendee's phone or desktop screen with the sender's name and photo, and an Emergency badge that pulses red and pins to the top when it counts.
Every event has one moment when the attendee is fully engaged and already handing over information: registration and ticketing. That is where the invitation belongs.
The confirmation page, the ticket email, the know-before-you-go message and the badge or bib pickup: the attendee is already paying attention. Put the invitation there.
One tap or one code, and the attendee approves your event. No mobile-number list to collect or maintain.
Parking the night before, the weather hold at the gate, the room change at 7:50 a.m., the results and next year's dates. Sent to everyone, or just the day, track or wave affected.
Every attendee, on the phone in their hand, before, during and after the event.
Attendees opt in and can silently disconnect at any time, including after the event ends.
The sponsor newsletter still belongs in email. These messages belong on the screen.
Which lot, which gate, where the shuttle is, when the doors open. Sent the evening before and again the morning of, to just the attendees arriving that day.
Lightning delays, heat advisories, shelter locations, resumption times and all-clear notices. Sent with the Emergency badge so it pins to the top and pulses red on every connected phone on the grounds.
A moved keynote, a swapped stage time, a delayed start wave. Sent to the track, stage or wave affected, with read acknowledgements so the operations desk knows who has seen it.
Bag policy reminders, medical tent locations, lost-and-found, water station changes, course reroutes. Short typed Blasts with a map image and a link.
The awards ceremony, the headliner set, the after-party, the packet-pickup window. Event Blasts carry a countdown and a calendar attachment so the time lands where the attendee will see it.
Results and photos, the survey poll, next year's early registration link, and a thank-you voice Blast from the organizer to a connected audience you did not have to rebuild.
Email is where confirmations and sponsor content live. SMS is where carrier fees, opt-out rules and character limits live. A custom event app only helps the attendees who installed it. None of them was designed for an organizer who already knows exactly who bought a ticket.
Blasts credits are bought once and never expire. One typed Blast to one attendee is one credit; a voice Blast is two. Credits left over from this year's event are still there for the next one, which fits an event budget better than a monthly platform seat.
The message appears on the attendee's screen with the organizer's name and photo. Read acknowledgements tell the operations desk who has actually seen the change, so staff and volunteers can focus on the people who haven't.
Distribution lists per day, track, wave, ticket type or role mean the corral-3 start change does not wake every runner in the field. Large lists can be staggered into daily waves for pre-event content.
Every Blast shows the sender's name and photo and a campaign badge (Emergency, Event, FYI, Promo, General or VIP). Attendees can revoke the event at any time without the organizer being notified. Messages auto-delete after 30 days with an optional self-destruct timer, and there are no tracking pixels.
| SMS | Blasts | ||
|---|---|---|---|
| Reaches attendees on event day | Depends on when the person opens email | Yes, if you have consented mobile numbers | Delivered to the connected person's phone or desktop screen |
| Per-message carrier cost | Low | Per message, per carrier | One prepaid credit per typed Blast; credits never expire |
| Confirms who actually saw the change | Open-tracking pixels only | Delivery only | Read acknowledgements from confirmed actions |
| Attendee must have connected first | No | Consent required | Yes, by design; attendees can disconnect silently |
| Rich content (maps, images, links, calendar) | Yes | Limited | Yes: rich HTML, images, links, events with calendar attachment |
Comparison reflects published Blasts.app product information as of August 2026 and general characteristics of email and SMS. A cost model for your attendance and message volume will be part of the event communication guide.
Blasts is not a way to message strangers, and DirectToAttendees does not pretend otherwise. It is built for the audience an organizer knows by name: the people who registered, bought a ticket or picked up a bib. That constraint is what makes the channel trustworthy for an attendee who is already tired of event spam.
For the person who will set it up
For the registration lead or operations manager who will set it up. Everything below reflects published Blasts documentation.
Add the event's personal invite link (blasts.app/connect/[ID]) and 4-digit connection code to the registration confirmation page, the ticket or bib-pickup email, the know-before-you-go message and the printed badge or wristband insert. Attendees tap the link or enter the code once; a public organization code lets them request the connection and the event approves.
For a registrant list that has opted in to event communications, upload that roster and send personalized Blasts invitations at scale through your own email service (Amazon SES, Microsoft Graph or Gmail). Each attendee still approves the connection.
For most events that is the iOS or Android app. Attendees at a desk before the event, or a virtual audience, can add the browser extension (Chrome, Edge, Brave and other Chromium browsers) or use the web app at blasts.app.
Create distribution lists for all attendees, each conference track, each festival day, each race wave or corral, VIP holders, exhibitors, volunteers and staff; there is no per-recipient cap and large lists can be staggered into daily waves. Send typed Blasts with maps and links, a voice Blast from the race director, Event Blasts with a countdown and calendar attachment, or a poll. Emergency Blasts pulse red and pin to the top.
Roster invitations are described in Blasts documentation as part of the Chrome extension; confirm before relying on them elsewhere. Exact administrator steps will be documented in the event communication guide once confirmed against current Blasts documentation.
In one paragraph
DirectToAttendees is an implementation of Blasts for event organizers, conference producers, festival operators and race directors who need a direct communication channel with the people who have registered or bought a ticket. Registration and ticketing are the moment the attendee connects once; from then on, parking, weather, schedule changes, venue instructions and emergency notices land directly on the attendee's phone or desktop screen instead of in an inbox they stopped checking on the way to the venue.
Yes. Blasts is connection-based, and DirectToAttendees is designed around the fact that an organizer already has a registration or ticketing relationship with every attendee and a natural moment, checkout, when it can invite them.
Connections can be established through an email invite link, a 4-digit connection code printed on a ticket, badge or wristband insert, or a personal invite link. Organizers with an opted-in registrant roster can send personalized invitations at scale.
By putting the event's invite link and 4-digit connection code into the registration confirmation, ticket email, know-before-you-go message and printed materials, and by inviting an opted-in registrant roster with personalized invitations. Attendees accept once and then receive Blasts through the iOS or Android app, a browser extension, or the web app.
Attendees always retain the ability to silently cut off the event. Step-by-step administrator instructions will be published in the DirectToAttendees event communication guide once confirmed against current Blasts documentation.
No. An attendee must approve the event's sender before any Blast is delivered. Blasts is built for existing relationships, which for DirectToAttendees means the people registered for your event who chose to connect.
Blasts have no per-message carrier fee, travel over encrypted tunnels rather than the carrier network, carry rich content such as maps, images and calendar attachments, show the organizer's name and photo, and report read acknowledgements from confirmed actions. They require a prior connection, which SMS does not.
Yes. Distribution lists let a sender name a group once, such as a track, a day, a wave or corral, a ticket tier or a volunteer team, and reach every member at the same time with no per-recipient cap. Large lists can be staggered into daily waves for pre-event content.
A typed Blast consumes one credit per recipient, so 5,000 credits; a voice Blast consumes two per recipient. Credits are prepaid, never expire, and are available at reseller pricing through BlastCredits.com, so unused credits roll into your next event.
The connection belongs to the attendee. They can disconnect silently at any time, and if they stay connected, the organizer can reach them again for results, surveys and next year's announcement. Individual Blasts auto-delete after 30 days, with an optional self-destruct timer from 1 hour to 30 days for time-boxed notices.
An iOS app, an Android app, browser extensions for Chrome, Edge, Brave, Opera, Vivaldi, Arc and other Chromium browsers, and the responsive web app at blasts.app.
DirectToAttendees is expanding into a full implementation resource for attendee communication on Blasts.
We're finishing the first edition now. Join the early-access list and we'll send it to you as soon as it's available.