What multi-channel notifications are
Multi-channel notifications send the same alert down more than one path at the same time. When a device triggers an SOS, crosses a geofence, or misses a check-in, the Hub can push that alert out by email, SMS, voice call, WhatsApp, and a webhook into another system all at once. You set it up once per team or per device, and it runs from then on without anyone remembering to forward anything.
A single channel can fail quietly. Email lands in a spam folder. A phone sits on silent in a bag. A duty manager hands off a shift and the contact list never gets updated. None of those failures announce themselves, so the alert looks like it went out even though nobody read it. Sending the same alert down several paths at once means one weak link does not decide whether your team hears about an emergency.
What teams use them for
Most organizations set these up for one of three reasons.
-
Safety escalation. An SOS needs to reach a real person fast, and it needs to reach them more than one way. A common setup sends an SOS to the on-call phone by voice call, to the same phone by SMS with a location link, and to a shared safety inbox by email. The voice call wakes someone up. The SMS link gets them a map without logging in. The email leaves a record.
-
Operational awareness. Not every alert is an emergency. Geofence crossings tell a dispatcher a crew arrived on site or left a restricted area. Check-in events confirm a lone worker is still fine. These usually go to email or a group chat rather than waking anyone at night.
-
Feeding another system. If your organization runs its own dispatch software, incident log, or dashboard, the HTTPS webhook channel pushes the event straight into it. That way the alert shows up where your team already works instead of in a separate tool nobody has open.
Set these at the team level when you can. Team-level notifications apply to every device on that team, so you do not have to repeat the setup each time a new device is assigned. Use device-level notifications for the exceptions, such as a single crew working in a higher risk area.
Before you start
Make sure you have:
- Access to the EVERYWHERE Hub with admin permissions
- The phone numbers, email addresses, or webhook URL you want alerts sent to
- Phone numbers written in full international format, starting with + and the country code
Step 1: Log In to the Everywhere Hub
-
Go to www.everywhere-hub.com and sign in using your username and password.
Step 2: Open the Devices Page
-
From the main menu, select Devices.
Step 3: Select the Team or Device you would like to Edit.
(Highlight shows device selection.)
Step 4: Navigate to "Notifications" Section
For Team Adjustments :
For Individual Device Adjustments:
Step 5: Select the Blue + Icon
Step 6: Toggle "ON" the events you would like Notifications for.
Step 7: Select Desired Notification Channel
-
- Email. Sends a preset alert by email.
- Voice. Places an automated voice call.
- SMS. Sends a text message to a mobile number.
- SMS with link. Sends a text message that includes a link to the location of the event.
- Patriot. Available in New Zealand only.
- WhatsApp. Sends the alert to a WhatsApp number.
- HTTPS. Sends the alert into another system by webhook.
Phone number format: SMS and voice numbers must include the + sign and the country code. For example, +14435557681. A number entered without the country code will not deliver.
Step 8: Double Check & Click "Save"
Your alerts will now go out through all selected channels.Choosing the right channels
Each channel has a different strength. Match the channel to how urgent the event is and where the person receiving it will be.
| Channel | Best for | Keep in mind |
|---|---|---|
| Voice | Automated voice message. Quick and simple. | Needs the + and country code. A missed call leaves no detail behind, so pair it with SMS or email. |
| SMS with link | Getting someone a location fast without asking them to log in. | Needs the + and country code. The recipient needs data or Wi-Fi to open the link. |
| SMS | A short, reliable heads up that works on almost any phone. | Needs the + and country code. |
| Keeping a written record and reaching a shared team inbox. | Slower to be seen. Ask IT to allowlist the sender so alerts do not land in spam. | |
| Teams outside North America who already coordinate in WhatsApp. | The recipient needs an active WhatsApp account on that number. | |
| HTTPS webhook | Pushing events into your own dispatch tool, incident log, or dashboard. | Someone on your technical team needs to build the endpoint that receives it. |
| Patriot | Monitoring center integration in New Zealand. | Available in New Zealand only. |
Common mistakes to avoid
Most notification problems we see in support come down to one of these.
- Leaving off the country code. This is the single most common reason an SMS or voice alert never arrives. Always enter the number as +[country code][number].
- Sending everything to one person. If every alert goes to one manager, the system goes dark the moment that person is on a plane, on leave, or off shift. Add a second recipient or a shared inbox.
- Turning on every event. Alert fatigue is real. If the team gets fifty geofence pings a day, they will stop reading them, and the SOS will be sitting in the same pile.
- Setting it up and never testing it. Run a test event after you save so you know the alert actually lands. Do not find out during a real emergency.
- Never revisiting the list. People change roles and phone numbers. Review your notification recipients on a set schedule so the list matches who is actually on call today.
Need help? If an alert is not arriving after you have checked the number format and the saved settings, contact EVERYWHERE Support with the device name, the event type, and roughly when the event happened. That lets the team trace it in the logs.