DELIVERY
Airport disruption alerts are only useful if they arrive where the decision is made. A dashboard for the daily picture, alerts for the moments that matter, and an API for your own tools.
Airport disruption alerts tell a business near an airport that operations, passenger flow or passenger waiting time are changing in a way likely to affect its next few hours of trading. The question is not whether a signal exists. It is whether it arrives somewhere a decision can still be made.
Each suits a different person and a different moment in the day. Most teams end up using two or three together.
A watchlist of the airports, terminals and locations you actually operate in. For each one, the three current scores with their window, confidence and reasons, shown as levels rather than raw numbers.
Underneath sits event history. Every change is recorded, so you can look back after a difficult afternoon and see what the signal said at the time. Comparing a week of changes against what your team saw is the fastest way to learn how much weight to give it.
Best for the morning look at the day ahead
You pick a location, a score and a level, and a message arrives when that threshold is crossed. A cafe might alert on demand pressure reaching HIGH in the next one to three hours. A duty manager might want only CRITICAL.
Who receives what matters more than how many rules you write. Tactical alerts go to whoever can change something in the next hour. Escalation alerts go to duty managers at a higher threshold and a lower volume.
Best for the moment something needs attention
When a score crosses a threshold you configured, DwellTime is designed to push a signed event to an endpoint you control, so the signal lands inside the tool your team already has open.
A rostering tool can flag a shift for review. A dispatch system can surface a staging prompt. An ordering tool can raise a suggested top-up. In every case the software prepares the option and a person approves it.
Best for putting the signal inside your own workflow
A REST interface for reading current and historical signals on your own schedule, scoped to an airport, a terminal and a business type. It suits dashboards you already run and internal reporting.
An event stream is planned for the opposite case, where waiting for the next poll is too slow. It suits live operations boards, driver apps and platforms passing signals through to their own customers.
Best for platforms and operations teams
Start with one or two thresholds per location rather than every score at every level. Use Slack for team-wide awareness and email where an alert needs a named owner. If a channel produces messages nobody acts on, raise the threshold instead of leaving it to be ignored. A muted signal is worse than no signal.
The window someone cares about usually decides which channel fits. Treat this as a starting point rather than a rule.
Slack or email, one or two thresholds
Next 1 hourDashboard kept open, webhooks into dispatch
Next 1 to 3 hoursEmail at HIGH and CRITICAL, plus history
Next 3 to 6 hoursREST interface and event stream
All windows, plus historyA single-site cafe may need nothing beyond one Slack channel. A transport operator across several airports may want the dashboard, webhooks and the interface at once.
None of these channels is available and no integration can be set up. Which ones ship first will depend on what pilot participants actually need, because a cafe group and a platform team pull that roadmap in different directions. We would rather build what the first operators use than announce a full matrix and deliver it late.
Airport coverage, pricing and timing are not announced. Any level or confidence value shown anywhere on this site is illustrative.
DwellTime is in early development. Tell us about your airport and your business, and help shape the first pilot.