conversation.{app_id}.{user_id}

{
    "id": 6779974,
    "created": 1449993141,
    "replied": false,
    "message": 6592,
    "type": "email",
    "reply_type": "text",
    "part_last": {
        "id": 7493777,
        "created": 1449993141,
        "first": true,
        "conversation": 6779974,
        "body": "<p>Some message</p>",
        "read": false,
        "type": "reply_admin",
        "sent_via": "message_auto",
        "from": {
            "avatar": "https:\/\/files.dashly.app\/avatars\/1418112360347-00000100.jpg",
            "type": "default_admin",
            "name": "Dmitriy"
        }
    },
    "parts_count": 1,
    "unread_parts_count": 1,
    "last_admin": {
        "avatar": "https:\/\/files.dashly.app\/avatars\/1418112360347-00000100.jpg",
        "type": "default_admin",
        "name": "Dmitriy"
    },
    "last_update": 1449993141
}

This channel receives messages when a new conversation with user {user_id} is started. Message format is almost similar to conversation.{app_id} channel.

We’re using this channel on the visitor’s to the site side of chat. Thus, there are differences:

• no user field
• no clicked, unsubsribed, closed, read fields
• no assignee field
• parts_count counter counts only parts visible to user (his and administrator’s answers)
• part_last shows last part visible to user (in case last part is a note it is not visible to the user, thus not shown)
• no tags field