What this helps you do
There are several doors into your organization on Blasts, and they all lead to the same consent-first connection. Which one you use depends on where your people already are: in a room, on your website, on a list, or in another system.
- Enrollment code: the code people type into the Blasts app under Settings to join you. Published the first time you Sync connections.
- QR code: the same thing, scannable. Shown on Connections and in the printable enrollment kit.
- Enrollment kit: a print-ready page with the code, the three steps, and the audiences people can choose from.
- Enrollment link: where enabled for your Hub, one standing link gives each person who opens it their own enrollment page. Place it in sign-up confirmations, emails, printed materials and signage.
- Connection request: invite one person by email; on Blasts they approve in the app, otherwise they get your invitation email.
- Paste a list or upload a CSV: many invitations at once, cleaned and previewed first, spread out at up to 200 a day.
- Inbound webhook: one URL your website form, CRM or Zapier can post a new person to; they are invited the same way as an import.
When to use it
For an event, two doors carry almost everything. The standing enrollment link goes wherever registration already sends people: the confirmation page, the ticket email, the know-before-you-go message, your website. The printable kit goes wherever attendees stand still: badge inserts, packet pickup, the information desk, venue signage. CSV and the inbound webhook pick up the people those two miss.
How to do it
- Open Connections and click Sync connections once to publish your code.
- Copy the code and QR from Grow your connections, or click Print the enrollment kit.
- Use Invite one person or Add many at once for people you have addresses for.
- Open Integrations for the inbound webhook URL and the fields it accepts.
- Accept requests under People who want to connect, or turn on auto-accept in Settings.
Example
An organizer puts the enrollment link in the ticket confirmation, prints the kit for the packet-pickup table and the information desk, and points the registration form's confirmation step at the inbound webhook. Three doors, one connected audience, and the parking notice on Friday night reaches people who registered in March and people who bought a ticket that afternoon.
Good to know
- Whichever door a person uses, they still choose their own audiences, and they can mute or disconnect at any time.
- Your ticketing platform owns registration; there is no ticketing connector. The Hub communicates with the audience registration produces.
- Each emailed invitation records its state: not on Blasts yet and emailed, on Blasts and waiting for approval, connected, or expired after 30 days. People who use the standing link connect directly and never appear as pending invitations.
- Rotate the inbound webhook token from Integrations if it ever leaks; everything posting to the old URL stops until the new token is pasted in.
- The Reach funnel on Connections shows the source of every connection: code, import, request, webhook, Zapier or connector.