Blasts for conferences, festivals, races and galas
Gate moved. Room changed. Lightning hold. Packet pickup pushed to 4 p.m. Bus running forty minutes late. DirectToAttendees gives you a permission-based channel to the audience your registration platform produced, from the confirmation follow-up to next year's invitation.
Open today. Built on Blasts: connection-based, encrypted, no subscription, and credits never expire.
Most event tools live in one moment: the confirmation email, the day-of alert, the post-event survey blast. DirectToAttendees is built on a different shape. The attendee connects once, at registration, and that same connection carries the gate change, the weather hold and the thank-you.
Make arrival easy before anyone leaves home. The messages that prevent event-day problems land in the weeks and days when attendees are still planning, starting with the follow-up to the registration confirmation.
Run the event in real time. The room moved, the gate closed, the sky opened, the start is held. Updates reach the phone in the attendee's hand, sent to everyone or to only the audience the change affects.
Don't throw the audience away at load-out. The people you spent real money acquiring are still connected when the follow-through begins, and they stay connected only as long as they want to.
The connection underneath never changes: the attendee approved it once, at registration, and it carries all three phases.
Event communication isn't one problem. It's three, spread across the lifecycle: attention before, precision during, and retention after.
Parking moved to the north lot, the gate everyone knows is closed, and packet pickup shifted to Friday evening. The attendee opened the confirmation email three weeks ago and hasn't looked at it since, and the update you send today lands in the same inbox, under everything else. The message that would have prevented Saturday morning never gets read.
The room changed. 2,400 people don't need to know; the few hundred who chose that track do. With one audience for the track, the update reaches the phones in their hands, and everyone else keeps walking to the right rooms undisturbed.
The audience you paid to acquire has scattered. Thousands of known attendees drove home, and the organizer is back to hoping they open an email when next year's registration launches. The relationship ended at load-out, and it didn't have to.
Your Hub speaks event, not generic CRM. It opens with the audiences an event actually uses, and every update you send picks the audience it belongs to, so a corral-3 start change never wakes the whole field.
On their preferences page, attendees pick the days, tracks and interests they want updates about. A Track A attendee hears about Track A. Nobody learns to ignore your updates because every one of them was relevant to somebody else.
Your team assigns connected people to audiences too: speakers into Speakers, crew into Staff, sponsors into Exhibitors. A person can belong to as many audiences as apply, like Saturday, VIP and Track A at once, and the update goes only to the ones the change touches.
The starter set is a menu, not a mandate: keep what fits your event, rename or archive the rest, and add Day 2, Track A, Wave 1, Speakers or Exhibitors in seconds.
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, and it does not change how registration works.
Your Events Hub gives you one standing link and QR code. Drop it into the confirmation page, the ticket email, the know-before-you-go message and the packet or badge pickup sign. Your registration platform keeps doing exactly what it does now.
One tap, and the attendee gets their own secure page and approves your event, whether or not they already use Blasts. There is no mobile-number list to collect or maintain, and the page is closed to search engines.
The same connection carries the parking instructions the night before, the gate change at 7:10 a.m., the weather hold at the main stage, the room change 17 minutes before the session, and the results and next year's dates after it's all over.
Confirmed connections appear in your Events Hub: every connected attendee, on the phone in their hand, before, during and after the event.
Attendees opt in and can silently disconnect at any time, including the moment they leave the grounds.
There's another way
Blasts is the consent-based network underneath: 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. What you send from the Hub is a typed or rich message with images, links and up to three attachments, and it goes to the one audience the change concerns: the lightning hold to the people standing in it, the sponsor thank-you to everyone, later.
The sponsor newsletter still belongs in email, and it stays there. These are the messages that fail when they arrive late, each one sent to the audience it concerns, and each one able to go out as a Blast, as an email, or as both.
Which lot, which gate, where the shuttle is, when doors open, and what to do when the gate everyone expects is closed. Sent the evening before, again on arrival morning, and again the minute something moves, to the attendees arriving that day.
A moved keynote, a swapped stage time, a breakout relocated 17 minutes before it starts. Sent to the track, stage or wave affected, straight to the phone in their hand instead of an inbox they'll check at lunch.
Lightning delays, heat advisories, shelter locations, resumption times, all-clear notices, and the session or day you have to call off. Written and sent in the minute you know, to everyone on site or to the one stage affected, with the read count telling the production office how much of the field still has to be walked.
Medical tent locations, bag policy reminders, water station changes, course reroutes, and the lost-and-found notice for the phone handed in at the info booth. Short typed Blasts with a map image and a link.
The awards ceremony, the headliner set, the after-party, the packet-pickup window closing. Scheduled the day before to arrive fifteen minutes ahead of the moment itself, so the time reaches the attendee where they will actually see it.
Volunteers get the call sheet, staff get the radio-channel change, exhibitors get move-in timing, speakers get the green-room call, VIP holders get the reception details. Separate audiences keep operational traffic out of attendee channels.
An Event Campaign is a set of messages built around one date: yours. Set the event date once, add the messages that belong before it, on it and after it, and the Hub schedules them all around that date.
An organizer spends an enormous amount acquiring each attendee, and most of that investment evaporates at load-out: the audience scatters, and next year starts with an email list and hope. A Blasts connection persists until the attendee decides otherwise.
For an annual event, next year doesn't start from a cold list.
These aren't product modes. They're the same persistent connection and the same event-language Hub, applied to different lifecycles.
The keynote moved rooms, the 2 p.m. breakout swapped speakers, the shuttle to the offsite leaves from the north door instead. Track and session audiences mean each change reaches only the people standing up to walk somewhere.
Gate B is closed and everyone is being routed to Gate D. Lightning within eight miles, main stage held, shelter in the pavilion. All-clear, doors reopen at 9:15. Day-based audiences keep Saturday's crowd out of Sunday's notices.
Packet pickup extended to 8 p.m., the wave 3 start pushed fifteen minutes, mile 9 rerouted around a road closure, results posted. Corral and wave audiences mean the change reaches the runners it applies to.
Valet is full, use the garage on the east side. The program starts twenty minutes late. The auction closes in ten minutes. Donor and VIP audiences, and the thank-you that lands the next morning.
Move-in dock times changed, the education track moved to hall C, the floor closes an hour early tonight. Exhibitor, buyer and education-track audiences keep operational traffic separate from attendee traffic.
Day-specific audiences mean Saturday's instructions never wake Sunday's crowd, and attendees pick the days that apply to them.
Email is where confirmations, receipts and sponsor content live, and it stays that way. An important email can still be missed or filtered on the morning the gate moves. SMS is where carrier fees, opt-out rules and character limits live. An event app is a real asset for the attendees who installed it. A consent-based screen channel is a different kind of channel, built around the fact that the organizer already knows exactly who registered.
Blasts credits are bought once and never expire. One typed Blast to one attendee is one credit. 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 Blast appears on the attendee's screen with the organizer's name and photo, and delivered, read and replied counts come from confirmed attendee actions rather than tracking pixels. Email still matters, so each connected person chooses Blasts, email or both, and the Hub can send the same gate change on both legs from your event's own sending address. Email is metered separately in email credits, and a new Hub includes 50 of them.
Audiences per day, track, wave, role or interest mean the corral-3 start change does not wake every runner in the field, and attendees can pick the audiences that apply to them.
Every Blast shows the sender's name and photo, so an attendee knows on sight which event is talking to them. Attendees can revoke the event at any time without the organizer being notified. Messages auto-delete after 30 days, 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 attention | Open-tracking pixels only | Delivery only | Read and replied counts from confirmed actions |
| Attendee must have connected first | No | Consent required | Yes, by design; attendees can disconnect silently |
| Rich content (maps, images, links, files) | Yes | Limited | Yes: rich text, images and links, plus up to three attachments of 5 MB each |
Comparison reflects published Blasts.app product information as of September 2026 and general characteristics of email and SMS. Blasts is not an SMS product and does not send text messages. A cost model for your attendance and message volume is in 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. The attendee's control over the connection isn't a limitation we work around; it is why the channel stays trusted enough to work at 7:10 on a gate-change morning.
For the person who will set it up
For the registration lead or operations manager who will run it. Nothing here changes how your registration or ticketing platform works.
An existing operator signs in at /hub/signin/ with an email code, a passkey or a Blasts sign-in. A new organization sets up its Hub through guided onboarding after signing in, and the Hub activates with the organization's first credit purchase from BlastCredits. Invite the rest of the production office and give each person the access their job needs.
The Hub gives your event one standing enrollment link and one QR code. Paste the link into the registration confirmation page, the ticket email and the know-before-you-go message, and print the QR on the packet-pickup sign, the badge insert and the arrival signage. Each attendee who opens it gets their own one-time secure page, and that page is closed to search engines by design.
Three doors, and they are generic on purpose. Import a CSV export from your registration system. Point any form, CRM or Zapier at the Hub's inbound webhook so new registrants land in the Hub as they sign up. Subscribe to signed outbound events to push delivery, read and reply activity back into the systems you already run. There is no built-in connector for a specific ticketing or registration platform, and a Zapier private app is available on request if you want that door to be easier.
Start from the event audience menu (All Attendees, VIP, Volunteers, Staff & Crew, Exhibitors & Vendors, Future Events) and add the days, tracks, waves, corrals, speakers and roles your event needs; attendees can also join the audiences that apply to them from their preferences page. From the composer, send a typed or rich message with maps, images and links and up to three attachments of 5 MB each, ask for a YES or NO reply and let the Hub count the answers, and read what comes back in one conversation thread. Schedule the know-before-you-go ahead of time, repeat a weekly briefing, or send the gate change the moment it is decided. Each connected person chooses Blasts, email or both, and the Hub can send the same notice on both legs; email is metered in email credits, with 50 included in a new Hub. Blasts itself, the platform underneath, also carries campaign badges such as Emergency, voice Blasts and events with a countdown and calendar attachment when a message is sent from the Blasts app; what the Hub composer sends is the typed and rich message described here.
Event Campaigns and Journeys are part of Hub Pro, which unlocks at $500 in cumulative credit purchases from BlastCredits for any organization. Everything the day-of actually needs, sending, audiences, Content Series, conversations, roles and the email leg, is included from the start, so a gate change on your first weekend does not wait on anything.
Hub behaviour described here is documented at blastshub.com/en/docs/for/events/. Blasts itself, the network, the app and the connection, is documented by Blasts at blasts.app, and this page reflects that published documentation.
In one paragraph
DirectToAttendees is the event organizer's front door to the Blasts Hub, for conference producers, festival operators, race directors and gala teams. Your registration or ticketing platform still owns registration; DirectToAttendees is about the messages that come after it. An attendee connects once from the confirmation, and the organizer has a permission-based channel for the moments that matter: the know-before-you-go and parking instructions, the gate change on arrival morning, the room change 17 minutes before a session, the weather hold and the all-clear, the delay, the cancellation, the lost-and-found notice, the session starting in ten minutes, and the thank-you, results and next-year invitation after everyone drives home.
If your organization already has a Hub, sign in at /hub/signin/ with an email code, a passkey or your Blasts sign-in. A new organization sets up its Hub through guided onboarding after signing in, and the Hub activates with its first credit purchase from BlastCredits. Hub Pro, which adds Journeys and Event Campaigns, unlocks at $500 in cumulative credit purchases for any organization.
No. Your registration platform still sells the tickets, takes the money and sends the confirmation. All you add is one standing link and QR code from your Hub, placed in the confirmation page, the ticket email, the know-before-you-go message and the packet-pickup or badge signage. Each attendee who opens it gets their own secure page and approves your event, whether or not they already use Blasts.
Through generic doors, and honestly: there is no built-in Hub connector for any specific ticketing or registration platform. What the Hub gives you is a CSV import for your registrant export, an inbound webhook that any form, CRM or Zapier can post new registrants to, signed outbound events so delivery, read and reply activity flows back to your systems, and a Zapier private app on request. Separately, the Blasts platform itself integrates with Zapier, Salesforce, HubSpot, Dynamics 365, Stripe, PayPal and others.
No, and it shouldn't. Confirmations, receipts and the sponsor newsletter belong in email, and an important email can still be missed or filtered on the morning the gate moves. Each connected person chooses to receive Blasts, email or both, and the Hub can send the same gate change on both legs from your event's own sending address. Email is metered in email credits, and a new Hub includes 50.
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 short connection code, or a personal invite link. The Hub's own standing link and QR is the path most organizers use, because it goes wherever the confirmation already goes.
Yes. Create an audience per track, day, wave, corral, ticket tier or crew role, and each update goes only to the audience it concerns: the corral-3 start change to corral 3, the hall C relocation to the education track. Attendees can also choose their own days, tracks and interests from their preferences page, so relevance doesn't depend on your team sorting thousands of people by hand.
A Blast to the audience the change affects, the minute you know. A weather hold, an evacuation, a start-time change or a cancellation goes to everyone standing in it; a gate change or a moved room goes only to the people walking there, which is what keeps a whole-event send worth reading. Attachments carry the map or the reroute, replies come back into one conversation thread, and the delivered and read counts tell the production office how much of the site still has to be covered on foot.
Yes. That is the core of DirectToAttendees: the attendee connects once, and the same connection carries know-before-you-go content in the weeks before, day-of updates during, and thank-you, results, surveys and next year's announcement after. An Event Campaign, part of Hub Pro, lets you plan the arc around the event date once; if the date moves, the pending messages move with it. Day-of updates never depend on that: they are ordinary sends, included from your first day.
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. Next year's invitation reaches the ones who were still connected when you sent it.
Blasts is not an SMS product and sends no text messages. Blasts have no per-message carrier fee, travel over encrypted tunnels rather than the carrier network, carry rich content such as maps, images, links and file attachments, show the organizer's name and photo, and report read and replied counts from confirmed actions. They require a prior connection, which SMS does not.
A typed Blast consumes one credit per recipient, so 5,000 credits. Credits are prepaid, never expire, and are available at partner 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. This year's day, track and wave audiences can simply be archived when they're done. Individual Blasts auto-delete after 30 days.
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.
The Hub is shared across Blasts verticals and documented in one place. The event version is at blastshub.com/en/docs/for/events/, which covers connecting attendees, audiences, sending, email, conversations, event campaigns, roles, integrations and credits in event language, and the shared topics sit alongside it at blastshub.com/en/docs/. Blasts itself, the app and the connection, is documented by Blasts at blasts.app, and DirectToAttendees pages reflect that published documentation.
DirectToAttendees is the implementation resource for attendee communication on Blasts, and the library keeps growing.
A practical guide to the messages an event actually has to land: where to put the connection invitation at registration, ticketing and packet pickup, how to structure audiences by day, track, wave and role, the wording for a gate change, a room change, a weather hold, a delay and a cancellation, and a day-of send plan for the production office. Tell us a little about your event and we'll send it over.