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: cleaned and previewed first. When you confirm the people on it agreed to hear from you, each new address becomes an email subscriber right away, and invitations to connect on Blasts go out at up to 200 a day. Without that confirmation the list is invited only.
- Inbound webhook: one URL your website form, CRM or Zapier can post a new person to. A new address becomes an email subscriber right away, unless the post sets email_optin to false, and is invited to connect on Blasts within the same daily limit.
When to use it
Pick the door that meets people where they are: the code and QR for a room or a screen, the kit for print, the enrollment link for emails and your website, CSV for a list you already have, the webhook for a form or a system that already knows who is new.
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
A property manager prints the kit for every lobby, puts the code in the move-in email, uploads the resident CSV once, and points the online maintenance form at the inbound webhook so every new tenant starts receiving by email, and is invited to Blasts, the day they sign. Four doors, one connected list.
Good to know
- Whichever door a person uses, they choose among the audiences you leave open to them; audiences you assign are set by your organization, and an import or webhook can only name ones that already exist. Anyone can stop at any time: mute or disconnect in Blasts, or reply STOP.
- Each invitation records its state: not on Blasts yet and emailed, on Blasts and waiting for approval, connected, or expired after 30 days.
- 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.