A fuel truck driver misreads a handwritten tail number on a whiteboard and tops off the wrong Citation. Nobody gets hurt, but the customer notices, and now your GM is on the phone apologizing instead of running the ramp. That is the failure mode every dispatch software vendor claims to fix. Most of the demos look the same. The contracts do not age the same way.
You are going to sit through a dozen sales calls that all promise real time visibility and faster turns. Some of those tools will hold up on a 100 degree ramp with three quick turns stacked and a radio that keeps cutting out. Others will look great in the demo and fall apart the first time your Wi-Fi drops at the far hangar. Here is what actually separates the two, and what to ask before you sign anything.
What Breaks First When the System Goes Down
Every dispatch platform works fine in a conference room with strong Wi-Fi and one demo aircraft on the board. That is not your ramp. Your ramp has dead zones behind the hangars, a network switch that resets during storms, and a line crew that needs to know where to marshal a Gulfstream in the next four minutes regardless of what the internet is doing.
Ask every vendor this directly: what happens on this screen when connectivity drops mid turn. If the answer is vague, or if it takes them more than one sentence to explain, that is your answer. A system that requires constant connectivity to function is a system you will eventually work around with a paper backup, which defeats the entire point of buying it.
Push further on what "offline mode" actually means in practice. Does it cache the last known board so your line techs can still see assignments, or does the app just go blank? Can a ramp agent close out a turn locally and have it sync once the connection comes back, or is that data lost? Vendors will tell you their uptime is excellent. Uptime numbers measure their servers, not your hangar's internet connection, and those are two very different problems.
The Training Question Nobody Asks Until It's Too Late
Line service turns over fast. You hire seasonally, you hire for weekends, and you are training someone new on the board almost every month. Software that takes a week to learn is software your best techs will quietly stop using in favor of the radio, and your newest hires will never fully adopt.
Before you sign, ask the vendor to train someone on your team who has never seen the product, live, on a call, with no script prepared in advance. Watch how long it takes that person to assign a turn, mark it in progress, and close it out. If it takes more than a few minutes for someone who already knows what a turn is, the interface is fighting your operation instead of supporting it.
Also ask what happens to that training when their product updates. Some vendors push interface changes without warning and expect your crew to figure it out mid shift. Others give you notice and a walkthrough. You want the second kind, especially if you run a lean crew with no dedicated dispatcher to absorb the learning curve for everyone else.
Who Owns the Data When You Walk Away
This is the question that gets skipped in almost every sales conversation, and it is the one that matters most a year from now. Your dispatch software is going to accumulate a real operational record: turn times, GSE utilization, staffing patterns, into plane timing, lav service history. That record has value whether or not the vendor relationship works out.
Get a straight answer, in writing, on three things before you sign:
- Can you export your full historical data in a usable format at any time, not just at contract termination.
- Does the vendor retain, resell, or aggregate your operational data, and if so, in what form.
- What is the actual off boarding process if you switch vendors, and how long does it take.
An FBO that cannot pull its own turn time history to negotiate a fuel supply contract, or to defend its safety record during an IS-BAH audit, has a data ownership problem, not a software problem. Treat this the same way you'd treat a lease clause. Read it before you need it.
Ask This Before Every Contract, Not Just This One
Run this five question sequence with every vendor you evaluate, including us. It takes fifteen minutes and it will tell you more than any feature list.
- Walk me through exactly what a line tech sees when a based Part 135 operator calls in a same day quick turn.
- What does the system do the moment connectivity drops during an active turn.
- How does a CSR see what the ramp is doing without walking outside or getting on the radio.
- What is your average implementation timeline for a shop our size, start to first live turn.
- If we cancel, how fast can we get our data out, and in what format.
Write the answers down. Compare them side by side after the calls, not during them, because the pitch will sound convincing in the moment regardless of the actual answer.
The best dispatch software is the one your crew forgets is software, because it just tells them what to do next.
Where CreuLink Fits Into This
We built CreuLink because we watched too many FBOs run turns off a whiteboard and a handheld radio, with the CSR desk finding out a jet had arrived only when the pilot walked in the door. A digital board that line techs, CSRs, and management can all see at once solves that specific problem: everyone knows the status of every tail on the ramp without a radio call. That is the bar we hold ourselves to, and it is the bar you should hold every vendor to, including us.
What This Decision Actually Costs You
The cost of getting this wrong is not the monthly invoice. It is a missed quick turn for a based customer who starts calling the FBO across the field, a line tech who reverts to a clipboard because the app was too slow under pressure, or a safety gap you cannot document during an audit because the data walked out the door with the last vendor. Run the checklist above before you sign anything. Your ramp will tell you within a week whether the software earns its place on it, and that week matters more than anything in the sales deck.
CreuLink Team
Dallas, TX
Why Radios Fail FBOs During Peak Season and What Fixes It
Radios break down exactly when ramp traffic peaks, not because the hardware fails but because one channel cannot hold a full shift's worth of information. Here is what actually breaks and how to fix it.
Coordinating Ground Crews When Three Departures Push at Once
A practical playbook for FBO and ground handling leaders on managing simultaneous departure pushes without blown turn times, missed services, or a customer walking to the FBO across the field.