Cookie settings
Workforce Signal Review

Evidence, channels & privacy · U.S. English

Notification choices

One quiet phone can hide several different settings

Separate delivery preferences, phone presentation and employer expectations before changing how work messages reach you.

Editorial analysis. This publication cannot access accounts or provide employer support. Official-source links lead away from this site.

In this article

A silent phone is an observation. It is not an explanation. Start by naming the layer you want to change: what is sent, how it is shown or what response is expected.

Sending and showing are different controls

A service-side preference concerns the messages a service sends. A phone setting concerns how the device presents notifications. Muting a sound does not, by itself, tell you whether a service still sends messages. Changing one service’s preferences does not establish what a separate app will do.

Allied Universal’s Earn More page says LISA text offers are opt-in and their frequency can be customized. It does not give a complete current menu path or establish that a LISA change controls Mercury notifications. Use the actual current interface and applicable employer instructions rather than a tutorial that guesses at screen labels.

Describe the desired result first

“I want fewer interruptions” can mean several things: fewer offer messages, hidden lock-screen previews, quieter alerts, a different delivery channel or a clearer understanding of when a response is expected. Decide which outcome you mean before touching settings.

  • Volume: How often does the service send this category?
  • Visibility: Who can see the content on this device?
  • Attention: Does the device make a sound or display an interruption?
  • Work expectation: What, if anything, are you expected to do with the message?

Only the first three are technical descriptions. A phone’s permission screen cannot establish employment expectations. If the consequence of missing a notice is unclear, ask the appropriate employer contact before assuming a setting change changes an obligation.

Make a reversible observation

FICTIONAL EXAMPLE

A worker wants to hide message previews on a shared household tablet while retaining the ability to check notices privately. The observation to test is whether previews remain visible, not whether the employer considers a message read.

A useful personal note records the setting’s label, which device was changed and the time. It does not need the text of a shift offer, a site address or a coworker’s name.

Change one relevant setting at a time when possible. If several layers change together, the next result will be hard to interpret. Do not assume a quiet period proves a setting worked: there may simply have been no new notice.

Text opt-out instructions have a scope

The corporate privacy policy describes opting out of informational texts by replying “stop” or following the message’s opt-out instructions. That general policy does not establish which other communication channels remain active or which notice categories are connected. For an unverified sender, independently confirm the channel before interacting with the message.

Keep marketing subscriptions, shift-offer preferences, app permissions and ordinary employer communications conceptually separate. The fact that all may arrive on one phone is not evidence that one action controls them all.

When a preference does not behave as expected

Check the exact category and device you changed, then compare a later observation with the intended outcome. Ask a specific question: “Does this preference cover these offer messages, and when should it take effect?” Avoid asserting an outage or a privacy failure from one unexplained notification.

Our Cookie Settings governs this publication’s optional reading positions. It cannot change LISA, Mercury, SMS delivery, employer records or your phone’s notification settings. Read the app-privacy analysis before treating a device permission as a statement about an entire workplace system.

SOURCE NOTES / OCTOBER 16, 2026

Evidence behind this article

Public-source reporting and editorial analysis. No private account was inspected. Worked cases are fictional.

Have a public source that changes this analysis? Suggest a correction. Please don’t send private employee records, identity documents or account credentials.