Notes
Add internal notes to an extra for context and traceability.
Overview
The Notes tab is an internal field for storing operational context and team communication for an Extra product.
You’ll typically find it as the last tab in the Extra’s configuration.
Notes are internal only. They do not populate the website, offers, tickets, or other customer-facing documents.
When to use Notes
Use Notes to add context that helps colleagues understand what was changed and why.
Common use cases:
Internal clarifications: Provider rules, operational constraints, or exceptions.
Change log: Why a price, resource, or allotment was changed.
Team instructions: What to do during cancellations, re-bookings, or manual handling.
Input Type: Free-form text.
Usage Instructions:
Be concise: Write clear, actionable information.
Timestamp entries: Start with date + initials.
Keep it product-level: Avoid customer-specific information.
Save your changes: Use Save after editing. The field may not auto-save.
Recommended note format
Use a consistent format so others can scan and trust the history:
FAQ
Are Notes visible to customers (web, offer, ticket, emails)?
No. Notes are meant for internal use only.
Should I write one long note, or multiple dated entries?
Use multiple dated entries. It keeps a clean audit trail and avoids overwriting context.
My note is only relevant for one brand. What should I do?
Start the note with the brand name (for example Tourpaq SE:) so it’s clear.
What kind of content should not be written in Notes?
Avoid:
Passenger personal data (names, passports, phone numbers, emails)
Payment details
Anything that belongs in a booking-specific service case
I updated the note but it didn’t “stick”. Why?
Most often, the page wasn’t saved.
After editing the Notes text area, click Save.
Related pages
Last updated
Was this helpful?