Changelog

What's new in TripDesk365

What changed, newest first. Each date is the day the release went live.

  • Flexible dates: choose ±1, ±2 or ±3 days on the search form, and the results open with the lowest fare for your party on each day around yours , on a return, on each pair of days out and back. The form says how many date searches each window takes before you search. Pick a day to see its fares. Days already gone are not searched, a refresh within a few minutes shows the same prices without searching again, and date searches count toward a daily allowance for your agency, shown under the grid. More
  • Card numbers stay with the cardholder: a client on the phone gets the payment link and types the card themselves on the payment company's page, rather than an agent typing it. A note, message or reason that contains a full card number is refused with a sentence saying why (the last four digits are fine), and a card number in an email sent to your booking inbox is blacked out before the email is kept. More
  • Your corporate clients' own people: on the Staff page, give somebody the Travel Manager or Booker role for one of your company clients. They see only that company's trip requests, approvals and bookings, at the price the company pays , never your commission or net fares , and their sign-in email points them to your corporate address when you have one. More
  • Somebody whose role does not include searching for fares, such as a corporate travel manager who approves, now lands on their own work (approvals, trip requests, bookings, travellers, policy) instead of a search form. Searching can be given to one person on the Staff page, approved by a second. More
  • Trip requests: a corporate client's traveller asks for a trip before anyone searches , where, when, how many, what it is for and why, a budget, and the company's own booking fields. When the company says so, its approver agrees the trip first (every trip, or only international ones). The agency takes the request, searches and sends the options as a proposal; the traveller is emailed the link, sees which options fit the budget and chooses; the agency books it, and the booking carries the request's project code and cost centre. Every step is kept with who did it and how long the request waited there. More
  • Over budget: when a company asks for it, a booking priced above its trip request's budget can be held but is ticketed only after the company's approver agrees, and an approval covers the price it was asked for, no more. More
  • Approvals waiting on me: one page with every trip and booking you may decide, oldest first, why each needs approving and how long it has waited, and approve several at once. Unanswered requests are chased: the approver is reminded after a day and again twelve hours before the link stops working, and the person who asked is told then, and if it expires. More
  • A corporate client's own people , its travel manager, its bookers , now see only their own company at your agency: its bookings, travellers, booking fields, travel policy, reports and trip requests. Everything else in your console is refused to them in words, and anything new is refused until it is made safe for them. More
  • Accounting export for corporate clients on NetSuite: write down once how the client's books name things , your agency as their vendor, their travel and fee accounts, which of their columns takes the cost centre, project or travellers, and a different account for a cost centre that needs one , and export a month of invoices and credit notes as a vendor-bill file ready to import. More
  • Return trips: search with a return date and each fare is priced for the way out and the way back together. Every result shows both directions with their day, time, stops and flights; a proposal shows the day the traveller comes back; a trip request for a return searches both ways; and the booking keeps every flight. A return date before the departure is refused in words. More
  • Search results now open with an airline matrix: the cheapest fare for each airline at each number of stops, and a click on a price shows only those fares. Filter by stops, airline, price, and takeoff and landing time each way; hide fares with a warning, or a company's out-of-policy fares; sort by price, departure, the way back or, for agents, commission. Filtering never searches again, so the prices stay the ones you were shown. More
  • Multi-city search: up to four legs on the search form, priced as one fare. Each result names every leg with its day, time, stops and flights; the filters and the time windows work leg by leg; proposals and the search log show the whole route; and the booking keeps every flight. A leg that is incomplete, goes nowhere, or departs before the one before it is refused, naming the leg. More
  • Trip requests can be multi-city: the traveller lists each leg and its day. The approver sees every leg, the trip counts as international if any leg crosses a border, and the agency's "Search this trip" opens the multi-city search with every leg filled in. More
  • Spending limits per direction: write a ceiling per direction, or per traveller per direction ("$600 a person each way"), and a return is judged each way and a multi-city trip each leg, instead of its whole price against a limit meant for one way. More
  • Holding a fare from the search results now asks which client it is for (a company's own people see only their company, already chosen), and choosing a higher fare on a booking keeps the booking's client. Holding and ticketing draw on your agency's own credit account with us. If a hold cannot be made, the page says why beside the fare. A booking's header shows the day the flight leaves where it leaves, and both days of a return. The hold page now says which fare it is about to hold , the route, every flight in local time, the cabin and brand, and the price the results showed , and says so first when that fare has expired. More
  • A traveller new to a company's list stays new on every booking until the company's approver accepts them: booking the same person again no longer skips the approval. Once accepted, they are on the list for every trip after. More
  • A booking waiting for approval can now send the approver's link again , after giving the approver role to somebody, for example. The same link goes to whoever may decide it now. More
  • A booking's steps say Done once reached, and Issue ticket is offered only to people who may issue tickets , anyone else is pointed to Ask us to ticket. A refused action now says in words which permission it needs and whom to ask. More
  • Ask us to ticket now reaches our ticketing desk from every agency: we see your booking, its deadline and your note, issue the ticket on your account with us, or decline with a reason , and you are emailed either way. More
  • A passport is asked for only when a trip crosses a border: a domestic trip is ready to hold and ticket with the traveller's name, date of birth and gender. A trip between countries , the US and Canada included , or one with an airport we cannot place still asks for it. More
  • Give one person one extra permission on top of their role, or take one of their role's permissions away. A permission given this way works only once a second person at your agency approves it; nobody can give one to themselves or approve their own request. Taking one away works at once. Every change is listed on the Staff page with who asked, who approved and why, and ended ones stay listed. More
  • Support hours: set the days and hours your desk works, your time zone and the days you are closed. Request deadlines in your work queues count only those hours, so a request that arrives on Friday evening is due on Monday, not overnight. Airline and ticketing deadlines (ticketing, voids, schedule changes, disruptions) never pause. More
  • When our support needs to see what one of your people sees, they can view your console as that person: read-only, for 15 to 60 minutes, with a reason. Nothing can be booked, ticketed, refunded or changed while they look, and every view is listed on your Staff page with who looked, as whom, why and for how long. More
  • Airline credits: keep a cancelled ticket's value as a credit the traveller holds (the airline, the ticket number and the issue date come from the ticket), or record one from an airline's email. Use it, in part or in full, on the traveller's next booking. The client's advisor is emailed 30 and 7 days before a credit expires, and every credit, its uses and how it ended stay listed. More
  • What's blocking: every open booking's next step on one page, the most urgent first, with each reason it cannot be held or ticketed yet in the same words its booking page uses, and the airline's ticketing deadline beside it. More
  • Readiness on every booking: what is done and what is missing (the fare held, the travellers' details, the names checked, the ticket, the client's invoice, the itinerary sent), the next thing to do, and for each missing item what happens if it stays missing. More
  • A held booking's itinerary now says it is not ticketed yet, and by when it must be, in its subject, its email, its printout and its share link; a quote says nothing is held. A higher fare in the alternate fares list that is in a different cabin says so. More
  • Supplier statements: add a consolidator's or an airline's statement (a CSV, a pasted table, or a PDF or screenshot read by Smart Import) and each line is checked against your bookings: matched, overcharged, undercharged, commission short, a credit, or a ticket that is not yours. Nothing on a booking changes; you accept or dispute each line, with a note. No passenger names are kept, and the file itself is not stored. More
  • A supplier log on every booking: each request sent to the reservation system about it, with what it was, when, who sent it and what came back, including how an answer that was lost was settled. More
  • Mask fares: set a role on your Staff page to see the client's price only. That person never sees the net fare, the markup or the commission: not in search, on a booking or on a proposal, and the pricing, commission and payout pages close to them. Masking takes effect at once; showing fares in full again is never the person's own act. More
  • A name check before ticketing: each traveller's name on the booking is checked against their saved profile (and the passport saved with it), against another saved record with the same date of birth, and against what the ticket can print. Each finding is yours to decide: take the saved name, confirm it as printed on the passport, or dismiss it. Until then the booking can be held but not ticketed, because a name corrected after ticketing costs money. More
  • Ask us to ticket: on a held booking, ask our desk to issue the ticket. It joins our queue due before the airline's ticketing deadline, with anything that would stop the ticket listed beside it, and you are emailed when it is ticketed, or told why not. More
  • Who pays whom, on every booking: for each way the sale can be paid, what the airline charges your client's card, what we charge, what you collect yourself, what we pay the airline and what comes back to you, each with when. A margin change that moves money onto our card charge, or leaves a sale earning nothing, now asks you to confirm before it is saved. More
  • Your service fee on a card sale, charged to your client through our payment link, is now paid to you with your markup in your payouts. And once your client's card is held, or the ticket is issued, the margin on that sale is fixed. More
  • Client proposals: tick up to five fares in your search results and send them to a client as one link. The client sees each option at one price, your margin included, and never what it costs you; they choose one, you are emailed, and you book it from the proposal. Links work for 24, 48 or 72 hours. More
  • Independent agents: a role can be set to see only the person's own book of business, meaning the bookings they made or own and the clients they advise. Agency-wide pages such as the operations queue, the inbox and billing close to that role. More
  • Your account with us, entry by entry: every ticket issued on credit, every refund and every payment we received, with the balance after each, what you owe and what you can still book. When your payment reaches us we record it, and what you can book goes back up at once. More
  • A searches report: every search your agency ran, who ran it, what came back and whether it was booked, the searches that found nothing on their own, and your most searched routes. More
  • A queue timing report: for each work queue, how long requests waited before someone picked them up, how long they took, how many met their deadline, and who finished them. More
  • Name each client's primary advisor from the people at your agency, and hand a work item to a colleague by name instead of by an account number. Only someone working at your agency can be chosen. More
  • A publication history: every pricing, travel policy and operations rule that was turned on, who drafted it, who published it and when. Commission corrections already decided are listed too, with who asked and who recorded the answer. More
  • A newer airline document for a booking you already have, uploaded, pasted or from the Inbox, can be added to that booking, with what it says differently listed beside it: a moved departure, a flight added or missing, a traveller who is not on the booking. Nothing on the booking changes by itself. More
  • Flight searches whose fares were not booked are now deleted 90 days after the search. The fare a booking was made on stays with the booking. More
  • Agreements, signed online: send a new corporate client or sub-agency its agreement pack, and a new agent or colleague theirs (terms, confidentiality, acceptable use and card handling). They read and sign on a link emailed to them; a second person at your agency countersigns; both are emailed a sealed copy. More
  • A new corporate client or sub-agency books once its agreement pack is complete, and a new colleague's first role is switched on once theirs is. Clients and staff already working are not affected, and their packs can still be sent. A contract signed on paper can be recorded instead. More
  • Sanctions checks on agreements: the business and the person signing are checked against the US, Canadian and United Nations sanctions lists when a pack is sent and again before it is countersigned. A possible match is looked at and cleared by a person, with a reason that stays on the record. More
  • Add your agency's own terms to the packs you send your clients and agents; they go after our standard documents, which stay as they are. More
  • A code by text on every signature: before a card authorization, a change authorization or an agreement pack is signed, the signer asks for a one-time code sent to the mobile number recorded before signing (the phone given on the payment page, or the mobile you entered when sending the pack). The signed record shows the code was entered and the number's last four digits. Codes go to US and Canadian numbers; for any other, signing is by email alone and the record says so. More
  • ID checks on card sales are now deleted in full: the photo of the ID and the selfie held by our identity-verification provider go 3 years after the check, and our own record of the check after 39 months, instead of the photos being kept up to seven years. More
  • A signing code that went to a VoIP number is flagged to your staff on the booking and on the agreement pack, since such numbers can be had in minutes. The signature still stands; on a held card, a card approver can ask for the cardholder's ID check. More
  • A client you have switched off can no longer be booked for: holding and ticketing for them are refused, while their existing bookings are serviced as before. More
  • Card disputes on payments taken through PayPal are now answered in one step as well: the booking's evidence and the signed card authorization go to PayPal directly, instead of being uploaded by hand. More
  • The payer's IP address, device, email address and phone number kept with a card payment are now deleted after 39 months, with the other checks on the payment. The payment itself stays in the booking's records. More
  • When a card sale needs more proof, your client now chooses how to confirm it is them: their card's bank confirms them (nothing is charged), an ID check, or a call-back from your agency, which a card approver records. The ID check is no longer the only way. More
  • Before an ID check, your client reads what is collected, why and for how long, and signs their consent by typing their name. Clients with a Québec billing address are offered the bank check or a call-back instead. More
  • Our card-fraud record: after a card dispute is lost as fraud, your card approver can report that the card was used without the cardholder's permission. Once we confirm it against our own dispute records, a later sale with that card needs extra verification; it is never refused. No agency is told whether a card is on the record. More
  • Card authorization on the payment link: your client initials the fare conditions you state, pays, and signs, and is emailed a signed copy. For a card you take by phone, the cardholder signs through a link emailed to them. The ticket is issued only once the card is held and signed for. More
  • Every check on a card payment is kept with the booking for 39 months: the card bank's verification, the address and security-code results, the payer's device, and each signing step, ready for a chargeback or a debit memo. More
  • Each signed card authorization is sealed as a digitally signed PDF with a trusted timestamp, so any later change to the file shows. The cardholder is emailed the sealed copy, and you can download it from the booking. More
  • Card charges through the payment link carry your agency's name on your client's card statement, the authorization says exactly how the charge will read, and your client is emailed a receipt when the card is charged. More
  • A card paid on the payment company's own page, including one you enter for a client by phone, is asked for its billing address, so the card bank checks it. More
  • A card an agent types for a client above $2,500 needs a second person, your administrator, to approve it before the ticket is issued; never the agent who typed it. A cardholder email that belongs to your own staff is flagged on the booking. More
  • When an agent books a traveller who is not yet on a corporate client's traveller list, the client's own approver confirms before the ticket is issued, by the same approval email as for out-of-policy trips. More
  • Changes after a card sale: a name correction, an added passenger or a change with an extra charge needs the cardholder's fresh, signed change authorization, and the extra charge is paid on its own link and charged when the change is made. More
  • Card disputes are tracked: when a client's bank disputes a card payment made through the payment link, the booking shows the dispute, its reason and the deadline to respond, and your administrators are emailed when it opens and when it is decided. More
  • We answer card disputes with the booking's own evidence: the sealed card authorization, the fare conditions your client initialled, the card bank's checks, the receipt and the tickets, sent to the payment company in one step, or prepared as a ready pack where the payment company takes it on its own site. The booking shows when it was sent. More
  • When a card dispute is lost, the agency's markup and commission share on that booking are not paid, and anything already paid comes back through the next payout; a dispute later won restores them. The booking and the dispute email both say so. More
  • An ID check on risky card sales: for a card you type for a phone client over $2,500, a card your client's bank did not verify, or whenever your administrator asks, the cardholder confirms their identity with a government ID and a selfie before the ticket is issued. A different name than the one signed needs your administrator's written reason. We cover the cost. More
  • Every card payment through the payment link is now scored for fraud. Your staff see the score and why: where the payer's connection comes from and whether it hides behind a proxy or VPN, how long their email has existed, whether their phone is a VoIP number, and whether the email that paid is the one that signed. A high score asks the cardholder for an ID check before the ticket is issued. The payment page now asks for the payer's phone number. More
  • Help on every page of the console: ask TripDesk365 support, and the page you were on and the booking go with your question. Replies come by email and on the Help page.
  • Agent tags: label the fares you want your consultants to sell, such as Extra commission or Preferred airline, by airline, route, cabin, booking class, travel and selling dates, or whether the fare pays you commission. Only your agents see them, in search results. More
  • Live flight data: from two days before departure each flight is followed, and a cancellation, a diversion or a delay of 90 minutes or more is filed on the booking by itself. More
  • The travel map shows live aircraft positions where flight data has them. More
  • Travellers are emailed their new departure gate and their baggage belt, and their trip link and itinerary show both. More
  • Connection at risk: when a late arrival leaves too little time for the next flight, the person who booked is told, with later flights from the airline timetable. More
  • Travel policy: an airline safety rule, so flights are operated by airlines on IATA's IOSA safety registry. More
  • Travel policy: a rule for the EU Air Safety List, so no flight is operated by an airline the European Commission bans or restricts. More
  • The airline safety rule now reads IATA's own IOSA registry, with each registration's expiry date. More
  • In Slack, /tripdesk flight BA117 lists your bookings on a flight with its latest status, delay, gate and baggage belt. More
  • Search results, the booking page, itineraries and trip links note any flight operated by an airline the European Commission bans or restricts in the EU, whether or not your policy has the rule. More
  • Invoices, credit notes and receipts as PDF files: download one from the booking, and the email to your client carries it. More
  • Tax numbers on your documents: add your EIN, BN, GST/HST or QST once, and each client's billing name, address and tax numbers. Every new invoice carries them. More
  • Travel policy covers more: rules by a traveller's band or grade, spending limits per traveller or per route, and four new rules: a destination's State Department level, a review for every trip in scope, preferred airlines, and how many of your people may share one flight. More
  • Trips imported from elsewhere are checked against more of your policy, including flight time. More
  • Client documents: open, print or email an invoice, credit note or receipt from the booking, with your business address and contact details on it. More
  • Invoices show a due date from your payment terms and a How to pay section with your bank details. Every change to the bank details is emailed, masked, to everyone who manages your business details. More
  • Travel policy per client: each client can have its own rules alongside the account's, and a client's travel manager manages only theirs. More
  • Trips sold outside TripDesk365 are checked against the client's policy when their price is recorded. An out-of-policy trip is flagged and the client's approvers are emailed; nothing is blocked. More
  • Approvals: only people allowed to approve can decide, never the person who asked, and a refusal needs a reason. More
  • The travel policy page shows where your rules are checked. More
  • Everyone can correct their own name under Your account.
  • New free tools on this site: the 2026 ARC calendar, a void deadline calculator, every country's State Department advisory level, and a flight emissions calculator. More
  • A free travel policy template, a duty of care checklist and a travel industry glossary. More
  • Book a demo from a form on the Contact page. More
  • The emissions report can now be cut per cost centre or per booking field, such as a production, a grant or a client matter, as well as per client. More
  • The flight-by-flight export has an Operated by column for codeshares. More
  • An emergency contact for every traveller, and their Known Traveler and Redress numbers with the issuing country, on the booking and the traveller's profile. Contact details are shown only to roles allowed to see them. More
  • Record the price of a booking imported from elsewhere: fare, taxes, your fee, what it cost and your margin. Then issue the client's invoice, record their payments as numbered receipts, or credit it in full to correct the price. More
  • Industry pages for film and TV production, professional services, nonprofits and universities, with a high-risk travel approval checklist and a Fly America Act checklist. More
  • Our database is now encrypted at rest, alongside file storage and message queues. More
  • Booking import: paste a GDS screen or upload an e-ticket, and TripDesk365 reads it into a draft booking for a person to check. More
  • Rebooking drafts: after a disruption, a draft email to the traveller for the agent to edit and send.
  • Travel map: travellers in the air or about to fly, with positions estimated from flight schedules. More
  • Slack: look up bookings and travellers with the /tripdesk command. More
  • Booking fields: ask for a cost centre or project code on every booking, required before ticketing if you choose.
  • Browser alerts for disruptions and advisory changes.
  • A public status page. More
  • Referrals: a free month for both agencies when one refers another.
  • A private forwarding address for each agency: forwarded airline and supplier emails are filed with their booking. More
  • Files on bookings, such as e-tickets and passport or visa copies, encrypted before they are stored.
  • Traveller profiles that remember details from one trip to the next.
  • Slack, Microsoft Teams and signed webhooks for booking events, and a read-only API with keys. More
  • CO₂e estimates on bookings and an emissions report per client. More
  • A booking register with saved views, a travel calendar and a traveller directory.
  • Daily and weekly email digests.
  • Itinerary emails, printable itineraries and calendar files, from the agency's own domain.
  • Private trip links a traveller can open without signing in, with a way to ask for different dates.
  • Each destination's State Department advisory level on the booking and the itinerary. More

Earlier releases are not listed here.

See TripDesk365 with your own bookings

A 30-minute walkthrough: we import a few of your real trips and show you what your team and your travellers would see.