send ticket to a contact not configured
ART-3207_KNOWLEDGE_NODE-55
test email to your configured address from the deliverability tool and confirm that a conversation or ticket is created.\n2. Respond from the test conversation or ticket in DevRev to the address mentioned in the deliverability check tool.\n\nYou need to add the address as a contact, which can be done in the email composer page.\n\n1. Check the status of the email sent by coming back to the chosen tool.\n\nIf the **DMARC Compliance checks** on the tool pass, then DevRev email is
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-1979_KNOWLEDGE_NODE-36
contact](https://docs.devrev.ai/product/plug) must be created first for any emails to be added as subscribers.\n* **Needs response**: Set to true whenever a new customer message is received on the ticket to ensure that no customer messages are missed. If a particular customer message does not need a response, the **Needs response** toggle can be turned off by the user. Turning off the **Needs response** toggle does not affect the SLA metrics.\n\nThese attributes can be effectively used in
Tickets | 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-3235_KNOWLEDGE_NODE-25
one.\n\nInstallation\n------------\n\nInstall the [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) from DevRev marketplace.\n\nConfiguration\n-------------\n\nIn the **Configuration** tab, the following settings are available:\n\n* **Custom Email Field**: Specify the backend name of the custom field where the email is entered when creating a ticket.\n* **Default Account**: Select the account to which new customers should be linked if they do not already exist in the
Reported by enricher | Automate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-29
your communication requirements.\n\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\n\nEnd users\n\n* Original sender\n\n  *Added to:* **Reported by** or **Email members** field.\n\n  *Is able to:* View the ticket on the portal and reply via email.\n* An end user in the same organization\n\n  *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,
Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-31
to the ticket via email. They cannot view the ticket on the portal, as they are added to the **Email members** field but not to the **Reported by** field.\n\nEmployees\n\n* With DevRev account (added to email thread)\n\n  *Added to:* **To**, **CC**, or **Email members** field.\n\n  *Is able to:* View the ticket on DevRev, reply via email, and receive in-app notifications. If they make changes to ticket attributes, they remain subscribers.\n* Manually added subscribers\n\n  *Added to:*
Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-30
or @mentioned in the DevRev app.\n\n  *Is able to:* View the ticket on the portal and reply via email as an email member.\n* A customer admin for the same workspace\n\n  *Added to:* **Customer Admins** group.\n\n  *Is able to:* View the ticket on the portal once their workspace is updated on the ticket.\n* An end user outside original sender's organization\n\n  *Added to:* **To** or **CC** fields in the email thread, or mentioned in the DevRev app (adds them to **CC**).\n\n  *Is able to:* Reply
Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-32
**Subscribers** field.\n\n  *Is able to:* View the ticket on DevRev and receive in-app notifications.\n* Without DevRev account\n\n  *Added to:* **Email members** field as subscriber.\n\n  *Is able to:* Reply to the ticket via email.\n\nEmail deliverability status\n\nThe sender of an email is able to view the status of an email. Additionally, the sender can view if their email has bounced, along with details about the bounce event.\n\nBelow are the various possible states of an email.\n\n* *In
Email | Integrate | Snap-ins | DevRev
ART-2039_KNOWLEDGE_NODE-25
create DevRev tickets from Marker.io issues, you can configure the\nsnap-in to use this email to auto-fill the **Reported By** and **Customer\nWorkspace** fields in tickets. If no contact or accounts match the email, they\nare automatically created.\n\nInstalling the Marker.io integration snap-in\n--------------------------------------------\n\n1. Install the [Marker.io](/marketplace/marker-io) from the\n   DevRev Marketplace.\n2. Configure the snap-in as needed.\n\n   * (Optional) Select the
Marker.io | Integrate | Snap-ins | DevRev
ART-1978_KNOWLEDGE_NODE-33
tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\n\nOnly verified users can login into the portal.\n\nTo create a verified user:\n\n1. Go to **Accounts** in the DevRev app and create an account.\n2. Create a contact under **Contacts** and link it to the account.\n\n### Set up customer admins\n\nTo set up customer admins, follow these steps:\n\n1. Log in on your DevRev app with your
Customer portal | Computer for Support Teams | DevRev
ART-1979_KNOWLEDGE_NODE-35
docs](https://docs.devrev.ai/import).\n* **Close date**: The date the ticket was closed.\n* **Source channel**: The channel through which the ticket was created. Customers can create tickets via email, the portal, and various other channels.\n* **Channel**: Indicates the medium used for customer communication.\n* **Subscribers**: Indicates the group of users who will receive updates about the tickets.External contacts cannot be added as subscribers, so a [DevRev
Tickets | Computer for Support Teams | DevRev
ART-1979_KNOWLEDGE_NODE-33
members** does not remove them from the **Reported by** field.\n\nShadow users can also be subscribers and email members.\n\n* **CCed members in email**: The CCed members in emails will be added to reporters if they are contacts in the workspace to which the ticket belongs. They will be added to email members if they are part of the ongoing email thread, without any workspace restriction.\n* **Shadow users**: Users created for tracking and record-keeping purposes that do not have access to the
Tickets | Computer for Support Teams | DevRev
ART-2002_KNOWLEDGE_NODE-26
(for example Stripe as a customer of Slack) or a workspace in your software product (such as a Slack workspace).\n\nCreate a new customer contact\n-----------------------------\n\n1. Go to **Contacts** > **+ Contact**.\n2. Fill in the following fields as **Add Display Name, Description, Domains, Tags, Tiers**.\n3. Click **Create**.\n\nWhile creating new customer records, be sure to specify the [**External Reference**](#external-reference) so customer information coming from other channels (like
Contacts | Computer for Growth Teams | DevRev