For travel agencies & TMCs
See what changed. Know what comes next.
One journey, not a pile of bookings. We watch flights and trains together, show which connection breaks, and find what still works. You know before your client does.
01THE GAP
A flight and a train are one journey to your client. Nobody watches the connection.
A journey is more than the sum of its tickets.
flight + ICE, booked separately
AROUND THE CLOCK. WE LOSE THE SLEEP, NOT YOU.
02WHAT IT COSTS YOU
So you find out last — from the client, at night.
The train leaves without your client. App, desk queue, next train — nothing works. At 21:07 they call the only number that still answers: yours.
By now the good options are gone. One of your agents gives up the evening to rebuild the trip from what’s left.
Nobody pays for that work. It comes out of your margin.
03THE SAME EVENING, WATCHED
The connection broke at 18:04. Your phone rings at 21:07.
Why that call happens — and how we make sure it never comes.
Take-off: 41 minutes late.The airline's screen says normal. So does the railway's. Ours doesn't stop there.
The connection breaks — the 18:51 ICE is now out of reach.You know right now, not at 21:07 — while there's still time to do something about it.
Next train that still works: the 19:51 — sent straight to your desk and your client.Found before the flight has even landed, so the new plan is already waiting when they step off.
Silence.The moment your phone used to ring. Your client already has a new train — and you already know it worked.
SAMPLE SCENARIO · WE FIND THE RESCUE — BOOKING STAYS YOURS · LIVE DATA IN THE PRODUCT
04YOUR OFFER
Make the watch part of your offer.
Proactive disruption care is what the big TMCs sell to enterprise clients. With the watch, you offer it too — as your own service.
It works like this: you send each client a link to their watched trip — live, in plain words, no app, no login. The warning and the new train come from your agency, not from a portal. Your client sees you working before they even knew there was a problem.
YOUR BRAND TAKES THE CREDIT. OUR SYSTEMS LOSE THE SLEEP.
05THE FINE PRINT, UP FRONT
What we cover — and how completely.
Coverage is not a yes or a no. There are three levels, and the difference only shows itself on the day something moves. So each level says what it means for you, not just what is in it.
WATCHED LIVE
We are told the moment something changes. This is where your warning comes from, and why the minutes in it are measured and not guessed.
- Flights — worldwide
- German long-distance trains — ICE & IC
- Belgian trains — SNCB/NMBS
- Dutch trains — NS
- The connection between them
- The rescue search when it breaks
TIMETABLE ONLY
We have the timetable. We do not have the delays. So if the flight is late, you still get the warning and the next departure. If this train is the late one, nobody tells us. The board shows it in grey to say so.
- French trains — SNCF
- Swiss trains — SBB
- FlixBus coaches
NOT COVERED TODAY
We cannot watch these at all. Put one of these legs in a journey and that leg stays blank to us — no delay, no cancellation, no warning. Tell us which one you need. That is how we choose what to connect next.
- German S-Bahn and regional trains
- Polish trains — being connected next, see below
- Trains elsewhere — Austria, Italy, Spain
What that means for a Paris trip: your client lands in Frankfurt and takes the TGV on. The flight is watched, so a late landing still tells you the TGV is out of reach, and we still put the next SNCF departure in front of you. What we would miss is the TGV itself being cancelled while the flight runs on time.
WHAT WE ARE CONNECTING NEXT
- Poland, both levels at once. Our account for the national railway data is active and we have read the feed ourselves. It carries real delays and real cancellations, and it is free to use commercially. Connecting it is the part that is not done.
- France and Switzerland, moved up to watched live. Both networks publish a live feed of the same kind we already read for Germany, Belgium and the Netherlands. Nothing new has to be invented. It has to be connected.
Never: green without data. If we can’t see a leg, we tell you — here, not in month three of a pilot.
06THE ASK
Bring us the trip that broke. We’ll tell you if we’d have caught it.
The one where the phone rang at night. Bring that trip — twenty minutes, leg by leg. We’ll show you what we’d have seen, when you’d have known, and which train we’d have found. You leave with a straight answer: yes, we’d have caught it — or an honest “not that one, not yet.” Either way, you’ve risked twenty minutes, nothing more.
AND PRICING? NO PRICE LIST YET — THE FIRST AGENCIES ON BOARD DECIDE IT WITH US.
FAQ · ASKED BEFORE THE TWENTY MINUTES
The questions agencies ask before they write to us.
Straight answers — including the ones that end in “not yet.”
What is TranSwynt, in one paragraph?
TranSwynt is a German B2B service that monitors self-assembled journeys for travel agencies: a flight and an onward train, or two flights, booked on separate tickets. When the first leg runs late and the connection is at risk, TranSwynt warns the agency’s desk and the traveller by email, before the traveller calls, and proposes an alternative that still works. Coverage today: flights worldwide, trains in Germany, Belgium and the Netherlands, live. TranSwynt is built and operated by SWYNT (Patrick Kowal SWYNT), Germany.
My clients already have the DB app and the airline’s app. Why this?
Each of those apps watches its own system — and only answers when asked. The DB app doesn’t know your client’s flight is running late; the airline’s app doesn’t care what happens after landing. Nobody adds the two together — that’s the gap in chapter 01. We watch the whole chain and speak up on our own, while your client is still in the air and can’t check anything.
Does TranSwynt rebook the trip — or replace our booking tools?
Neither, deliberately. We watch, we warn, we find the train that still works. Booking it — and the client relationship — stays with you. Nothing about how you book today changes; we sit alongside your tools as the early-warning layer, not underneath them.
Who gets the warning when a connection breaks?
Your desk, always — and your client too, if you gave us their address for that trip, at the same moment, automatically. Because at 18:04 a warning shouldn’t wait in anyone’s inbox to be forwarded. You decide per trip: client warned directly, or desk only and you deliver it personally. During a test everything goes only to you — your clients aren’t involved. And either way, those alerts are the only thing our system ever sends a client of yours — no marketing, no contact from us.
Can you tell us whether the original ticket is still valid on the new train?
No — and we won’t pretend to. Validity depends on the fare and the operator: a Sparpreis is bound to its train, and when a late flight costs your client the booked ICE, DB owes them nothing — the delay wasn’t DB’s. We find the train that still physically works; whether the old ticket carries over is your professional call. The difference is you’re making that call at 18:05 with options, not at 21:07 without them.
What does it take to get a trip watched?
An email. You send us the itinerary — flight number, the booked train, the date — and the watch usually starts the same day. No integration with your booking system, no accounts to create, no IT project.
What client data do you need — and where does it live?
To test: none at all. “Client A, Kraków–Frankfurt–Stuttgart, Thursday” is enough to watch a journey — the link and the alerts go to you, not your client. Names and addresses only enter the picture when you decide a client should get their trip link or be warned directly — and before that happens, we agree data-processing terms (AVV) with your agency. What we store lives in a database in the EU (Ireland); alert emails come from alerts.swynt.eu; the full detail is in our privacy policy.
What happens when you can’t see part of a trip?
We tell you — on the trip itself, not in a footnote. No data, no green: a leg outside our coverage is shown as unwatched, so you know what you’re relying on before you rely on it. Chapter 05 is the current list, and it’s honest.
What are we committing to?
Nothing beyond the step you’re in. There are three, and each one is your decision:
Step one: twenty minutes. You bring one broken trip, we tell you honestly whether we’d have caught it. That’s all.
Step two — only if step one convinced you: the design partnership. Ninety days, 100 € a month, and one number we agree before day one that counts as success. We watch your clients’ real journeys; the links and alerts go to you alone. The end date is fixed on day one, so it can’t quietly drag on. The price after is fixed before day one too, so you know both numbers before you sign.
Step three — only if the number was met: you keep the watch. At the price we fixed together — there’s no price list; the first agencies on board set it with us. If the number was not met, you walk, and it stops at the token months. And even at this step there’s no long contract: cancel any month, no reason needed.
You never promise anything beyond the step you’re in, and both prices are on the table before you pay the first one.
Will your client see our brand or yours?
Today, mostly ours. The page runs on our address (transwynt.swynt.eu) and looks like TranSwynt. But your client gets it from you: you put the watch on their trip, you send them the link. Your name, logo or colours on the page — not built yet. That’s one of the first things early partners get a say in.
Something we didn’t answer? Ask it the useful way — with a real trip attached: info@swynt.eu