Customer Information on Resort setup

Configure resort-level customer information (errata) in Tourpaq Office. Set travel/booking periods, guest messages for tickets/WebBooking, and required acknowledgment in the booking flow.

How to access: Setup → Resorts → open a resort → Passenger Information.

This is where you define resort-specific customer information (errata) and guest notifications shown in the booking flow and on customer-facing outputs.

Overview

Use Passenger Information on a resort to add resort-specific messages (often called Customer information / errata) that appear on:

• Tickets

• WebBooking

• The booking flow and booking confirmation screens

You can also make the message mandatory to acknowledge before the booking can be completed.

Purpose

Ensure customers (and staff) see the right information for the selected resort, for the correct travel period—and (optionally) confirm they have read it.

Preconditions

• You have administrative access to Tourpaq Office.

• The resort already exists in Setup → Resorts.

• If you want brand-specific wording, the brand must have Use custom text enabled.

Navigation path

Setup → Resorts → (open resort) → Passenger Information

Passenger Information on a resort: manage guest notifications shown in the booking flow, tickets, and WebBooking.

---

How it works (what you see on the Passenger Information tab)

On the Passenger Information tab you’ll typically see:

• A list of existing rules/entries (or “There are no entries to show” if none exist)

• Create, Edit, and Delete actions

• Pagination (25 rows per page)

• A Default text tab

• One tab per brand (only for brands where Use custom text is enabled)

Default text vs. brand-specific text

• Default text is the “base” message.

• Brand tabs let you override only the message text for that brand, while keeping the same date logic.

---

Create a new resort message

1

Open the resort

1. Go to Setup → Resorts.

2. Click the resort you want to configure.

You are now on the resort edit page.

2

Go to Passenger Information

Open the Passenger Information tab to view existing entries.

3

Click Create

Click Create to add a new entry.

A form opens with Save and Cancel.

4

Fill in the rule fields

Travel period (required)

• From: start date of the period where the message applies

• To: end date of the period where the message applies

Booking date period (optional)

• Booking date from: only show/apply the message for bookings created on/after this date

• Booking date to: only show/apply the message for bookings created on/before this date

Message text

• Information for customer on ticket: the text shown on tickets, WebBooking, and booking screens (opens in a pop-up editor)

Acknowledgement

• Acknowledge (checkbox): when enabled, the user/customer must actively confirm the message during the booking flow (checkout).

If you enable Acknowledge, the booking flow will block completion until all required messages are confirmed.

5

Save

Click Save.

• If the entry is valid, you’ll see a success message.

• If something is wrong, you’ll see a warning/error explaining what needs to be fixed.

---

Validation rules (important)

Date range checks

• To must be later than From.

Overlap checks (to avoid conflicting messages)

The system prevents multiple entries that cover the same period.

• Entries without booking-date limits are compared only with other entries that also have no booking-date limits.

• Entries with booking-date limits are compared only with other entries that also have booking-date limits.

If you need different wording in different periods, split the travel period into non-overlapping ranges.

---

Edit or delete an existing entry

Edit

1. Click Edit on the entry.

2. Update the fields.

3. Click Save.

Delete

1. Click Delete on the entry.

2. Confirm the deletion.

The entry is removed and a success message is shown.

---

Brand-specific configuration (override the text per brand)

Use this when the same rule (same dates) should have different wording for different brands.

1. Open the resort’s Passenger Information tab.

2. Go to the relevant brand tab.

3. Click Edit on the entry.

You will see the rules from Default text, but only Information for customer on ticket is editable.

1. Update the text and click Save.

---

FAQ

What should I write in “Information for customer on ticket”?

Write short, clear, actionable information—such as local rules, check-in instructions, meeting point details, or temporary operational changes.

If the message is long, use:

• short paragraphs

• bullet points

• clear headings (where relevant)

What’s the difference between “Default text” and a brand tab?

• Default text is the standard message.

• A brand tab lets you override the message wording for that brand only (the date periods and rule logic stay the same).

When should I use “Booking date from/to”?

Use booking-date limits when the message should only apply to bookings created during a certain sales period (for example: “Only for bookings made after 1 Jan”).

If you want the message to apply to all bookings for a travel period, leave booking dates empty.

I can’t save my entry. What should I check first?

Most save issues are caused by:

• To being earlier than (or equal to) From

• The new entry overlaps an existing entry in a way the system does not allow

Adjust the dates (or split the period) and try again.

Can I have multiple resort messages for the same travel period?

Not if they overlap. The system blocks overlapping rules to prevent conflicting information.

If you need multiple messages, consider:

• Combining them into one message, or

• Splitting the travel period into smaller non-overlapping ranges

I edited the text on a brand tab, but I still see the default text. Why?

Common causes:

• The brand does not have Use custom text enabled

• You edited the wrong brand tab

• The output you’re checking is tied to a different brand than expected

If you’re unsure which brand the booking uses, verify the booking’s brand first.

What happens if I enable “Acknowledge”?

The message becomes mandatory to confirm during the booking flow. The user/customer must check the confirmation checkbox(es) before they can proceed.