Help centre / Clients and pipeline

Keep client conversations private

Choose the correct portal recipient and keep booking-party conversations separate on a shared trip.

Choose the right context

A traveller link and a booking-buyer link have different scope. Create the link for the intended person and share it with that recipient. Keep it private; anyone who has an active private link may be able to open its scoped view.

Use the conversation, not the internal note

Messages are the place for text and files the client should see. Private agency notes are separate. Staff note history and mentions remain in their permission-checked context, and note bodies are not emailed.

Shared trip does not mean shared inbox

A group departure can include several unrelated booking parties. Their private conversations and attachments must not be treated as a group discussion. Open the appropriate traveller or booking-buyer thread before replying.

Notifications are prompts

Recipient-scoped alerts point back to the conversation. Access is checked again before delivery and when opening a thread or attachment. An old message notification is not a permanent right to keep reading a reassigned trip.

Review the practical actions

1. Confirm that the message belongs to the correct client or booking.
2. Read any attached file in the permitted context.
3. Update the underlying booking or document record when needed.
4. Verify reported transfers against the bank statement rather than treating a report as receipt.
5. Revoke a private link if it has been shared with the wrong person.

The portal is not a universal client login, a public group chat or a connected Gmail/Outlook mailbox.

Still stuck? Email hello@ahmadzunair.online.