What this helps you do
Blasts gives your company a direct channel to employees, with their consent. Each employee installs the free Blasts app once (the phone app for frontline staff, the browser extension for people at a desk) and connects to your company. After that, your notices arrive on their phone or computer, clearly marked as from your company, without depending on whether they open email. 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
Roll it out through channels you already control rather than waiting for a gathering: the IT announcement, the new-hire checklist, the intranet, a poster in each break room, a manager's shift huddle. Work site by site and shift by shift, and make the invitation part of onboarding so every new hire is connected in week one.
How to do it
- Open Connections in your Hub and click Sync connections once so your enrollment code is published.
- Put the enrollment code and QR code on the intranet, the new-hire checklist and the break-room board, or click Print the enrollment kit for a one-page poster with the three steps.
- Where the enrollment link is enabled for your Hub, paste that one standing link into the onboarding email and the intranet page: each person who opens it gets their own enrollment page.
- If your company controls its email domain, verify it once with a DNS TXT record. With Domain Auto-Approve on your company's Blasts account, people on your verified domain connect without you approving each request one by one. That is the bulk path for a workforce.
- For contractors, franchise staff or anyone without a company address, use Invite one person, or Add many at once with a pasted list or a roster export. Invitations are checked on Blasts and spread out at up to 200 a day.
- Point your onboarding form at the inbound webhook on Integrations, or use the Zapier app, so each new hire is invited on their start date.
- Accept requests under People who want to connect, or turn on auto-accept in Settings so employees are connected the moment they join.
Example
A distribution company with three sites and 900 employees publishes the DNS record, puts the enrollment code in the new-hire checklist and prints the kit for every break room. HR uploads the roster export for the warehouse crews who check email once a week; those invitations go out over the following days. Six weeks later the night shift at every site is reachable on the phones they already carry, so a 5 a.m. dock closure is one Blast instead of a phone tree.
Good to know
- Connecting is consent-based: an employee can mute or disconnect at any time. Domain Auto-Approve removes friction, not consent.
- Import columns: your file needs an email column. The Hub also recognizes name, first name, last name, phone, address, city, state or province, ZIP or postal code, country, manager, department, team, birthday, household, and interests (a column headed audiences, tags, groups or lists works too). Files are limited to 5,000 rows and 2 MB, and bad addresses, duplicates and dead domains are flagged in a preview before anything is sent.
- There is no HRIS, payroll or directory connector. Your roster reaches the Hub as a CSV export, through the inbound webhook, or through Zapier.
- The Reach funnel on Connections shows where every employee stands (known, invited, requested or connected) and how they arrived: code, import, webhook, request or Zapier.
- Settings has an Employees portal you can turn on; sign-in to it is limited to addresses on your work email domain.
- This is Blasts, not SMS: there are no carrier fees and no personal mobile numbers to collect or protect.