What this helps you do
Blasts gives your community a direct channel to the people who live there, with their consent. Each resident installs the free Blasts app once and connects to your community. After that the water shutoff, the entry a technician needs, the gate that failed, the amenity closure and the community calendar land on their phone, clearly marked as from your office, instead of in a portal nobody logs into. 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
Put the invitation at the moment the relationship starts: the lease signing or closing packet, the move-in checklist, the welcome email, the association onboarding letter. Then repeat it where residents stand still: the lobby board, the mail room, the amenity doors, the office counter and the community website. Do it once per move-in and the connection carries for the whole tenancy.
How to do it
- Open Connections in your Hub and click Sync connections once so your enrollment code is published.
- Print the enrollment kit and post it in the lobby, the mail room, the elevator frames and beside the amenity doors.
- Put the enrollment code, or the standing enrollment link where it is enabled for your Hub, into the move-in packet, the welcome email and the association onboarding letter.
- Each resident installs Blasts on their phone, opens Settings, enters the code and taps Join.
- For the residents already living there, export your opted-in resident or owner list 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 move-in form or community website form at the inbound webhook on Integrations, or use the Zapier app, so each new resident is invited the day they take the keys.
- Accept requests under People who want to connect, or turn on auto-accept in Settings so residents are connected the moment they join.
Example
A 280-unit community puts the code in the move-in packet and the kit in both lobbies, then imports the opted-in resident list the office already keeps. Six weeks later 210 residents are connected, so when a riser fails on a Monday afternoon, Building B hears about the shutoff before anyone gets home and the office takes four calls instead of forty.
Good to know
- Connecting is consent-based: a resident can mute or disconnect at any time, and the office is not told. A lease or an association membership is not consent to message someone here; the resident joins.
- 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 property-management, work-order or access-control connector. Your resident list reaches the Hub as a CSV export, through the inbound webhook, or through Zapier.
- Two people in one unit are two connections. Group them as a household on the person page so a mailing can be held to one copy.
- The Reach funnel on Connections shows where every resident stands (known, invited, requested or connected) and how they arrived: code, import, webhook, request or Zapier.
- This is Blasts, not SMS: no per-message carrier fee, and no mobile numbers to collect or keep current after a move-out.