The email most people didn't open
Benefits enrollment closes Friday. The reminder went out Monday to 900 inboxes and sat under vendor newsletters and calendar invites. Half the workforce learns about the deadline from a coworker.
Blasts for the workplace
When everyone needs to know, don't hope everyone checks email.
Create a direct Blasts communication channel with your workforce for important HR, operations, security and company communications. Messages land on the screen, not in a crowded inbox.
Built on Blasts. Connection-based, encrypted, no subscription required.
Three situations every employer recognizes
Company communication fails quietly. Nobody tells you they didn't see the message; you find out later.
The site that closed at 6 a.m.
Weather, a power outage, a security incident. Operations needs every person on the early shift to know now, and the only tools available are a group text that half the team muted and an email that will be read at 9.
The frontline that never sits at a desk
Warehouse, retail floor, field crews, drivers, clinical staff. They have company email addresses they check once a week. Important information reaches the office and stops there.
There's another way
Connect once. Communicate directly.
Blasts is built around persistent connections between parties that already know each other. An employee connects with the organization once. From then on, the organization has a direct, encrypted channel that shows the message on the employee's phone or desktop screen, with the sender's name and photo, and an Emergency badge when it matters.
- A connection must exist before a Blast can be delivered. Employees can't be Blasted by organizations they haven't connected with.
- Messages travel over an encrypted Blasts connection, not through email servers or SMS carriers.
- Employees keep control: they can mute, set quiet hours, or disconnect at any time.
- Delivery, read and reply counts come from confirmed actions, not tracking pixels.
How your organization gets connected
This is where DirectToEmployees is unusually strong. You already know exactly who works for you, and you already own your company email domain. Blasts turns both into one connection per person.
Verify your company domain
Prove once that your organization controls @yourcompany.com. That verified domain is what lets Blasts recognize everyone on it as yours, without a per-person invitation campaign.
One connection across the devices they already use
Each employee connects once, and Blasts reaches them on the phone or desktop they already work from, whether that is a warehouse handset or an office browser.
Reach the whole workforce directly
Send to everyone, a site, a shift or a department. The message shows on the screen with the sender's name and photo, and an Emergency badge when it matters.
Everyone who needs to know, on the screen they are already looking at.
Domain Auto-Approve removes friction; it does not remove consent. Every employee can silently cut off a sender.
What employers use a direct channel for
Not every message belongs on the screen. These do.
Emergency and safety alerts
Site closures, severe weather, security incidents, evacuation instructions. The Emergency badge pins the message and pulses red.
HR deadlines and open enrollment
Benefits windows, policy acknowledgements, payroll changes and W-2 availability, with a poll or reply to confirm receipt.
Shift and schedule changes
Coverage requests, overtime opportunities, last-minute changes for a specific site or shift list.
IT and security notices
Phishing warnings, mandatory updates, outage status. Sent from a verified internal sender rather than an email that looks like phishing itself.
Leadership and culture
A 90-second voice Blast from the CEO after quarterly results, auto-transcribed for people who prefer to read.
Events and all-hands
Town halls, training sessions and site events, delivered as a Blast with a countdown and a calendar attachment.
Why this deserves a place beside email and SMS
Email is where documents live. SMS is where carrier fees and opt-out rules live. Neither was designed for an organization that already knows exactly who it needs to reach.
No per-message carrier fees
Blasts credits are bought once and never expire, with no monthly subscription. One typed Blast to one employee is one credit; a voice Blast is two. There is no per-message carrier bill.
Reach that doesn't depend on inbox habits
The message appears on the screen with the sender's face and name. Read acknowledgements tell you who has actually seen it.
Fast to deploy across a whole workforce
One connection per person, on the devices they already use, organized by your verified company domain instead of a per-person invitation campaign.
Built on cryptography your IT team can inspect
Blasts.app publishes the key exchange (ECDH P-256) and cipher (AES-256-GCM); keys are exchanged once at pairing and stored locally. Messages auto-delete after 30 days with an optional self-destruct timer, outbound DLP scanning catches sensitive patterns such as Social Security and card numbers, and there are no tracking pixels.
Email vs. SMS vs. Blasts for internal communication
| SMS | Blasts | ||
|---|---|---|---|
| Reaches people who don't check email | Depends on whether the person opens email | Yes, if you have consented mobile numbers | Delivered to the connected person's phone or desktop screen |
| Per-message carrier cost | Low | Per message, per carrier | One prepaid credit per typed Blast; credits never expire |
| Confirms who actually saw it | Open-tracking pixels only | Delivery only | Read acknowledgements from confirmed actions |
| Recipient must have connected first | No | Consent required | Yes, by design |
| Encrypted in transit | Varies | No | ECDH P-256 + AES-256-GCM |
Comparison reflects published Blasts.app product information as of August 2026 and general characteristics of email and SMS. Detailed cost modelling for your headcount will be part of the implementation guide.
Built for the relationships you already have
Blasts is not a way to message strangers, and DirectToEmployees does not pretend otherwise. It is built for the one audience an employer knows completely: its own people. That constraint is exactly what makes the channel trustworthy for the person receiving it.
- Employees connect once; the organization does not need to collect or manage personal mobile numbers.
- The employee can mute, set quiet hours, or disconnect without asking anyone.
- When someone leaves the organization, the connection can end with them.
For the person who will set it up
Implementation detail: how the workforce connection is built
For the IT or internal-communications owner who will set this up. Everything below reflects published Blasts documentation.
Publish the DNS TXT record
Add a TXT record of the form blasts-verify=<hex> to your company domain, the same kind of record used for email authentication. This proves your organization controls @yourcompany.com.
Enable Domain Auto-Approve
With the domain verified, people on the same corporate email domain auto-connect with the organization's Blasts sender instead of approving invitations one by one. Blasts.app describes this as scaling to a million or more members. Employees keep their silent cut-off rights.
Cover people outside the domain
Contractors, franchise staff or anyone without a company address connect the standard way: an email invite link, a 4-digit connection code shared verbally, or a personal invite link (blasts.app/connect/[ID]). An opted-in roster can be invited at scale with personalized invitations through Amazon SES, Microsoft Graph or Gmail.
Choose the receiving surface
Desk staff add the browser extension (Chrome, Edge, Brave, Opera, Vivaldi, Arc and other Chromium browsers). Frontline staff use the iOS or Android app, or the responsive web app at blasts.app.
Build distribution lists and badges
Create lists by site, shift, department or role; there is no per-recipient cap and large lists can be staggered into daily waves. Emergency Blasts pulse red and auto-pin to the top; Event Blasts carry a countdown and a calendar attachment; polls and voice Blasts are available for acknowledgement and leadership messages.
Exact administrator steps for domain verification and Domain Auto-Approve, and any first-connect consent prompt, will be documented in the implementation guide once confirmed against current Blasts documentation.
In one paragraph
What is DirectToEmployees?
DirectToEmployees is an implementation of Blasts designed for organizations that need a direct communication channel with an existing workforce. Because the employer already knows who its employees are, and can verify its own email domain, the existing employment relationship becomes the foundation for a connected, direct channel that does not depend on inbox habits or SMS carriers.
Direct answers
Do employees have to be connected before they can receive a Blast?
Yes. Blasts is connection-based. DirectToEmployees is designed around the fact that employers already have an established relationship with their workforce and can organize deployment around that existing employee base.
Connections can be established through an email invite link, a 4-digit connection code, a personal invite link, or, for organizations that verify their email domain, Domain Auto-Approve.
How does an employer establish Blasts connections with employees?
By verifying the company email domain with a DNS TXT record and enabling Domain Auto-Approve, so people on the same corporate domain auto-connect with the organization's sender. Employees then receive Blasts through the browser extension or the iOS/Android app.
Employees keep the ability to silently cut off the sender. Step-by-step administrator instructions will be published in the DirectToEmployees implementation guide once confirmed against current Blasts documentation.
Can we Blast a purchased list or people who don't work for us?
No. A recipient must approve the sender before any Blast is delivered. Blasts is built for existing relationships, which for DirectToEmployees means your workforce.
How are Blasts different from SMS for employee alerts?
Blasts have no per-message carrier fee, travel over encrypted tunnels rather than the carrier network, show the sender's name and photo, and report read acknowledgements from confirmed actions. They require a prior connection, which SMS does not.
What does it cost to send a Blast to 1,000 employees?
A typed Blast consumes one credit per recipient, so 1,000 credits; a voice Blast consumes two per recipient. Credits are prepaid, never expire, and are available at reseller pricing through BlastCredits.com.
Is Blasts secure enough for internal company communication?
Blasts.app publishes the following: peer-to-peer encrypted tunnels using ECDH P-256 and AES-256-GCM, keys stored locally, messages auto-deleted after 30 days with an optional self-destruct timer, outbound DLP scanning, and no tracking pixels. Your security team should evaluate these against your own requirements.
Which devices can employees receive Blasts on?
Browser extensions for Chrome, Edge, Brave, Opera, Vivaldi, Arc and other Chromium browsers; an Android app; an iOS app; and the responsive web app at blasts.app.
Do we need a subscription?
No. Credits are one-time deposits with no monthly subscription requirement, and they never expire.
Resources in preparation
DirectToEmployees is expanding into a full implementation resource for workforce communication on Blasts.
- The DirectToEmployees Implementation Guide: domain verification, Domain Auto-Approve, list structure and rollout sequencing
- Rollout templates: IT announcement, manager talking points, frontline install instructions
- Cost model: Blasts credits vs. SMS at your headcount and message frequency
- Distribution list patterns for multi-site, multi-shift organizations
- Emergency communication playbook
- Organization pricing through BlastCredits.com
Get the Free Employee Implementation Guide
We're finishing the first edition now. Join the early-access list and we'll send it to you as soon as it's available.