How to Configure Arrival and Departure Alerts in Samsara
Quick Summary
Knowing exactly when a vehicle reaches a customer site, or when it finally leaves, saves dispatchers from constantly checking the map and gives customers accurate updates without a phone call. Samsara builds arrival and departure detection directly into geofences and route stops, then lets administrators layer alerts on top so the right person gets notified the moment it matters. This guide walks through how that detection works and how to configure alerts around it.
Since these alerts depend on the broader location and routing tools built into the platform, it helps to understand the system behind them first. Samsara – GPS Fleet Tracking Software provides the GPS hardware, geofencing, and dispatch tools that arrival and departure alerts rely on, and it offers useful context before working through the configuration steps covered in this article. With that framing established, let’s look at how Samsara actually detects arrivals and departures.
How Does Samsara Detect an Arrival or Departure?
What determines when a vehicle is considered “arrived”?
Samsara relies on geofences to determine a vehicle’s status at a route stop, and the default logic is more precise than it might first appear. By default, a route stop is marked as arrived only once a vehicle has remained inside that stop’s geofence for two consecutive minutes. This short buffer prevents a vehicle simply passing near a location, without actually stopping, from triggering a false arrival. It also means a driver who briefly pulls into a lot to check a delivery address, then leaves without actually completing the stop, won’t accidentally register as having arrived.
What determines when a departure gets recorded?
Departure follows a similar logic, but with a shorter threshold. Once a vehicle leaves the stop’s geofence and remains outside it for 30 consecutive seconds, Samsara records the departure. This asymmetry between the two-minute arrival buffer and the 30-second departure buffer exists because arrivals are more prone to false positives from vehicles passing nearby, while departures are less ambiguous once a vehicle has clearly left the area.
Can these thresholds be adjusted?
Yes. Both the arrival and departure thresholds can be customized through Dispatch Settings rather than staying fixed at their defaults. This flexibility matters for fleets operating in dense urban environments, where geofences might sit close together, or for large industrial sites where a vehicle might briefly leave a large geofence boundary without actually completing its stop.
How does a full route’s start and end get determined?
Beyond individual stops, Samsara also applies geofence logic to determine when an entire route begins and ends. A route is considered started once a vehicle leaves the starting location’s geofence and stays outside it for two consecutive minutes, and it’s considered ended once the vehicle enters the geofence of its final stop. Understanding this distinction is useful when troubleshooting why a route shows a different status than an individual stop does.
How Do You Set Up Geofences Before Creating Alerts?
Why do geofences need to exist before you configure alerts?
Arrival and departure alerts are built on top of geofences, so a geofence needs to exist first before any alert referencing it can function. Without a defined boundary, Samsara has no reference point for determining whether a vehicle has actually reached or left a location, which makes geofence setup the necessary first step rather than an optional add-on.
What are the basic steps to create a geofence?
Setting up a geofence for a specific address follows a short sequence:
- Select the Settings icon at the bottom of the Fleet menu.
- Choose Addresses/Geofences.
- Select + Add Address.
- Enter a descriptive name for the location.
- Draw the geofence boundary using a box, circle, or freehand shape on the map.
- Save the address.
What if you have many frequently visited locations to add at once?
Adding addresses one at a time works well for a small number of locations. Larger operations can use a faster approach. Start by reviewing the Time on Site report to identify your most frequently visited locations. Then download the data and use it as a starting point for bulk address creation. This approach is much faster than entering each site manually.
How Do You Configure an Arrival or Departure Alert?
What are the core steps to build an alert?
Once your geofences are in place, creating an alert follows a consistent workflow across the dashboard:
- Navigate to Alerts, then select Create Alert.
- Choose a trigger, such as Geofence Entry, Geofence Exit, or Route Stop ETA Alert, using the search field to narrow a long list of options if needed.
- Apply the alert to specific vehicles, drivers, or tagged groups rather than the entire fleet, if scoping is needed.
- Add an optional geofence condition to restrict the alert to a specific location.
- Add an optional engine on/off condition, if the alert should only fire under a specific engine state.
- Choose how recipients are notified: email, push notification, or text message.
- Save the configuration.
How many vehicles or assets can one alert configuration cover?
Each alert configuration supports up to 4,000 devices, which comfortably covers the vast majority of fleets in a single configuration. Larger enterprise fleets that exceed this limit typically split alerts across multiple configurations grouped by region, division, or vehicle type, rather than trying to fit everything under one rule.
Can you limit when an alert is active?
Yes, and this is a detail worth using deliberately rather than leaving every alert running around the clock. By default, an alert configuration stays active continuously, but it can be restricted to a specific time range instead. You can set an alert to trigger only during a defined time window, such as normal business hours. You can also configure it to trigger outside that window. This setup helps catch unexpected after-hours movement at a facility that should otherwise remain idle. Time-based restrictions can also reduce alert fatigue among dispatchers. A rule that runs only when it matters prevents unnecessary notifications. As a result, dispatchers receive fewer alerts and are less likely to ignore important ones.
How Do Route Stop Alerts Differ From General Geofence Alerts?
What makes Route Stop ETA alerts unique?
While general geofence alerts trigger whenever a vehicle crosses a boundary, Route Stop ETA alerts focus specifically on scheduled stops within a planned route. This distinction matters operationally. A Route Stop alert can tell a dispatcher when a vehicle arrives and how that arrival compares with the scheduled time. This information helps dispatchers communicate proactively with customers instead of relying on a simple location update.
How does Samsara calculate a route’s ETA?
Route ETAs recalculate at each stop status change, such as an arrival or departure, and also update periodically throughout the trip. The table below summarizes how frequently recalculation happens under different conditions.
| Condition | ETA Recalculation Frequency |
|---|---|
| Standard trip progress | Recalculates regularly throughout the route |
| Stop status change (arrival or departure) | Recalculates immediately |
| ETA is 30+ minutes from destination | Recalculates every 15 minutes |
| Driver stays longer than scheduled at a stop | Recalculates every 15 minutes |
What is the route tracking window, and why does it matter for alerts?
Samsara applies a tracking window to each route to account for early or late arrivals without losing track of the route’s status. By default, this window starts one hour before the scheduled start time and extends six hours past the scheduled end time, giving drivers reasonable flexibility to complete all stops. If your fleet routinely runs earlier or later than this default window allows, adjusting it through Dispatch Settings helps prevent alerts and route statuses from behaving unexpectedly near the edges of a shift.
What Are Common Use Cases for Arrival and Departure Alerts?
How do fleets use these alerts for customer communication?
One of the most common applications is reducing the number of “where’s my delivery” phone calls a dispatch team receives. When a driver exits one stop’s geofence, the system can calculate a realistic ETA to the next stop, and an automated notification can go out the moment the vehicle arrives at the following location. This kind of automated, real-time communication tends to reduce inbound status inquiries considerably compared to relying on manual updates.
How do fleets use these alerts for detention or dwell time tracking?
Arrival and departure timestamps also support detention management, especially in logistics operations where long waits at a facility can quickly increase costs. A geofence entry can start the detention clock, while the corresponding exit can stop it. Dispatchers can then automatically flag stops that exceed the expected time. This approach eliminates the need for someone to manually track how long each vehicle sits at a dock.
How do fleets use these alerts for security or after-hours monitoring?
Some organizations configure geofence alerts specifically for locations where dormancy is expected, such as a yard overnight or on weekends. Any unexpected movement flagged during those windows can indicate anything from unauthorized use to a potential theft in progress, and pairing the alert with a quick response, such as sharing the vehicle’s real-time location with local authorities, turns a passive notification into an actionable security tool.
Conclusions
Arrival and departure alerts in Samsara rest on a layered system: geofences define the boundaries, default thresholds determine when an arrival or departure is officially recorded, and alert configurations decide who gets notified and under what conditions. Understanding this structure, rather than treating alerts as a single toggle, lets a fleet fine-tune notifications for customer communication, detention tracking, or after-hours security without drowning administrators in unnecessary alerts. For a broader look at how these alerts connect to the platform’s wider tracking, routing, and safety tools, Samsara – GPS Fleet Tracking Software remains a valuable resource alongside the configuration steps outlined here.
Frequently Asked Questions
Yes. The default two-minute threshold for arrival, and the 30-second threshold for departure, can both be adjusted through Dispatch Settings. This is useful for fleets operating in areas with closely spaced geofences or unusually large facility boundaries.
An alert configuration itself supports up to 4,000 devices, and you can add multiple recipients per alert, notified through email, push notification, or text message. For larger organizations, splitting alerts across several configurations by region or vehicle group often works better than trying to manage one very broad rule.
No. While Route Stop ETA alerts are specifically tied to scheduled routes and stops, general geofence entry and exit alerts work independently of any route plan. This means you can set up arrival and departure detection for any address in your dashboard, whether or not a formal route has been created around it.
