The group room: settings, reports, what the office sees

On Pro, each departure can have a group: one text-only thread where the travelers who have the app, the guides and your office write to each other. It is off for every departure until you turn it on, your guide and your office moderate it, the Inbox stays the receipted channel for anything that must reach everyone, and the group becomes read-only when the trip ends and is deleted 30 days later.

Where it is, and what it needs

Open a departure and choose the Group tab, between Updates and Who's ready. Turning the group on needs three things, and the switch tells you which one is missing in a plain sentence:

Flip the switch labeled Group chat — the text-only group for this departure, off until you turn it on, moderated by your guide and your office, gone 30 days after the trip — to On under Settings at the foot of the tab. "The group is on. Travelers see a Group tab in the app at their next sync." Switching it Off removes the tab from every phone at its next sync; the messages stay on the dashboard.

Settings

The thread

Every message, newest first, live while the tab is on screen ("Live — new messages appear here as they land"), with a search box for a word or a name. Each message shows who wrote it — a traveler as "Margaret H.", a guide with a Guide chip, your staff with an Office chip, your connected system with an API chip — plus Question · unanswered or · answered, Pinned, and, under "Travelers ask", Only guides and the office see this. Under each message:

To write as the office, use the box above the thread — "Write to the group, as the office". It goes out under your name. The hint beside it is the rule: need everyone to see it, with receipts? Send it as an update instead. A group message has no receipts and no exception list.

Reports, and the 24-hour clock

A traveler or a guide can report any message with one of four reasons: Rude or abusive, Selling something, Not about the trip, Something else. When one is made:

Each entry in the queue shows who reported it and why, the message as it read when it was reported, and one row of decisions: Remove message, Put the message back (only for one hidden by reports — restored exactly as written), Stop Robert posting, Remove Robert from group, and Dismiss (nothing else happens; a message hidden by reports stays hidden unless you put it back). One decision closes every open report on that message. Handled reports stay listed below the thread.

The reporter is named here and nowhere else. Never to the person reported, never on any phone. Treat the queue accordingly.

What the office sees that travelers don't

And what the office is not told: who has read a message (there are no receipts in the group), who has left the group (leaving tells nobody), and who has blocked whom (a block only hides that person's messages from the reader who set it, and the server tells nobody). A traveler who needs separating from another is your call, made on what you can see: the messages and the reports.

Cordelle's part

Cordelle can close a group without you, and will if a report goes unanswered past the 24-hour clock or content must come down at once. The tab then says "Cordelle closed this group on date. Write to [email protected] to reopen it." The messages stay for your review and export, and the switch stays shut until we reopen it. This is the developer account's obligation to the App Store and Google Play, and it is the reason every report is copied to us.

Notifications

The group never puts a message's words in a notification. A traveler's phone gets a count — "Group: 3 new messages" — at most once every two hours by default, never in quiet hours, on its own quiet channel; a reply to their own message or their question being answered gets its own heads-up, still never in quiet hours. Each traveler can choose Every message, A few times a day, Only when someone answers me or Never, and can quiet the group for a night or for the rest of the trip. None of that touches your updates.

Your duties as the operator

Your own system

With the full API, your booking system can read a departure's group, switch it on or off with the same rules as this tab, post under its key's name marked "(API)", and remove a message; and your webhooks hear room.post.created and room.post.reported — ids and the reason, never the words. Reports are handled here, where the reporter can be named. Details on the developer page.

Billing

The Billing page's Features list reads Group chat — on (the same group: text only, one per departure, off until you turn it on, moderated by your guide and your office, gone 30 days after the trip) on Pro and the trial, and not available on this plan on Companion. A running group keeps going whatever your plan does later.

← Back to the Help Center [email protected]