Messages is the in-app chat between you and your clients. Each conversation is tied to one booking request, so the thread stays with the booking rather than scattering across email. This article covers where threads come from, how to use the inbox, and what happens when a booking changes hands.
Finding your messages
Messages is a top-level item in the consultant navigation. The red badge next to it is your total unread count across all conversations, and it updates in real time as clients reply. Clicking it opens Messages, whose subtitle reads either “N unread” or “Client conversations”.
On a wide screen the page is two columns: Conversations on the left, the selected thread on the right, with “Select a conversation to start messaging” until you pick one. On a phone you get the list first, then the thread full-screen with a Back to conversations link.
Each row in the list shows the client's name, the request number, a preview of the last message, how long ago it was sent, and an unread count. Unread rows are shown in bold, and closed conversations carry a Closed tag.
Where conversations come from
You do not create threads from the Messages page. A conversation appears in one of two ways:
- When you claim a booking request. Claiming opens a thread between you and the client and posts the system message “<your name> has been assigned to your request.”
- From a Chat button. Booking Queue cards, the request details modal and the supplier payment detail page all carry a Chat button that opens the thread for that request in a pop-up panel — creating it on the spot if it does not exist yet. The button shows its own unread badge.
There is exactly one conversation per booking request, so the pop-up panel and the Messages page always show the same thread. Clients reach the same thread from their own bookings pages.
Sending a message
- Select the conversation. The header shows the client's name and the request number.
- Type in the box marked Type a message... at the bottom. The box grows as you type.
- Press Enter to send, or Shift + Enter for a new line. You can also click the send arrow.
- A message appears for both sides once TravelFlow has saved it, usually within a second; your own messages are shown on the right of the thread. A message can be up to 4,000 characters.
TravelFlow writes every message and every system notice itself: a message carries the name on the sender's profile, and the notices are worded from the booking records. Nobody can post as another person or as the system, or change a message once it is sent.
Opening a conversation clears your unread count for it. The client gets a Message from <your name> notification containing the first part of your message; when they reply, your notification links straight back to Messages.
Closed conversations
A conversation can be marked closed. When it is, the list shows a Closed tag, the message box is disabled and its placeholder changes to Conversation closed. You can still read the full history; you just cannot post to it. Use email or a new booking request to continue the discussion.
When something goes wrong
- “Chat opens once a consultant is assigned to this request.” The Chat button cannot identify both parties yet — claim the request first.
- “Message failed to send. Please try again.” The text you typed is kept in the box so you can retry. If it keeps failing, reload the page and check you are still signed in.
- “Could not open chat. Please try again.” The conversation could not be created; retry from the Messages page or the request details modal. When TravelFlow knows why (for example, the request has no consultant yet), the button says so instead.
- No conversations listed. The list shows “No conversations yet” until you claim a request or open a chat from one. Threads are only visible to the consultant currently assigned to the request.