case notification when a ticket is created, assigned, and notification with support response
ART-1953_KNOWLEDGE_NODE-29
[support@yourdomain.com](mailto:support@yourdomain.com)\n* **Subject**: "You are missing messages from <Org Name>"\n\nReply to the customer on a ticket\n---------------------------------\n\n* **Trigger**: When a reply is made to a customer on a ticket.\n* **Action**: The system sends out a notification to the customer with the reply message.\n* **Sender**: {Company\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\n* **Subject**: "[{Company\\_Name}] Update on TKT-XXX"\n\nTicket
Customer email notifications | Computer by DevRev | DevRev
ART-2027_KNOWLEDGE_NODE-39
Notifications**.\n\n* Each notification type\xe2\x80\x94such as being assigned, mentioned, or when a customer esponds\xe2\x80\x94can be toggled for both in-app and email delivery.\n\n### The email composer in Tickets\n\nInside every ticket, under the **Customer Messages** tab, agents can access a fully featured email composer. This allows direct email communication with customers from within DevRev.\n\nHere\xe2\x80\x99s what the email component supports:\n\n| Feature | Icon / Access Point |
Email | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-42
ticket notifications\n\n* Enable through the **Notify on new ticket creation** snap-in configuration.\n* Provide a Slack channel ID in the **Channel ID to send ticket notifications** configuration.\n* Snap-in will send notifications to the target channel whenever a new ticket is created, regardless of the source channel or platform.\n* Notification message threads are **not** synced between platforms.\n\n### Notifications for ticket state update\n\n* Enable through **Notify on ticket state
Slack | Integrate | Snap-ins | DevRev
ART-1976_KNOWLEDGE_NODE-29
section.\n\nNotification behavior\n---------------------\n\n* Group-only routing triggers notifications for all group members.\n* Direct user assignment triggers notifications only for the assigned user.\n* Combined group and user routing triggers notifications only for the assigned user.\n* If a user is assigned as the owner after notifications have been sent to the group members, those notifications are removed for all members and retained only for the assigned owner.\n* When a new owner is
Routing | Computer for Support Teams | DevRev
ART-2912_KNOWLEDGE_NODE-25
DevRev marketplace.\n\nInstallation\n------------\n\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\n2. In the DevRev marketplace, find **Ticket email notifier** and click **Install**.\n3. In DevRev, **Snap-ins** > **Ticket email notifier** > **Configure**.\n4. Select SendGrid connection and **Connect**.\n5. Enter the required parameters like **Subtypes**, **Recipient name**, **Subject**, **Introductory part**, **Table contents**, and
Ticket email notifier | Automate | Snap-ins | DevRev
ART-1954_KNOWLEDGE_NODE-33
notifications for new assignments.\n   * Group Mentions: Enable notifications for mentions involving your affiliated groups.\n   * Mentions: Enable alerts when you're mentioned.\n   * Comments: Enable updates for comments on your subscribed records.\n   * Attribute Updates: Enable notifications for attribute updates in records to which you subscribe.\n3. Select the priority level (*Important*, *Others*, *Muted*) for each notification type. This determines the destination tab on the **Updates**
Updates | Computer by DevRev | DevRev
ART-16583_KNOWLEDGE_NODE-1
whenever a DevRev customer experience engineer responds.\n\nConfiguration\n-------------\n\n##### \n\n**Prerequisites**\n\n* Apple Developer Program access for iOS apps.\n* Google Developer Account and Firebase project access for iOS apps.\n* Admin access to DevRev Plug settings.\n* Access to Bundle ID, Team ID, and APNs/FCM keys.\n* Mobile SDK integration with your Android or iOS app.\n\n1. Go to **Settings** > **Support** > **Plug settings** > **Mobile push notifications**.\n2. Click **+
Push notifications for mobile | DevRev | Docs
ART-12390_KNOWLEDGE_NODE-44
(Optional) Users for private visibility | Output ports created dynamically based on button clicks |\n| SendNotification | Sends a notification to specified users or groups. | * receivers: Users or groups who will receive the notification * body: The body of the notification * title: The title of the notification * linked\\_object: (Optional) The object which will open on clicking the   notification | Empty response on success
Workflow action library | Workflows | Computer by DevRev | DevRev