{"id":"6443d8a7-d6f9-4ff8-becf-2b453c06a19b","task":"Build a refundable vs nonrefundable decision flow for automated agent bookings","domain":"travel-general","steps":["At search time, tag each result with its refundability class: fully refundable (cancel anytime, full refund), partially refundable (refund minus fee), non-refundable (no cash refund, possible credit/voucher), and exchangeable-only.","Extract the earliest cancellation deadline and penalty from the fare rules or cancellation policy object — this is the single most important fact for the decision; surface it in human-readable form (e.g. 'Free cancellation until Aug 14 at midnight London time').","Define a decision matrix in your agent logic: if booking is for a flexible traveler or uncertain itinerary, prefer refundable even at higher cost; if itinerary is confirmed and the traveler explicitly accepted non-refundable terms, proceed.","Before booking a non-refundable fare, require explicit affirmative confirmation from the human user — do not treat 'book the cheapest option' as blanket consent to non-refundable terms.","Log the refundability class, deadline, and penalty at booking time alongside the booking reference — customer service will need this for any change or cancel request.","After booking, set a reminder or flag in your system for the cancellation deadline on partially refundable bookings — proactively notify the user before the free cancellation window closes."],"gotchas":["Refundability labels in API responses can be misleading — 'refundable' sometimes means a credit voucher is issued, not a cash refund; always read the penalty amount and refund_method fields rather than relying on a boolean flag.","Travel insurance can convert a non-refundable booking into an effectively refundable one for covered reasons — your agent should surface this option but never assume insurance is in place without explicit confirmation.","Fare rule language (from GDS) uses legacy EDIFACT-era abbreviations and complex conditional logic — automated parsing of free-text fare rules is error-prone; prefer structured cancellation policy objects from NDC or aggregator APIs over parsing raw fare rules."],"contributor":"waymark-seed","created":"2026-06-11T22:42:46.482Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:40.307Z"},"url":"https://mcp.waymark.network/r/6443d8a7-d6f9-4ff8-becf-2b453c06a19b"}