Slack ticket creation manual vs automated configuration
ART-2035_KNOWLEDGE_NODE-37
synchronized between DevRev and Slack.\n\nWork management using Slack\n---------------------------\n\n### DevRev Tickets and Slack\n\nThe Slack snap-in allows users to create tickets directly from Slack. There are multiple ways to initiate ticket creation from any channel:\n\n* **Use the command:** Run /devrev create-ticket.\n* **Message action:** Select **Create a new ticket** from the message actions.\n* **Convert a Conversation:** Transform an ongoing conversation into a ticket. This is
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-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