Know the moment a flight changes.
Pulse watches your airport's existing flight feed, diffs every change, and hands each one to the person who has to act, by email and SMS.
Live in production at a Canadian regional airport, and improving every month with the teams who use it.
A flight board shows the change. Pulse hands it to the person who has to act.
A walk through Pulse
Gate 4 to Gate 6 · Carousel 2
ETA 14:35
A live alert, as it lands
A flight change becomes a structured alert with the fields that matter, then goes to each contact on the rule by their preferred channel. Every delivery is logged.
Rules you can read at a glance
Each rule names its airline, trigger, time window, recipients and channel. No code, no buried config. Anyone on the team can see what a rule will do.
| Time | Fetched | Updated | Alerts | Status |
|---|---|---|---|---|
| 14:35 | 42 | 11 | 2 | ok |
| 14:34 | 42 | 4 | 0 | ok |
| 14:33 | 41 | 7 | 1 | ok |
| 14:32 | 41 | 2 | 0 | ok |
| 14:31 | 40 | 9 | 3 | ok |
A poll log you can point to
Every poll is recorded: how many flights were fetched, how many changed, how many alerts fired, and how long the poll took. If something stops working, the log shows it.
| Flight | Change | Outcome |
|---|---|---|
| WS 3568 | Gate 4 to 6 | Sent |
| AC 8123 | ETA revised | Sent |
| F8 214 | Gate 3 to 5 | Failed · retry |
| AS 118 | Status change | Skipped · suppressed |
An alert log, not just a sent flag
Every alert is logged with its outcome: sent, failed and retried, or skipped and suppressed. You can show who was told and who was not, and why.
Per-airline behaviour, not one size
Set each carrier to Standard, Enhanced or Suppressed. A carrier that needs every change paged gets Enhanced; one that only needs the log gets Suppressed.
What Pulse watches
Gate, stand, status, ETA, ETD, carousel and diversions. Every field on the flight record is diffed each poll, so a change anywhere on the record can trigger an alert.
How rules decide who hears what
Rules match on airline, change type and time window. A gate change for one carrier can page the handler; for another, just log it. The right alert reaches the right person.
Delivery and reliability
Retries on failed sends, per-contact channel preference, and your own SMS and email provider keys. When a send fails, you see it and the alert is retried.
What you need to run it
A flight data feed you already have, SMS and email provider keys, and a contact list. No new hardware, no cameras, no rip and replace.
Three ways to start
Pulse runs on your existing feed and your own SMS provider keys, with no per-message surcharge.
Pilot
For one airline or a small operation getting started with alerting.
- One flight feed
- Up to 3 alert rules
- Email delivery
- Alert and poll history
Operations
For a multi-airline airport that needs targeted routing and SMS.
- Multiple flight feeds
- Unlimited alert rules
- Email and SMS delivery
- Per-airline behaviour
- Operational history
Enterprise
For airports and handlers that need scale, integrations and support.
- All feeds and rules
- Per-airline behaviour
- Custom integrations and routing
- Priority support and onboarding
Help shape Vectro Pulse
We are working with a small number of regional airports, ground handlers and FBOs as design partners. It is a scoped pilot on your own operation, and what you learn with us shapes the product.
What you get
- Hands-on setup and onboarding, done with your team
- Direct access to the people who build Vectro Pulse
- A real say in what we build next
What we ask
- A live operation willing to run a scoped pilot
- Honest feedback, including what does not work
- One named contact for check-ins
The five products share one data layer
Each product stands on its own and gets more useful alongside the others. The rest of the family is below.
Questions we hear
See Vectro Pulse running
A 30 minute walkthrough in a real airport context, specific to your operation. No slides.