how to find my tickets in DevRev
ART-1979_KNOWLEDGE_NODE-27
also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\n\nViews of tickets can be found under **Support** in the DevRev app.\n\n![]()\n\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\n\nAttributes\n----------\n\nTickets have attributes that can be used to filter
Tickets | Computer for Support Teams | DevRev
ART-1979_KNOWLEDGE_NODE-37
filters and **Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\n\nYou can add custom attributes to tickets to track additional information. For more information on custom attributes, see [object customization](./object-customization).\n\nIssues are attached to tickets in order to track efforts with product priorities.\n\nCreate a ticket\n---------------\n\n1. Go to **Support** > **Tickets** from the sidebar on the left.\n2. Click **New Ticket** on
Tickets | Computer for Support Teams | 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-1954_KNOWLEDGE_NODE-25
DevRev](/docs/intro)\n[Updates](/docs/product/updates)\n\nUpdates\n=======\n\nUpdates help you stay on top of all your activity on DevRev.\n\nConversations, tickets, and issues where you are an owner, member, or creator, or where comments are made or you are @mentioned, are automatically shown in your updates. A group can also be mentioned here which will send a notification to all the members of the group. For other tickets and issues, you can follow them to receive some or all updates through
Updates | Computer by DevRev | DevRev
ART-1978_KNOWLEDGE_NODE-32
on the following URL: support.devrev.ai/<yourcompany>.\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\n\n![]()\n\n### Customer roles and permissions\n\nThe customer portal has two levels of customer roles and permissions:\n\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\n* **Customer admins**: Customers who can log in on the portal and see not just their own
Customer portal | Computer for Support Teams | DevRev
ART-4271_KNOWLEDGE_NODE-28
PLuG widget:\n\n  * The ticket number and basic details appear in the same conversation pane.\n  * Users can click **Details** to view complete ticket information.\n  * If the **Tickets** tab is enabled in PLuG, users can track their ticket status there.\n\n### Slack experience\n\nWhen a conversation is converted to a ticket in Slack:\n\n  * Ticket information is sent within the same thread.\n  * All subsequent messages sync with the newly created ticket.\n  * The transition is seamless for the
Convert Conversations to Tickets | Conversations | Support | DevRev