Cruise Ship Shore Excursion Refund Request Form
Use this shore excursion refund request form to collect the booking details, issue description, and refund preference needed to review a cancelled or unsatisfactory excursion. It gives guests a clear way to submit supporting information and tells them what happens next.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Cruise Lines · Travel And Hospitality · Tour Operations · Guest Services
Overview
This Cruise Ship Shore Excursion Refund Request Form is built to capture the information staff need to review a refund request without chasing the guest for basics later. It gathers submission notice consent, guest and voyage details, excursion specifics, the reason for the request, supporting documents, and a final acknowledgment that the information is accurate and that the guest authorizes contact.
Use this template when a shore excursion is cancelled, altered, or unsatisfactory and the guest needs a formal way to request a refund. It is especially useful when multiple parties may need to review the request, such as guest services, shore excursions, and a third-party vendor. The form creates a clean audit trail and keeps the review focused on the booking, the incident, and the requested refund method.
Do not use this form as a general complaint box or a broad customer survey. If the guest only wants to share feedback with no refund request, a separate feedback form is a better fit. Also avoid collecting unnecessary PII or overly detailed personal information. Keep the fields tied to the refund decision, use conditional logic for the “other” reason field, and make the next step after submission explicit so guests know whether they will receive a confirmation, follow-up questions, or a decision timeline.
Standards & compliance context
- Keep the form aligned with GDPR data minimization by collecting only the guest and voyage details needed to review the refund request.
- If the form is public-facing, make the fields and labels accessible under WCAG 2.1 AA, including clear required markers and keyboard-friendly controls.
- Avoid collecting unnecessary sensitive data, and do not ask for passport numbers, payment card details, or other PII that is not needed for the refund decision.
- Use the consent_to_review and authorization_to_contact language to make the review process and follow-up communication explicit.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section sets expectations up front by telling the guest what happens after submission and what they are consenting to.
- What happens after I submit this form?
- I understand my submission will be reviewed and may be shared with Guest Services and Finance for refund processing.
Guest and Voyage Information
These fields identify the traveler and reservation so staff can match the request to the correct booking without extra follow-up.
- Guest name
- Cabin number
- Voyage number
- Contact email
- Contact phone
Shore Excursion Details
This section ties the refund request to the exact excursion, port, date, and party size involved.
- Excursion name
- Port of call
- Excursion date
- Booking reference
- Number of guests on this booking
Refund Request Details
These fields explain why the guest is requesting a refund and what outcome they want.
- Reason for refund request
- If other, please describe
- Describe what happened
- Preferred refund method
Supporting Details
This section captures evidence and staff notes that help verify the claim and document the review.
- Supporting documents or photos
- Witness names or staff notes, if available
- Additional comments
Guest Acknowledgment
This final section confirms the guest believes the information is accurate and agrees to be contacted if clarification is needed.
- I confirm the information provided is accurate to the best of my knowledge.
- I authorize Guest Services to contact me about this request using the details provided.
How to use this template
- 1. Configure the submission notice so the guest sees what happens after submit and agrees to review before entering any personal or booking information.
- 2. Set up the guest, voyage, and excursion fields with the correct field types, including date picker, email, phone, numeric input, and short text fields for booking references.
- 3. Add conditional logic to show the refund_reason_other field only when the guest selects an option that requires extra explanation.
- 4. Route submissions to the shore excursions or guest services owner, and include the booking reference in the notification so staff can verify the reservation quickly.
- 5. Review the supporting documents, witness or staff notes, and guest acknowledgment together before approving, denying, or escalating the refund request.
Best practices
- Mark only the fields needed to verify the booking and assess the refund as required, and leave the rest optional.
- Use a date picker for the excursion date and a numeric input for number of guests so the form is faster to complete and easier to validate.
- Keep the refund_reason list short and specific, then use an other field only when the preset options do not fit.
- Explain in the submission notice what happens after the guest submits, including whether a team member will contact them for more information.
- Ask for supporting documents only when they help resolve the request, and state acceptable file types and size limits.
- Use progressive disclosure so guests do not see extra explanation fields unless their selected reason requires them.
- Include a clear authorization to contact checkbox if staff may need to follow up about missing booking details or evidence.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should a guest use this refund request form?
Use it when a shore excursion was cancelled, significantly changed, or did not match what was promised. It also works when a guest wants to request a partial or full refund after a service issue. If the matter is only a simple schedule question, a refund form is usually the wrong starting point. This template is meant to document a refund request, not replace the operator’s incident review process.
Who should review and approve submissions?
Typically the shore excursions team, guest services, or the onboard operations manager reviews the request first. If the excursion was run by a third-party vendor, the form can be routed to the vendor contact for validation before a decision is made. Keep the approval path clear so guests are not left guessing. If your process includes finance, add that step only after the operational review is complete.
What refund reasons should this form include?
Include common options such as cancellation, missed port, safety issue, service not delivered as described, and dissatisfaction with the excursion experience. The template also includes an other field for cases that do not fit the preset list. Use conditional logic so the guest only sees the extra explanation field when needed. That keeps the form shorter and reduces incomplete submissions.
Should this form collect supporting documents?
Yes, if guests may have photos, receipts, or written confirmation that helps explain the issue. Keep the upload field optional unless your policy requires proof for certain refund types. Be specific about acceptable file types and size limits so the submission does not fail. If you do not need a document to make a decision, do not collect it.
How often is this form used?
It is used whenever a guest submits a refund request, so the cadence is event-driven rather than scheduled. That makes consistency important: every submission should capture the same core fields for comparison and audit trail purposes. If your operation handles many excursions, standardizing the form reduces back-and-forth. It also helps staff identify recurring issues by port, vendor, or excursion name.
Can guests submit this anonymously?
Not usually, because refund processing requires booking details and a way to contact the guest. If you want to support anonymous feedback about the excursion itself, use a separate feedback form rather than this refund request form. This template includes contact fields and an authorization to contact checkbox so the team can follow up. That keeps the refund workflow tied to a real reservation and a clear communication channel.
What are the most common mistakes when using this template?
The biggest mistake is asking for too much information, especially fields that are not needed to verify the booking or assess the issue. Another common problem is using free-text fields where a date picker, numeric input, or multi-select would be easier to complete and review. Teams also forget to explain what happens after submission, which creates follow-up confusion. Finally, if you collect any personal data, you should state how it will be used and who will review it.
How can this form connect to existing systems?
It can route submissions to guest services, a shared operations inbox, a CRM, or a ticketing system for review and tracking. If your workflow uses booking software, map the booking reference field so staff can verify the reservation quickly. You can also send an automated confirmation to the guest after submission. Keep integrations focused on the review process rather than adding unnecessary systems that slow down resolution.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
Spring '26 brings service desk tickets, performance reviews, goals, and feedback directly into the MangoApps employee dashboard—no extra logins needed.
-
Employee app solutions that close communication gaps, keep frontline teams informed, and help prevent costly corporate crises.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
Ready to use this template?
Get started with MangoApps and use Cruise Ship Shore Excursion Refund Request Form with your team — pricing built for small business.
