What this helps you do
Your notices reach employees in two ways. By email, from your first send, with nothing installed: an employee on your opted-in list receives every notice sent to an audience they are in. On Blasts, when an employee chooses to connect with your company on a device they choose: once that connection uses the same email address you have for them, their messages move there on their own. Nobody is required to install anything, and you never manage two lists.
When to use it
Set this up before the first real workday change, so the first notice people get is not a closure. Work through the channels you already control: the onboarding packet, the intranet, the break-room board, a lead's shift huddle.
How to do it
- Open Employees and choose Import. Upload a CSV of the employees who agreed to receive your notices. Only the email address, the name and an audiences column are kept; every other column is discarded before anything is saved. Confirm they agreed, and each one can receive by email from your first send.
- For one new person, post them through the inbound webhook on Integrations (the same rules apply). Adding one address by hand with Invite one person sends an invitation instead of making a subscriber.
- Click Sync connections once so your enrollment code is published, then put the code, the QR code or the printed kit where employees already look. Anyone who uses Blasts enters the code in the app, which sends your company a connection request.
- Accept requests under People who want to connect, or turn on auto-accept in Settings.
- Put each person in the audiences for their assignment (see Organize by assignment).
Example
A facilities company imports its opted-in list with an audiences column naming North Yard, Eastgate Depot and Night Shift, audiences it created first. Everyone on the list receives the next closure notice by email. Over the following weeks some employees enter the enrollment code in Blasts with the same address the company has for them, and their notices start arriving on Blasts without anyone doing anything.
Good to know
- The move to Blasts needs the SAME email address. If an employee connects on Blasts with a different address (say a personal address when you imported a work address), that is a separate person here: the audiences the first address is in do not move to it, and the first address keeps receiving by email. Marking the two addresses as the same person on the person page does not stop duplicates across channels: if the work address receives by email and the personal address on Blasts, both receive the notice. The mark only skips the second address when both would receive the same Blast, and the audiences still don't carry over.
- A work address or a personal address can both be used, as long as your company has the employee's agreement to reach them there. Don't import addresses you don't have permission to use.
- Connecting is consent-based: an employee can stop at any time.
- Invitations are spread out at up to 200 a day.
- There is no HRIS, payroll, scheduling or directory connector. Your list reaches the Hub as a CSV export, through the inbound webhook, or through Zapier, and nothing here knows who works for you.
- The employees portal in Settings has nothing for employees to do yet. Preferences and connecting on Blasts work without it.