automated replies included in ticket notes
ART-2027_KNOWLEDGE_NODE-37
If Channel is not email, it is sent from the email address configured in the snap-in under **Notification sender email address**.   - If no email snap-in is installed, the reply is sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). | Yes |\n| Replies to notification emails | Email reply | Response added to ticket thread | Yes |\n\n![]()\n\nEven when a reply comes via email, it\xe2\x80\x99s always synced into the customer\xe2\x80\x99s portal view.\n\nEmail experience from an
Email | Integrate | Snap-ins | DevRev
ART-1961_KNOWLEDGE_NODE-31
needed. For example, if the ticket is found to be spam, you can automatically add a comment to the ticket.\n\n**Suggest part**\n\nOften, your integrations create tickets or issues associated with a default part. The suggest part takes the ID of a ticket or issue and suggests a relevant part. You can use this to route your tickets or issues to the most appropriate part of the product. For example, when a ticket is created, you can find a relevant part and update the ticket with the suggested
Workflows | Computer by DevRev | DevRev
ART-15160_KNOWLEDGE_NODE-0
b"Airdrop does not sync comments created by automations or workflows back to external systems, because such comments usually don't contain any information relevant to the external system.\n\nExamples of such comments are comments that ask users whether the issue was correctly classified. Since these are not relevant outside DevRev (and would even pollute customers' data in the external system), they are not synced in syncs to the external system."
Airdrop automation-created comment sync