Documentation/Integrations and API·1 min read·Updated Nov 7, 2026
Notifications
Notifications will tell you when something needs your attention: a shipment at risk, a late arrival, a delivery. You'll choose the rules, the channels and when not to be disturbed. Planned.
Planned
Notifications are not available yet. Email and webhooks come first, with the visibility launch; SMS, Slack and Microsoft Teams follow.
Alert rules
A rule says when to alert and who gets it. Examples of what you'll be able to set:
| Rule | Example |
|---|---|
| Risk goes up | Alert me when a shipment's risk becomes High. |
| ETA slips | Alert me when the predicted arrival moves by more than 60 minutes. |
| Milestone | Alert the receiver when a shipment departs pickup, and again when it's delivered. |
| Tracking lost | Alert dispatch when a shipment has no location update for an hour. |
| Exception | Alert the team when a new exception appears. |
Rules can be set for your whole organization by an admin, and adjusted by each person for themselves. You can narrow a rule to certain lanes, facilities, carriers or customers.
Channels
| Channel | Best for | Status |
|---|---|---|
| Summaries and anything that isn't urgent. | First | |
| Webhooks | Sending events to your own systems. See Webhooks. | First |
| SMS | Urgent alerts for people away from a screen. | Later |
| Slack and Microsoft Teams | Alerts in your team's channel. | Later |
Quiet hours
Each person will be able to set quiet hours, for example from 20:00 to 07:00 in their time zone. During quiet hours, non-urgent alerts wait and arrive as one summary. You decide which rules are urgent enough to come through anyway.
Avoiding alert fatigue
- One alert per change: if the risk stays high, you aren't alerted again every few minutes.
- Alerts link straight to the shipment, with the reasons behind it.
- Start with a few rules on High risk only, then add more if you need them.