It is easy for a travelling passenger and a helpful organiser to request the same Davos pickup independently. The problem is not solved by assuming that a shared surname or flight number will make the duplication obvious. Bring the requests together deliberately so that everyone knows which booking and vehicle arrangement remain valid.
Collect every reference before changing anything
Ask the people involved to locate their request numbers and any written confirmations. Distinguish an unanswered enquiry from a confirmed reservation; these are not interchangeable. Compare the airport, travel date, passenger name and destination to establish whether the requests really describe the same journey. Similar-looking trips can be separate legs or separate parties. Avoid cancelling an order simply because its title resembles another item in the organiser’s email inbox.
Tell the transfer team there may be a duplication
Send the references together through the normal contact channel and explain who submitted each one. State that you want the team to review the overlap before giving a final operating instruction. Do not send two separate messages saying only “cancel this”, because the relationship between the requests may be lost. Identify the preferred contact person for the conversation so that subsequent replies do not produce another pair of conflicting decisions.
Compare the actual scope of both requests
One enquiry may contain an airport pickup only while the other includes a return leg, additional passenger or different destination. Compare the complete itinerary, vehicle category and luggage details, not just the fare. If one request has the correct flight but the other has the updated address, send one consolidated set of details. The final record should not force dispatch to reconstruct the journey from fragments spread across two unrelated email threads.
Obtain an explicit written resolution
Ask which reference remains active and what happens to the other request under its applicable terms. Any payment already made should be identified accurately, with its amount and reference, without sending full card details. Do not assume that cancelling a duplicate automatically creates a refund or transfers funds between orders. The team should confirm the operational and payment treatment separately so that the passenger knows what to expect at collection.
Distribute only the current instructions
Once the duplication is resolved, send the active confirmation to the travelling party and mark old copies as superseded in your own records. The passenger should have one airport, one local pickup date, one current contact and one set of meeting instructions. Check flight information through the official airport source close to travel, then communicate meaningful changes against the surviving reference. This keeps the booking history understandable without hiding or deleting the evidence of how the original confusion arose.
Questions about this journey
Can two identical flight numbers prove a duplicate booking?
No. Check the party, date, direction and full itinerary before deciding that two requests are the same.
Should I delete the earlier confirmation?
Keep it for your records, but clearly mark which reference the transfer team confirmed as active.
Does a duplicate cancellation guarantee a refund?
No. Ask the team to confirm the applicable payment and cancellation treatment in writing.