tickets reopening automatically when moved to Awaiting Customer response due to convergence bot
ART-2009_KNOWLEDGE_NODE-28
ticket's stage when linked issue is linked or unlinked.\n* Close pending tickets if they have remained in the *Awaiting customer response* stage for longer than x days.\n* Update ticket's stage to waiting on user when user reverts on new conversation.\n* Update ticket's stage to *Accepted* and notify owner and customers when an enhancement in ideation stage is linked.\n* Update a spam conversation's stage to *Suspended*.\n* Update a spam ticket's stage to
Convergence | Automate | Snap-ins | DevRev
ART-2012_KNOWLEDGE_NODE-28
say \xe2\x80\x9cI would like to add a terminal stage on my tickets\xe2\x80\x9d and we will get it done.\n\n  * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\n\n  * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your
Follow-up ticket | Automate | Snap-ins | DevRev
ART-2009_KNOWLEDGE_NODE-24
[Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Convergence](/docs/automations/converge)\n\nConvergence\n===========\n\nConverge support and build by bringing together conversations, tickets, and issues.\n\nOnce the convergence snap-in is installed, tickets and issues automatically change states when related tickets and issues do. These state changes are visible in the **Discussions** and **Events** tabs of tickets and issues.\n\n![]()\n\nWorkflows\n---------\n\nThe workflows present in
Convergence | Automate | Snap-ins | DevRev