Slack connector message handling CONV objects
ART-2035_KNOWLEDGE_NODE-54
given DevRev user   - Can be used to later send direct messages to the user on the Slack using Send message to Slack node. | - Slack connection   - DevRev user id | - Slack user id |\n| Start Thread Sync | - Set up 2 way message synchronization between a Slack thread and a DevRev object discussion. | - Slack connection   - DevRev Object ID   - Slack channel ID   - Slack thread ID (message ID of parent message, returned by send message to Slack workflow node) | N/A |\n| Start Channel Sync | -
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-33
DevRev app.\n\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\n\n![]()\n\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\n\nConversation roll window\n------------------------\n\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\n\n* The roll window remains active for five
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-55
Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection   - DevRev object ID   - Slack channel ID | N/A |\n\nAdditional capabilities and limitations\n---------------------------------------\n\n### 2-way sync between DevRev and Slack\n\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\n* By default, messages from bots, service
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-36
Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\n\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\n* Notification threads are not
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-34
minutes after a conversation is created.\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\n* A new direct message from the customer resets the roll window timer.\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\n* Only messages within the thread of the originating message of the conversation are synced.\n* Messages within Slack threads of follow-ups sent directly to
Slack | Integrate | Snap-ins | DevRev
ART-6174_KNOWLEDGE_NODE-30
there.\n\n![]()\n\nSlack end-user experience\n-------------------------\n\nWhen a conversation is converted to a ticket in Slack:\n\n* Ticket information appears within the same thread.\n* All subsequent messages sync with the newly created ticket.\n* The transition is seamless for the end user.\n\nConversation conversion scenarios\n---------------------------------\n\nConsider converting a conversation to a ticket in these scenarios:\n\n* Complex issues requiring in-depth investigation\n*
Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev
ART-2035_KNOWLEDGE_NODE-56
accounts, or AI agents in DevRev aren\xe2\x80\x99t synced to Slack. To change this, enable the **Sync bot messages from DevRev to Slack** option in snap-in configurations.\n* The snap-in supports syncing of message edits and deletions between platforms.\n* Message attachment sync is supported both ways, with a file size limit of 250MB.\n\n### Inviting DevRev app to channels\n\n* Adding the DevRev app to many Slack channels can be challenging at scale.\n* Use the /SlackInviteBot command from the
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-40
channel determines the sync location in DevRev:\n\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\n\nSyncing different panels to separate Slack threads is not supported.\n\n![]()\n\nOnly shared tickets are synchronized between DevRev and Slack.\n\n### Follow-up and merged Tickets\n\nThe Slack snap-in supports follow-up and merged tickets.\n\n* When two tickets merge, and both have syncing
Slack | Integrate | Snap-ins | DevRev
ART-4271_KNOWLEDGE_NODE-28
PLuG widget:\n\n  * The ticket number and basic details appear in the same conversation pane.\n  * Users can click **Details** to view complete ticket information.\n  * If the **Tickets** tab is enabled in PLuG, users can track their ticket status there.\n\n### Slack experience\n\nWhen a conversation is converted to a ticket in Slack:\n\n  * Ticket information is sent within the same thread.\n  * All subsequent messages sync with the newly created ticket.\n  * The transition is seamless for the
Convert Conversations to Tickets | Conversations | Support | DevRev