Back at the office
The dashboard is where the work actually happens.
The office side of Cordelle: build a departure from last season’s itinerary, bring the roster in, see who is ready, and publish.
Tours and departures
Build a tour once, then run it every season as a dated departure with its own roster.
Clone last season
Copy a whole departure — days, events, hotels, flights, packing list, country guides — and move the dates.
Move the whole trip
Trip pushed back a week? Give it a new start date and every itinerary day slides with it. No retyping.
Itinerary builder
Days and events with times and notes. Drag a day to reorder it and everything renumbers and re-dates itself.
Start from a document
Paste last season’s itinerary or your brochure text and get a draft departure back — days, events, hotels, flights, packing list — with an honest list of everything it couldn’t find. You check it, then publish.
Live flight status (Pro plan)
Type a flight number and a date and the airports and times fill themselves in. Then every group flight in Logistics carries the same live line travelers see — gate, delay, belt, and how old it is — so the office sees the same live line the group sees at the airport. How it works.
Bring the roster in
Paste a CSV from whatever your booking system exports — or connect WeTravel and pull each trip’s travelers straight across.
Email everyone their code
One click sends each traveler their own join code, and tells you exactly who was skipped and why.
Readiness grid
Worst first: who never joined, who joined but hasn’t downloaded, who’s on an old version — each with their phone number, ready to call.
Send a guide out with the trip
Your guide signs in with a guide code that opens the guide’s view of the trip, not a guest’s. Copy it from the dashboard, and issue a new one in one tap when the season ends — the phone holding the old code is signed out with it.
Message the group from your desk
The same megaphone the guide has, with the same per-traveler receipts — and one shared list — labeled in your dashboard with who sent each message — so you and the guide are never telling the group two different things.
Group map
Whoever is sharing, on one map, refreshed every 30 seconds. Last-known positions, never a trail.
Printed packet
A print-ready pack — the whole trip in black and white, plus tear-off slips whose QR opens the app straight to that traveler’s trip.
Publish when ready
Edits stay private until you publish. Travelers only ever see a version you signed off.
Your team
Invite office staff by email with owner or admin roles, each with optional two-step sign-in.
Departures keep themselves current
A trip turns itself on the morning it starts and closes the day after it ends, in its own time zone. Last season stops cluttering your list.
Branding
Palette, custom colors and logo, with a live phone preview as you change them.
Billing that runs itself
Card on file, plan changes and invoices through Stripe. No emails to us to upgrade.
Zapier, and your own tools
Send new travelers out to wherever the rest of your office works, or let another system add them here — through Zapier, or a scoped key on our own API. A key never reaches billing, your team or other keys. And if your own booking system should be running the whole trip, not just the roster: the API, below.
Already have a booking system?
Send whole departures from your own system, and leave the dashboard closed.
If your bookings already live in software you own, that software can be the office. It sends Cordelle each departure as one document — tour, dates, days and their events, hotels, flights, documents, packing list, guides and roster — and Cordelle makes the stored trip match it, republishes only when there is something new to publish, and answers with what it did. It messages the group, with the same per-traveler receipts the dashboard shows, each message labeled in the shared list with the key’s name and “(API)”, never as a person. And it hears back over signed webhooks when a traveler joins, taps a status, raises or clears an SOS, sees a message, or a departure is published.
The dashboard is opened once: to sign up, add the card a trial needs before it can make anything, and make the key. Billing lives there too, where a key cannot reach it. Everything after that is yours to automate.
The developer page has the quickstart, the shape of the departure document and the webhook signature; the full reference is the OpenAPI document the API serves, which needs no key.
- Safe to send hourly. Every send is compared with what is stored and only the sections that changed are written; the same document twice writes nothing and republishes nothing. A traveler your document doesn’t mention is reported back, never deleted.
- Webhooks carry ids, not people. A delivery names the departure and the traveler by Cordelle’s id and by your own reference — no names, no phone numbers, no care notes, no message text, no coordinates. Your system reads the details with its key, under the same consent rules the dashboard keeps.
- Part of Pro, and the 30-day trial. Listing departures and reading or adding travelers works on every plan; sending whole departures, messages and webhooks is the full API. A key opens the API and nothing else — not billing, not your team — and it cannot delete a departure or a traveler.
Three steps, and none of them involve talking to us.
-
1
Sign up and brand it
Create your agency, pick your colors, upload your logo. A one-click sample tour shows you the shape of it before you type anything real.
-
2
Build a departure
Paste last season’s itinerary and let the import draft it for you, clone a departure you’ve already run, or type it in. Bring the roster from a CSV or straight from WeTravel — or, on Pro, let your own booking system send the whole departure.
-
3
Send the codes
Publish, then email every traveler their join code. The email walks them to the app; they type six characters, and the whole trip is on their phone.