How to Receive Mobile Alerts in Azuga
Quick Summary
Azuga – Fleet Management Software & GPS Fleet Tracking Solutions lets fleet managers and drivers stay on top of vehicle activity the moment something happens, without having to sit in front of a dashboard all day. Azuga’s alert system watches for events such as speeding, hard braking, idling, and low device battery, then delivers that information through email, web notifications, and push notifications inside the Azuga FleetMobile app. This guide explains how mobile alerts work in Azuga, how to turn them on and configure the events that matter most to your fleet, and how to fix the most common reasons alerts stop arriving on a phone.
What Are Mobile Alerts in Azuga and Why Do They Matter?
An alert in Azuga is a notification sent whenever a vehicle or driver triggers a condition you’ve defined, such as exceeding a speed threshold, braking harshly, or idling longer than expected. Azuga can deliver that notification through three channels at once: email, a web notification visible through the bell icon in the browser dashboard, and a mobile push notification inside the Azuga FleetMobile app. Mobile alerts specifically matter because they reach the people who need them fastest, whether that’s a fleet manager away from their desk or a driver who needs an in-the-moment nudge about unsafe driving behavior.
Every new Azuga account starts with four default alerts already configured: Standard Idling Alert, Standard Low Battery Alert, Standard Speeding Alert, and Standard Stop Alert. These give a new fleet baseline visibility right away, but they’re only useful once notifications are actually turned on and routed to the right people’s phones. The sections below walk through enabling mobile delivery, configuring thresholds, and adding new alerts beyond the defaults.
What Do You Need Before Setting Up Mobile Alerts?
A short checklist beforehand keeps the setup process quick and avoids missed notifications later.
- An active Azuga account with administrator access to the Alerts page.
- The Azuga FleetMobile app installed and logged in on the phone that should receive alerts.
- Notification permissions enabled for the app at the device’s operating system level.
- A clear idea of which events matter most to your fleet, such as speeding, hard braking, or idling.
- A list of who should receive each alert – fleet managers, paired drivers, or both.
How Do You Turn On Mobile Alert Notifications?
Azuga treats mobile delivery as one of several notification channels attached to each alert, so enabling it happens inside the alert’s own settings rather than through a single global switch.
How Do You Enable Mobile Delivery for an Alert?
- Log in to the Azuga Fleet web application.
- Go to ADMIN, then select Alerts.
- Select the pencil icon beside the alert you want to update, or click Add Alert to create a new one.
- Locate the notification options and choose how you want to be notified: Web, Mobile, or Email.
- Toggle on the Mobile option so the alert also arrives as a push notification in Azuga FleetMobile.
- Save your changes to apply the update.
How Do You Choose Who Receives Each Alert?
Every alert also lets you define who should be notified, separately from which channel the notification travels through. The Send Alerts To field controls internal recipients, such as Group Admins or Paired Drivers, while the CC field can route a copy to people outside the Azuga system entirely. Review both fields whenever you enable mobile delivery. An alert configured to notify only a Group Admin will not reach a driver’s phone, even when you turn on the Mobile option for the alert itself.
How Do You Confirm Notification Permissions Are Enabled on Your Phone?
Turning on Mobile delivery inside Azuga is only half the setup – the phone itself also needs to allow the app to send push notifications. If this permission was declined when the app was first installed, alerts configured correctly in Azuga will still never appear on the device.
| Platform | Where to Check Notification Permissions |
| iOS (iPhone/iPad) | Settings, then Azuga FleetMobile, then Notifications – confirm Allow Notifications is turned on |
| Android | Settings, then Apps, then Azuga FleetMobile, then Notifications – confirm notifications are enabled |
It also helps to check that the app isn’t restricted by battery-saving or Do Not Disturb settings, since some phones silently suppress notifications from apps they consider inactive. Opening the Azuga FleetMobile app periodically, rather than leaving it untouched for weeks, generally keeps it in the phone’s active app list and reduces this kind of interference.
Which Events Can You Set Up as Mobile Alerts?
Beyond the four defaults every account starts with, Azuga supports a broader library of alert types that fleets commonly add once the basics are running smoothly.
| Alert Type | What Triggers It |
| Speeding Alert | Vehicle exceeds a defined speed threshold, often tied to the posted speed limit |
| Hard Braking Alert | Driver brakes abruptly, which is highly indicative of accidents or distracted driving |
| Idling Alert | Vehicle idles longer than the time threshold you configure |
| Low Battery Alert | GPS tracking device’s battery drops below a set level |
| Stop Alert | Vehicle stops at an unexpected location or for longer than expected |
| Geofence Alert | Vehicle enters or exits a defined geofenced area |
| Tire Pressure (TPMS) Alert | Tire pressure varies from the recommended level |
| Device Plugged In/Unplugged Alert | GPS tracking device changes state from plugged in to unplugged, or vice versa |
Azuga recommends enabling several of these beyond the out-of-the-box set to improve overall awareness of fleet activity, particularly Hard Braking and Geofence alerts, since both flag events that typically call for a fast response rather than a once-a-week review.
How Do You Add a New Alert From Scratch?
Creating a new alert follows a similar pattern to editing an existing one, with a few extra steps for defining the trigger condition itself.
- Go to ADMIN, then select Alerts.
- Select Add Alert at the top of the Alerts dashboard.
- Choose an Alert Type from the dropdown, such as Speeding or Idling.
- Edit the threshold and frequency details – for example, a speed limit or an idling duration.
- Set Send Alerts To and, optionally, CC recipients.
- Choose your notification channels: Web, Mobile, and/or Email.
- Toggle on the alert, then select Add Alert to save it.
Because thresholds set too tightly can flood recipients with notifications, it’s worth starting with Azuga’s suggested defaults and adjusting gradually. An idling alert set to trigger after just thirty seconds, for instance, will generate far more mobile notifications than most fleet managers want to review, while a threshold of five or ten minutes usually captures the idling patterns worth acting on.
How Do Drivers Receive and Use Mobile Alerts?
Drivers experience mobile alerts differently from fleet managers because Azuga FleetMobile limits their access to their own paired vehicle rather than the entire fleet. When a driver pairs with a vehicle, alerts configured for Paired Drivers arrive as push notifications on the driver’s phone in real time. These alerts provide immediate feedback on events such as hard braking or speeding instead of a delayed summary.
Azuga FleetMobile also uses badges and push notifications to highlight unsafe driving events as part of its scoring and rewards system. As a result, drivers may see the same event appear as an alert and affect their driver score, which reinforces the behavior the system aims to correct.When a driver pairs with a vehicle, alerts configured for Paired Drivers arrive as push notifications on the driver’s phone in real time. These alerts provide immediate feedback on events such as hard braking or speeding instead of a delayed summary. Azuga FleetMobile also uses badges and push notifications to highlight unsafe driving events as part of its scoring and rewards system. As a result, drivers may see the same event appear as an alert and affect their driver score, which reinforces the behavior the system aims to correct.
How Do You Confirm Mobile Alerts Are Working Correctly?
After setup, a short verification pass confirms alerts are actually reaching the phone rather than just being configured correctly on paper. Start by checking the bell icon inside Azuga FleetMobile, which shows a running list of alerts the app has received, and confirm recent events appear there as expected. Next, ask a driver or manager who should receive mobile alerts whether push notifications appear on their lock screen. An alert may appear in the app’s notification list without triggering a system-level push when the device has incorrect notification permissions. Finally, if you recently changed a threshold, allow a little time for a real event to occur naturally, or trigger a test scenario deliberately – such as a short test drive with mild braking – to confirm the new setting behaves as expected.
What Common Problems Come Up With Mobile Alerts?
A handful of recurring issues account for most mobile alert problems fleet managers run into. The table below summarizes them.
| Symptom | Likely Cause | Suggested Fix |
| No push notifications arrive on the phone | Notification permission disabled at the device level | Enable notifications for Azuga FleetMobile in the phone’s system settings |
| Alerts appear in the app but not as push notifications | Mobile channel not toggled on for that specific alert | Edit the alert in ADMIN and enable the Mobile notification option |
| Driver never receives an alert for their vehicle | Driver not correctly paired with the vehicle, or not listed under Send Alerts To | Confirm the driver-vehicle pairing and recipient settings for the alert |
| Too many notifications arriving | Threshold set too sensitively, such as a very short idling time | Adjust the alert’s threshold to a less sensitive value |
| Alert stopped working after a recent update | App notification permissions reset during an OS or app update | Recheck notification settings after major phone or app updates |
Conclusion
Mobile alerts turn Azuga from a dashboard you have to check into a system that reaches out when something actually needs attention. Getting them working reliably comes down to a short list of details: enabling the Mobile channel on each alert, confirming notification permissions at the device level, and setting thresholds that flag real issues without overwhelming recipients. Once configured, Azuga – Fleet Management Software & GPS Fleet Tracking Solutions keeps fleet managers and drivers informed the moment a speeding, hard braking, idling, or geofence event happens, wherever they are. Fleets that want help fine-tuning their alert strategy, or comparing Azuga’s mobile alerting against other fleet and CRM platforms, can also turn to Solution for Guru, a CRM and software implementation partner that supports businesses through software selection, configuration, and rollout.
Frequently Asked Questions
Yes. Mobile push notifications are delivered through the Azuga FleetMobile app, so it needs to be installed, logged in, and granted notification permissions on the recipient’s phone. Without the app installed, an alert configured for Mobile delivery simply has nowhere to send its push notification.
Yes. Each alert lets you toggle Web, Mobile, and Email independently, so nothing stops you from enabling all three at once for a single alert. Many fleets do exactly this for high-priority events like hard braking or geofence violations, so the notification reaches someone regardless of which channel they happen to be checking.
The most common cause is a notification permission that was declined when the app was first installed, which silently blocks push notifications even when the alert itself is configured correctly in Azuga. Check the phone’s system settings for the Azuga FleetMobile app, confirm notifications are allowed, and then verify the Mobile channel is toggled on for the specific alerts you want to receive.
