create ticket conversation for every new slack message
ART-2035_KNOWLEDGE_NODE-41
Slack threads, all the messages from both Slack threads reach only the primary ticket in DevRev, while messages from DevRev only sync to the primary ticket\xe2\x80\x99s Slack thread.\n* If only one ticket has a syncing Slack thread, that thread syncs with the primary ticket.\n* No messages from the duplicate ticket sync to Slack.\n* If a ticket is immutable but receives a new customer message in its Slack thread, a follow-up ticket is automatically created for future discussions.\n\n### New
Slack | Integrate | Snap-ins | DevRev
ART-6174_KNOWLEDGE_NODE-28
tickets\n--------------------------------\n\n**Manual conversion**\n\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\n\n![]()\n\n**Automated conversion via workflows**\n\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\n\n* When a conversation meets defined criteria\n* When the AI agent identifies an issue requiring escalation\n* According to custom business
Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev
ART-12391_KNOWLEDGE_NODE-26
with *Conversation created* or *Ticket\n   created*.\n\n   This trigger is whenever a conversation or ticket gets created by your\n   customers from Portal or Plug, or any of your integration which supports\n   conversation syncing, like Slack, WhatsApp, or email. You can find the\n   integrations in our marketplace.\n2. Add the *Talk to agent* step as the next action. Fill all the required values\n   of this step. The values needed to fill here are explained below.\n3. Deploy the
Conversational workflows | Workflows | Computer by DevRev | 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-2035_KNOWLEDGE_NODE-46
**Auto-create incidents from Slack channels**, which automatically creates an incident for every direct message posted in specified Slack channels.\n\nThe first two options will open a pop-up modal with a new incident form, with some fields pre-populated based on the context.\n\n### Sync options\n\nIncidents support syncing messages both within a dedicated Slack thread and across an entire Slack channel, including all associated threads. The sync target is determined by the **Sync for new
Slack | Integrate | Snap-ins | DevRev
ART-4199_KNOWLEDGE_NODE-27
message.channels.\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\n\nConfigure DevRev\n----------------\n\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\n2. Add the channel IDs for either incidents, tickets or issues.\n3. Click the respective buttons to enable the sync between threads.\n4. Select the part ID to associate a particular part.\n5. Click **Save** and copy the
Slack message agent | Automate | Snap-ins | DevRev
ART-4199_KNOWLEDGE_NODE-25
DevRev.\n\n![]()\n\nFor more information, refer to the [Slack message agent](https://marketplace.devrev.ai/slack-message-agent) on the DevRev marketplace.\n\nInstall\n-------\n\n1. Install the DevRev [Slack app](/docs/integrations/slack).\n2. Install the Slack message agent in your org.\n\nConfigure the custom Slack bot\n------------------------------\n\n1. Go to [Slack API](https://api.slack.com/apps) and create a new app **From scratch**.\n2. Go to *Basic Information*\\* > **App Credentials**
Slack message agent | Automate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-31
creating conversations from any Slack channel:\n\n1. Link the DevRev Customer workspace to the channel by running /devrev link in the channel.\n2. In the pop-up modal, search for the DevRev Customer workspace.  \n   2a. Select the preferred workspace and click **Link**.  \n   2b. If your channel is already linked to a workspace, the modal will show the details of the workspace and an option to unlink.\n3. Once linked, new contacts identified via Slack are automatically added to the associated
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-32
workspace. When creating work items, the linked customer workspace is pre-selected for quick access.\n4. Invite the DevRev app to a channel by running /invite @DevRev in the channel.\n\nOnce the above steps are completed:\n\n* Messages sent by customers directly to the channel will create new conversations.\n* Any messages in thread, or channel messages by members from your own team won\xe2\x80\x99t create new conversations.\n* Created conversations can be located in the **Inbox vista** in your
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-45
Creating issues with sync enabled from external channels is not supported.\n\nDevRev Incidents and Slack\n--------------------------\n\n![]()\n\nIncident Management is available as a **beta feature**. Contact the support team to enable it before configuring incident settings.\n\nThe Slack snap-in allows incident creation directly from Slack using the following methods:\n\n* Use the /devrev create-incident command.\n* Select **Create a new incident** from the message actions.\n* Enable
Slack | Integrate | Snap-ins | DevRev
ART-1300_KNOWLEDGE_NODE-85
https:// api.devrev.ai / conversations.create\nCreates a conversation.\nRequest.\n\nThis endpoint expects an object.\ntype "support" Required\ndescription string Optional\nDescription for the conversation.\ngroup string Optional\nThe group that the conversation is associated with.\nis_spam boolean Optional\nWhether the conversation is spam.\nmembers list of strings Optional\nThe users in the conversation.\nmessages list of objects Optional\nInitial messages on the conversation.\nShow 2
Create — DevRev | Docs
ART-1506_KNOWLEDGE_NODE-4
https://api.devrev.ai/conversations.create \\  \n    ---|---  \n    >|      -H "Authorization: Bearer <token>" \\  \n    >|      -H "Content-Type: application/json" \\  \n    >|      -d \'{  \n    >|   "type": "support"  \n    >| }\'\n[/code]  \n  \nTry it\n\n201Created\n\n[code]\n\n    1| {  \n    ---|---  \n    2|   "conversation": {  \n    3|     "id": "id",  \n    4|     "members": [  \n    5|       {  \n    6|         "type": "sys_user",  \n    7|         "id": "members"  \n    8|       }
Create Conversation (Beta) — DevRev | Docs
ART-2035_KNOWLEDGE_NODE-30
organization.\n\nList of available commands\n--------------------------\n\nAfter installation, visit your Slack workspace and enter the command /devrev help. A pop-up modal will display all the available commands.\n\nCreate DevRev conversations from Slack\n--------------------------------------\n\nThe snap-in enables support teams to manage customer interactions directly from DevRev. You can enable this feature by toggling the **Sync conversations from Slack to DevRev** setting.\n\nTo start
Slack | Integrate | Snap-ins | DevRev