Trip Delay Alert
Watches every truck until loading, like a dispatcher would
- 3 levels
- Each with timing, channel and people
- 4 channels
- Email, SMS, WhatsApp, voice call
- In advance
- The alert comes before loading time
Not moved
Planned departure: 13:00 · Vehicle has not moved yet · 12 min late
Loading: before 14:00 · drive ~1 h
Example trip timeline
- 12:30Yellow bell appears on Orders
- 12:40Level 1: WhatsApp → driver + owner
- 12:50Level 2: SMS, Email → 1 person
- 13:10Level 3: Voice call → 1 person
Plate and times shown are illustrative.
Some of the brands that trust us







- and more
The module from start to finish
Seferi does for every truck what a dispatcher does all day on the phone. It works out the latest departure by taking the drive time from the truck's current position away from the loading time; if the truck is still standing then, an alert appears next to its plate and your team is told by email, SMS, WhatsApp or voice call through the levels you set.
Product screen
Worked out from the truck's position
The latest departure is the loading time minus the drive time from where the truck is now. The truck's position must come from your connected tracking system.
Not moved
Planned departure: 13:00 · Vehicle has not moved yet · 12 min late
Loading: before 14:00 · drive ~1 h
Example trip timeline
- 12:30Yellow bell appears on Orders
- 12:40Level 1: WhatsApp → driver + owner
- 12:50Level 2: SMS, Email → 1 person
- 13:10Level 3: Voice call → 1 person
Plate and times shown are illustrative.
How the work flows
Three levels
Levels are set against the latest departure: before it, on time or after. The first level always reaches the driver and the order's owner; a level runs only if the truck is still standing.
- 1
Loading time and place are entered
- 2
Latest departure is worked out
- 3
If the truck is standing, the alert appears
- 4
Levels notify the team
Panels on the screen
One click to message the driver
On a job with a delay alert, right-click the row to send the driver a delay message on WhatsApp.
Delay alertNobody rings the driver to ask "have you left?"; the truck that will be late shows up before the loading slot is missed.
What does this module take over?
On the left how it runs today, on the right how it runs in Seferi.
Whether the truck has left is found out by calling the driver.
A standing truck shows next to its plate at the latest departure time.
The delay is only noticed when the truck should already be at loading.
The alert comes while the truck can still make it.
Used in the daily work
Every item maps to a screen inside the product — none of it is a roadmap.
- Latest departure time from the loading time and the truck's position
- An alert next to the plate of a truck that is running late
- A yellow bell on Orders as departure nears; you choose how early it appears
- Filtering jobs with a delay alert in Orders
- Three levels: when, through which channel and to whom
- Email, SMS, WhatsApp and voice-call channels
- Right-click to send the driver a delay message on WhatsApp
Who uses it
The same module does not open the same screen for everyone on the team.
Operations
Sees the alert next to the plate and sends the driver a delay message.
Order owner
Always gets the first-level notice, together with the driver.
Admin
Sets the levels, channels and people in Settings.
Once this module is switched on
In the demo you see these on your own data.
Connects to
Nobody calls the driver to ask "have you left?".
The delay shows before loading.
Who gets told is decided in advance.
What gets asked most before a demo
What does the alert need?
The truck's position must come from a connected tracking system, and the job needs a loading time and place. The feature is switched on in Settings.
Is the customer told too?
No. The alert only reaches your team; you decide what to tell the customer.
Which channels are used?
Email goes from your own address, SMS and voice calls from Seferi's account, and WhatsApp from your company's connected number.
See Delay alert running on your own operation
The demo is not a slide deck; it is a session that runs on your own data.
- 01
A 30-minute call
We listen to your operation: how many vehicles, which lanes, which step is still done by hand today.
- 02
A run on your own data
We read a real request from your own inbox and turn it into a quote; you see your own lanes on screen.
- 03
A rollout plan
Which module goes live on day one, what gets migrated, and the package price for your fleet size — in writing.
