--- title: Designing Cancellation and Refund Flows description: "Cancellation is where empathy meets clarity. Show the policy first, confirm the consequence, communicate the refund timeline, and let the AI handle the emotional weight." canonical: https://nowah.xyz/blog/designing-cancellation-refund-flows lastModified: "2026-08-07T07:59:21.055Z" --- # Designing Cancellation and Refund Flows Cancellation is where empathy meets clarity. Show the policy first, confirm the consequence, communicate the refund timeline, and let the AI handle the emotional weight. Nobody cancels a trip happily. Plans change. Emergencies happen. Work conflicts arise. The person clicking "Cancel" is already having a bad day. The cancellation flow should not make it worse. This sounds obvious, but most cancellation experiences are adversarial by design. Hidden policies, confusing confirmation dialogs, unclear refund timelines, and aggressive retention tactics ("Are you SURE you want to cancel?") treat the user as a revenue problem rather than a human in a difficult situation. We design cancellation as an act of service. The same trust that earned the booking should carry through the cancellation. ## Policy display before the cancel button ![Illustration for this section](https://pics.nowah.xyz/website-media/design-033-img-1.webp) The cancellation policy is shown before booking, not after. This is a pre-booking trust signal — the user sees exactly what will happen if they need to cancel before they commit any money. In the review modal, the cancellation policy appears in plain language near the top of the information hierarchy: "[Free cancellation](/blog/hidden-cost-of-free-cancellation) within 24 hours. After that, a $75 cancellation fee applies, and you will receive the remainder as a refund." or "This is a non-refundable fare. If you cancel, you may receive airline credit for future use." The language is specific. Not "cancellation fees may apply" — the actual fee. Not "subject to airline policies" — the actual policy. Specific language prevents the nasty surprise that users remember more than anything else about a bad booking experience. When the user later initiates a cancellation, the same policy is shown again, now in the context of their specific booking: "Your flight to Tokyo was booked with a flexible fare. Cancelling now will refund $280 of your $320 fare. The $40 cancellation fee is deducted from your refund." ## The confirmation dialog The cancellation confirmation dialog is not "Are you sure?" That question is a guilt trip dressed as a safety measure. It does not provide information. It creates doubt. Our confirmation dialog states the consequence: "Cancel your flight to Tokyo on April 5th? You will receive a $280 refund to your original payment method within 5 to 10 business days. The $40 cancellation fee will be deducted." The dialog has two buttons. "Keep my booking" is the primary action, styled with the accent green. "Cancel booking" is the secondary action, styled in a muted, non-alarming tone. The visual hierarchy gently favors keeping the booking — not through manipulation but through the reasonable default that most people opening a cancellation dialog are checking the consequences rather than definitely cancelling. The dialog does not use aggressive retention language. No "You will lose your amazing deal!" No "Prices have gone up since you booked!" The user has made a decision. The interface respects it by providing clear information and clean options. ## Refund timeline communication ![Supporting diagram](https://pics.nowah.xyz/website-media/design-033-img-2.webp) After cancellation is confirmed, the [most important](/blog/why-speed-is-most-important-feature) piece of information is when the money comes back. Uncertainty about refund timing creates anxiety that persists long after the cancellation is processed. The confirmation screen states the refund amount and the timeline explicitly: "$280 will be refunded to your Visa ending in 4242. Expect it within 5 to 10 business days, depending on your bank." The specificity — the card, the amount, the timeline range, and the reason for the range — eliminates ambiguity. We follow up with a confirmation notification and email containing the same information. The refund timeline is tracked, and if the refund is processed by the payment provider, the user receives a notification: "Your $280 refund has been processed. It should appear on your statement within 2 to 3 business days." This proactive communication about the money's journey removes the need for the user to check their bank statement daily or contact support to ask "Where is my refund?" ## AI as empathetic handler In a chat-first interface, the cancellation can happen through conversation. The user says "I need to cancel my Tokyo flight." The AI responds with empathy and clarity. "I understand — plans change. Let me pull up your booking. Your flexible fare allows cancellation with a $40 fee. You would receive $280 back to your Visa card within 5 to 10 business days. Would you like to go ahead with the cancellation?" The AI's tone is empathetic without being performative. "I understand" acknowledges the situation. The immediate pivot to clear, specific information respects the user's time. The question at the end gives the user agency to proceed or reconsider. If the user confirms, the AI processes the cancellation and reports the result: "Done. Your Tokyo flight is cancelled. Your $280 refund is being processed — expect it within 5 to 10 business days. I have sent a confirmation to your email." The conversational handling has an important advantage over form-based cancellation flows: the AI can suggest alternatives. "Would you like to look at different dates instead?" or "I could check if there is a rebooking option with a smaller fee." These suggestions are offered once, gently, and only when relevant. They are not retention tactics — they are genuine alternatives that the user might not have considered. ## Post-cancellation behavior After a cancellation, the trip status updates throughout the app. The trip card in the Trips tab shows "Cancelled" with the refund status. The [trip detail view](/blog/designing-trip-detail-view) updates the affected segment. The Documents tab retains the cancellation confirmation. The AI does not pretend the cancellation did not happen. If the user returns to the chat, the AI might say "I see your Tokyo trip was cancelled. Would you like to plan something else?" This acknowledgment maintains conversational continuity. We avoid post-cancellation marketing. The user just cancelled a trip — they do not want to be sold another one immediately. The suggestion to "plan something else" is offered once, in the first conversation after cancellation. After that, the AI reverts to its standard greeting behavior. Cancellation flows reveal a product's true character. Any product can be delightful when the user is spending money. The products that earn lasting trust are the ones that handle the difficult moments — the cancellations, the refunds, the plan changes — with the same care and clarity they bring to the booking itself. --- Nowah is an AI travel agent that searches and books real flights and hotels through conversation — no filters, no thirty open tabs. [Plan your next trip](https://app.nowah.xyz).