Skip to main content

Other Conversations

Every assistance issue comes with its own conversation. You can also create standalone conversations that aren't tied to an issue, for example to let your own support staff chat with a traveller through the same infrastructure.

Standalone conversations belong to your organization. Sitata's assistance team does not monitor them; your own staff take part as participants. If the traveller needs emergency assistance, create an issue instead.

Create A Conversation

With your organization token (or a staff user's token):

POST /api/v2/org/:company_id/conversations
{
"conversation": {
"name": "Booking support",
"participant_ids": ["<traveller id>", "<staff user id>"]
}
}
  • Every participant must belong to your organization, as a traveller or as staff.
  • When a staff user creates the conversation, they are added as a participant automatically.
  • Each participant receives a "new conversation" notification (type 6), or for whitelabel travellers, you receive a notification.suppressed webhook.

The response is a conversation in the same shape as an issue conversation (with issue_id: null).

List Conversations

GET /api/v2/org/:company_id/conversations         # all of your organization's conversations, most recently active first
GET /api/v2/org/:company_id/conversations?discrete=true # only conversations not attached to an issue
GET /api/v2/conversations # as a user: the conversations they participate in
GET /api/v2/conversations?discrete=true

Chat In It

Standalone conversations use exactly the same messaging as issue conversations. Join conversation:<id> on the socket and send messages, typing indicators and read receipts as described in Messaging.

Staff users take part the same way, using their own user token. Your organization token can list conversations, but only participants using their own user token can write in them.