Get members connected when they join or renew

Connect each member once at the moment they join, renew or register, and every notice after that lands.

What this helps you do

Blasts gives your organization a direct channel to members, with their consent. Each member installs the free Blasts app once (the browser extension at a desk, the phone app otherwise) and connects to your organization. After that, the meeting change, the nomination deadline and the renewal notice arrive on the screen they are already looking at, clearly marked as from your organization, instead of sitting under a week of list mail. The Hub picks the right path for each person: someone already on Blasts gets a request in the app; someone who is not gets your invitation email with the enrollment code.

When to use it

Joining and renewing are the moments. Put the invitation in the join confirmation, the renewal confirmation, the member portal and the event registration confirmation, and repeat it in person at the annual meeting, the chapter mixer and new-member orientation. Renewal season brings most of the membership past the offer once a year, which is why it works.

How to do it

  • Open Connections in your Hub and click Sync connections once so your enrollment code is published.
  • Add the enrollment code and QR code to the join and renewal confirmations, the member portal dashboard and the event registration confirmation.
  • Where the enrollment link is enabled for your Hub, paste that one standing link into those templates and your website: each person who opens it gets their own enrollment page.
  • Click Print the enrollment kit for the registration desk at the annual meeting, the chapter meeting table and the new-member packet. Chapter leaders can share the same code with their own members.
  • For members who never scanned, export the opted-in list from your membership system and use Add many at once or upload the CSV. Invitations are checked on Blasts and spread out at up to 200 a day.
  • Point your join form or renewal confirmation at the inbound webhook on Integrations, or use the Zapier app, so each new member is invited the day they join.
  • Accept requests under People who want to connect, or turn on auto-accept during renewal season.

Example

A 4,000-member society puts the code in the renewal confirmation in October and prints the kit for the annual meeting registration desk in November. In January the membership coordinator uploads the opted-in export for everyone who never scanned, and those invitations go out over the following days. By spring 2,900 members are connected, and the first meeting change reaches them the hour it is decided.

Good to know

  • Members do not share one email domain the way a company's staff do, so Domain Auto-Approve does not apply to a membership list. Every member connects individually.
  • The connection belongs to the person, not to the dues record: a member who lets a membership lapse and rejoins later is already reachable, and anyone can disconnect quietly at any time.
  • Import columns: your file needs an email column. The Hub also recognizes name, first name, last name, phone, address, birthday, household, and interests (a column headed audiences, tags, groups or lists works too). Files are limited to 5,000 rows and 2 MB, with a preview before anything is sent.
  • There is no connector to an association-management system. Your member list reaches the Hub as a CSV export, through the inbound webhook, or through Zapier.
  • This is Blasts, not SMS: no carrier fees, and no spreadsheet of members' mobile numbers to collect or pass around.

Do it in your Hub

Inside your Hub, Help shows this same article next to the screen it describes. Sign in at directtomembers.com or right here.