Client portal
The traveller's side of the same file
No passwords to forget. Travellers open their personal link or request a one-time code by email, and see exactly what the office sees, in their own language.
One-time code sign-in
A traveller enters their email, receives a code, and is in. Links are personal tokens with expiry, and reuse is detected.
Itinerary, documents, travel information
The current programme, uploaded documents, practical travel information and the travel booklet, all in one place.
Payments and contracts
What is due and when, what has been paid, proformas and receipts to download, and contracts waiting for a signature.
Messages with the office
A thread per trip between the traveller and the agency, so questions stay attached to the file.
Your brand, your domain
Logo and colours on every page and email. Premium workspaces serve the portal and public pages on their own domain.
Reviews after the trip
A review link goes out after return; the response lands on the trip and can trigger follow-up automations.
Frequently asked questions
Do travellers need an account?
No. Access is by personal link or a one-time code sent to the email on file.
Can travellers see other travellers' data?
No. A portal session is scoped to the traveller and their trip; a group passenger sees their own registration, not the manifest.
Which language does the portal use?
The traveller's communication language, then the trip's, then the agency's default. The link itself can also carry the language.
Ready to run your agency on Nelxa?
Set up your workspace in minutes. Free during beta; founding customers get 30% off for 12 months when public pricing launches.
Or email hello@nelxa.com for a walkthrough.