configure support email to create tickets automatically
ART-3207_KNOWLEDGE_NODE-39
here are treated as new support tickets.\n* **Conversations**: These addresses trigger conversations (not tickets).\n\n> Example: Use sales@yourcompany.com for general inquiries and help@yourcompany.com for support.\n\n### Step 4: Set the Default Part and Owner\n\n* Select the **default part** of your product for categorizing tickets.\n* Assign a **default owner** (for example, a support lead or queue manager) for incoming tickets.\n\n### Step 5: Personalization settings\n\n| Setting |
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-38
Step 2: Define the Primary Use Case\n\nChoose how DevRev should interpret emails sent to the primary address:\n\n* Choose between generating a **Ticket or a Conversation** from the incoming email.\n\nToggle on **Set email as the default channel for tickets** to ensure that:\n\n* Customer chat replies are sent via email as well as to the original source of the channel.\n\n### Step 3: Add Additional Support Emails\n\nYou can add more addresses to handle support requests.\n\n* **Tickets**: Emails
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-26
configuration instructions, refer to [Email snap-in configuration](/docs/integrations/email-config).\n\nFor more information, refer to the [Email snap-in](/marketplace/email-with-tickets) on the DevRev marketplace.\n\nConversation and ticket creation for emails\n-------------------------------------------\n\nWhen an email is received, DevRev checks if the sender is linked to your workspace and creates a conversation or ticket. If a sender is not recognized, DevRev creates a new user profile to
Email | Integrate | Snap-ins | 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
ART-3207_KNOWLEDGE_NODE-37
href="mailto:support@devrev.ai">support@devrev.ai</a>\n\n\n\n18     </td>\n\n\n\n19   </tr>\n\n\n\n20 </table>\n```\n\nShow more\n```\n\n**Result**:\n\n![]()\n\n### Next steps for configuration of the snap-in\n\n### Step 1: Add a Primary Email Address\n\n* Format: Name <email@domain.com> \xe2\x80\x94 this is what appears in the customer\xe2\x80\x99s inbox.\n* Example: Maple Support <support@maplesoftware.net>\n\nThis email address becomes the primary channel for incoming support mail.\n\n###
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-47
**Primary Use Case** is **Tickets**, go to **Support** > **Tickets** in the DevRev app; otherwise, if the **Primary Use Case** is **Conversation** go to **Inbox**. Find and open your verification message here.\n6. Open the given link to confirm the request. Make sure you click the link that allows your support address to be forwarded to v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai.\n7. Go back to your Gmail forwarding settings, select **Forward a copy of incoming mail** and **Save
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-34
Configure email integration snap-in\n--------------------------------------\n\n1. Go to **Settings** > **Snap-ins**. In the top-right corner, click **Explore Marketplace**.\n2. Scroll down the page to find the **Email Integration** snap-in and click **Install**.\n3. In the **Connections** tab, select the connection that you created. You could [create a new connection](#1-create-a-new-connection) here as well.\n4. Select the options and inputs suitable for your organization in the
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-45
snap-in. These only appear once the email snap-in is successfully installed and verified.\n\nSet-up the provided forwarding address to the account you want to forward from. For example support@example.com.\n\nIn the DevRev app, under the **Instructions** tab you can see a forwarding email address displayed as v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai. This is the address where you can forward your support emails.\n\nGoogle Workspace/Groups\n\n1. If you are using Google Groups, add your
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-46
support address as a member of the Google Group.\n\n   You must be a part of the group and have permission to send emails to the Google Group.\n2. Go to the settings of your support Gmail account.\n3. Navigate to **Forwarding and POP/IMAP** and add the forwarding email address v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai. Click **Next**.\n4. Click **Proceed** when you are redirected to a new webpage. You are asked for a confirmation code sent to this forwarding address.\n5. If the
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-49
select **Forward all emails sent to this mailbox**, enter the forwarding address v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai, and choose whether you want to keep a copy of forwarded emails. If you don\'t see this option, make sure a license is assigned to the user account. Select **Save changes**.\n\nOnce added, an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-15716_KNOWLEDGE_NODE-3
SMTP/IMAP). You\xe2\x80\x99ll need admin access to complete the setup.\n\n[Email integration setup instructions](https://devrev.ai/docs/integrations/email)\n\n6. Syncing Cases Between DevRev and Salesforce\n\nYes, you can sync cases (tickets) from DevRev to Salesforce using the Salesforce integration. Mapping and sync options are available during setup.\n\n[Syncing cases with Salesforce](https://devrev.ai/docs/integrations/salesforce#sync-cases)\n\n7. Supported Airdrop Sources\n\nDevRev Airdrop
Support queries related playbook
ART-1478_KNOWLEDGE_NODE-46
event source is deployed, the instructions show a unique email address. You have to set up forwarding in your original email inbox or Google Group to this email address. In the example above, if the forwarding address is `v1.abc.xyz@hooks.devrev.ai`, you should set up email forwarding from `test@company.com` to `v1.abc.xyz@hooks.devrev.ai`.\n\n#####\n\nOnly emails forwarded from the allowlist of emails/domains are emitted as events. Hence, this event source should be used for email forwarding
Event sources — DevRev | Docs