A push notification reaches a person who installed a surface you own and who allowed alerts. It can nudge a deadline, a card, or a task they already started. It cannot reach the plant that never downloaded the app. If they do not have the app, you do not have a channel. Treating push as a substitute for SMS is how a headquarters campaign reports success and the floor never sees the date.
SMS still carries time-sensitive facts to phones you can text with consent, as laid out in text message employee communication. Teams reaches people who live in that desktop app, which Microsoft Teams benefits communication treats as a desk channel. Email alone fails the floor, which is the point of why email-only open enrollment fails. Push is a fourth surface. It is the one you may use only after an install.
When push is the right nudge
Use push for one purpose at a time. A deadline in the next 72 hours. A card that is ready. A form they started and did not finish. The person should already expect the app to talk about benefits. One action, one tap, a page that opens to the exact step. A push that lands on a home screen full of tiles wastes the tap.
Skip push for anything long, anything clinical, and anything you would be unwilling to have appear over a lock screen in a grocery line. Skip it for first-time education. A person will not learn an HSA from a banner. They might tap a banner that says enrollment closes Friday and their form is unfinished.
If the same news must reach people without the app, write the SMS or the shift briefing first. Then send push to the installed group as a convenience. SMS or the briefing remains the record for everyone else. Count the groups separately. A strong delivery rate inside the app says nothing about the warehouse.
Opt in, cap the frequency, hide the health detail
Ask for notification permission in a moment that makes sense: they just enrolled, they just saved a dependent, they asked to be reminded. Explain the one kind of alert you will send. A system prompt with no context gets denied, and you cannot keep asking.
Cap the frequency in writing. A workable default outside enrollment is a few pushes a month, and only when there is an action. During enrollment, a higher cadence is reasonable for people who have not finished, and it should stop when they finish. Suppress completed tasks. A push to someone who already enrolled is how they turn alerts off for good.
Lock-screen previews need a rule. No drug names, no diagnoses, no claim amounts, no “your therapy visit” language. The preview can say “Benefits deadline Friday” or “Your ID card is ready.” The detail waits inside the app, after unlock. If your tool cannot shorten the preview, do not send that message as a push. Use a vague preview plus an in-app message, or use a channel that is not painted across a lock screen. The same restraint shows up in specialty drug messaging: the ping is only the door.
Push, SMS, and Teams
Choose the channel from the audience in front of you. SMS: opted-in mobile numbers, including people with no corporate app, especially deskless and frontline crews. The message is short, urgent, and links to a page. Push: installed app, opted-in alerts, a nudge back to a task in that app. Teams: desk workers who already work there, a post or a chat that points to the same page. Email carries the longer note for people who read it. Put every deadline on a second channel as well.
When a text is too much, push is sometimes the calmer tap. A weekly SMS about a wellness article will burn the list. A single push inside an app they opened on purpose can point to the same article without using the phone number. That trade only exists for people who installed the app. Everyone else still needs the channel they actually have.
Do not stack all four on the same morning with the same words. Pick the primary channel per segment. Use a second channel only for people who did not act. Document the order in the campaign brief so the vendor, HR, and the plant supervisor are not all “just sending a reminder” on Thursday.
How you know the channel is real
Report installed users as a share of the workforce, by site, before you report push opens. If installs cluster at headquarters and the floor is missing, push is a convenience for that group. The rest of the company still needs a channel they already have. Set a target for install only if you are willing to staff the download: a QR at hire, a reason to install, and a person who can help on a shift.
Then report the action: enrollment finished, card viewed, or form submitted. Opt-out and alert-disable rates tell you when the cap was too high. The measurement guide keeps those diagnostics off the finance slide. If you need a place to run SMS, push, and the page behind both, LinQed Online is built for that split. See the product or talk with us before you announce a push program to people who will never see it.
Key takeaways
- Push reaches people who installed your app and allowed alerts.
- If they do not have the app, you do not have this channel. Use SMS or a briefing.
- One purpose per push: a deadline, a ready card, or an unfinished task.
- Opt in with a reason. Cap the frequency. Suppress people who already acted.
- No health details, drug names, or claim amounts on the lock screen.
- Report installs by site before you report push engagement.
Frequently asked questions
Can push replace texting the plant?
No. Push only hits installed apps. A warehouse that never downloaded it will not see the deadline. Use SMS, with consent, or a shift briefing for that group. Push can complement SMS for people who have the app. It cannot stand in for it.
What is allowed on the lock screen?
A generic cue: deadline, card ready, action needed. Leave out drug names, conditions, claim dollars, and anything that would expose a health fact to someone looking over a shoulder. Put the detail behind unlock, inside the app.
How often should we send pushes?
Few enough that alerts stay enabled. Outside enrollment, a handful a month, each with an action. During enrollment, remind people who have not finished, then stop when they do. A push after completion trains people to disable the channel.
What if almost nobody installed the app?
Then you do not have a push channel yet. Do not plan open enrollment around it. Build install into hiring and into a reason people want the app, and keep SMS and no-login pages as the path that works this season.
Use push only where the app is installed. If they do not have the app, you do not have this channel.
Kate transforms complex ideas into clear, actionable employee communications that drive behavior change, leading projects from strategy through production. A Texas A&M communications graduate and IABC member.
