send email to customers directly without customer initiated conversation
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-4020_KNOWLEDGE_NODE-24
[Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Send customized emails](/docs/automations/send-emails)\n\nSend customized emails\n======================\n\nThe [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) snap-in automates email sending. Once activated, this operation becomes available in the Workflow builder, enabling the delivery of personalized messages.\n\nConfiguration\n-------------\n\n1. Create a **SendGrid**
Send customized emails | Automate | Snap-ins | DevRev
ART-4020_KNOWLEDGE_NODE-25
account.\n2. Generate an **API key**.\n3. Create a SendGrid connection:\n   a. Go to **Settings** > **Snap-ins** > **+ Connection**\n   b. Select **SendGrid**.\n   c. Add the **API key** and click **Save**.\n\nInstallation\n------------\n\n1. Install the [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) from the DevRev marketplace.\n2. Open the Workflow Builder and locate the **send customized emails** action node.\n3. Configure the node by selecting the
Send customized emails | Automate | Snap-ins | DevRev
ART-1627_KNOWLEDGE_NODE-1
---|---  \n    >|      -H "Authorization: Bearer <token>" \\  \n    >|      -H "Content-Type: application/json" \\  \n    >|      -d \'{  \n    >|   "email": {  \n    >|     "body": "body",  \n    >|     "recipients": [  \n    >|       "recipients",  \n    >|       "recipients"  \n    >|     ],  \n    >|     "sender": "sender",  \n    >|     "subject": "subject"  \n    >|   }  \n    >| }\'\n[/code]  \n  \nTry it\n\n200Successful\n\n[code]\n\n    1| {}  \n    ---|---\n[/code]  \n  \n[Submit
Send Surveys (Beta) — DevRev | Docs
ART-4020_KNOWLEDGE_NODE-26
SendGrid connection and providing inputs such as:\n\n   * **Sender email**\n   * **Recipient emails**\n   * **Email body or email template name (use only one)**\n   * **Fields to replace in the email template** for dynamic content substitution\n\n   ![]()\n\n   Use either the email body or the email template name, but not both. The email template name must match a template created in SendGrid. The **Fields to replace in the email template** allows dynamic value substitution. For example, if the
Send customized emails | Automate | Snap-ins | DevRev
ART-1974_KNOWLEDGE_NODE-24
Teams](/docs/product/support)\n[Conversations](/docs/product/conversation)\n\nConversations\n=============\n\nA conversation is an object type that's used to track any synchronous or near-synchronous discussions. A conversation maybe started by a customer, a builder, or a system (auto-created).\n\nA new conversation is routed to the customer org's default owner unless it matches keywords in the support routing snap-in configuration.\n\nConversations from new or unidentified customer orgs have
Conversations | Computer for Support Teams | DevRev
ART-3207_KNOWLEDGE_NODE-44
sharing settings:\n\n* **Signature**: Added to all personal emails sent via DevRev\n* **Share files as links**: Ensures deliverability of attachments via secure links\n\n3. Configure email forwarding for your email provider\n-----------------------------------------------------\n\nFor conversation or tickets to be created in DevRev, the emails must be forwarded from your email provider. The forwarding instructions are available **under the Installation section** of the Email Integration
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev