tickets created through plug customer workspace assignment customer account set
ART-2002_KNOWLEDGE_NODE-32
get resolved and matched when the same customer engages with you on the Plug widget for a support interaction.\n\nThis is achieved by using the *external reference* provided by you when creating customer identity.\n\n**External reference for a customer**\nA unique identifier for an end user from your primary customer record. The system uses this to resolve a newly created customer with customers already in the system.  \nIf none is available, a good alternative is the email address or phone
Contacts | Computer for Growth Teams | DevRev
ART-2000_KNOWLEDGE_NODE-31
domain. If none is specified, a system-generated identifier is assigned to the account.\n\n![]()\n\nFor ingestion channels where providing an external reference isn't possible, the system relies on custom logic to identify and match incoming customer identity.\n\n> Example: The Slack and Email integration uses a combination of the customer email and workspace domain\\_name values. WhatsApp uses the WhatsApp number and associated name.\n\nAdd a workspace\n---------------\n\nTo add a workspace to
Accounts | Computer for Growth Teams | DevRev
ART-1976_KNOWLEDGE_NODE-28
scenarios\n----------------------------\n\n* Ticket routing based on customer inquiry keywords.\n* Group-specific routing based on customer account assignments.\n* Assignment routing based on severity and subtype.\n* Custom field and tag-based routing.\n* First responder ticket assignment.\n\nSystem requirements\n-------------------\n\n* Administrator privileges are required for workflow deployment and execution.\n* User status (active/away) is configurable through the profile
Routing | Computer for Support Teams | 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-16264_KNOWLEDGE_NODE-29
account.\n  + If both **Reported By** and **Account** fields are initially empty, you can search for and add any contact to the **Reported By** field, which will auto-fill the **Account** and **Workspace** (if applicable).\n* **Handling multiple users:**\n\n  + If all selected users within the **Reported By** field belong to the same workspace, the **Workspace** field remains unchanged.\n  + If users are from different workspaces, the **Workspace** field is emptied, while the **Account** field
June 2025 | Changelog | 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-15506_KNOWLEDGE_NODE-19
\xe2\x9c\x85 | If neither exists: System creates the account first, then creates the workspace. User is linked to both. If account exists but workspace doesn\xe2\x80\x99t: System creates the workspace under the existing account. User is linked to both. If workspace exists under different account: System returns an error, as workspaces cannot be a part of 2 accounts. |\n| \xe2\x9c\x85 | \xe2\x9d\x8c | If workspace doesn\xe2\x80\x99t exist: System creates a new account and workspace (if needed).
Identify your users with Plug | DevRev | Docs
ART-15506_KNOWLEDGE_NODE-18
doesn\xe2\x80\x99t exist, the system automatically creates the user.\n\nThis approach ensures efficient management and integration of objects within the DevOrg.\n\n| Workspace Ref | Account Ref | Results |\n| --- | --- | --- |\n| \xe2\x9d\x8c | \xe2\x9c\x85 | (Most common Usage) \\nIf the account doesn\xe2\x80\x99t exist: An account is created, and the user is linked with the account. |\n| \xe2\x9d\x8c | \xe2\x9d\x8c | No action on account or workspace. The user is returned. |\n| \xe2\x9c\x85 |
Identify your users with Plug | DevRev | Docs
ART-2895_KNOWLEDGE_NODE-10
The mobile number of the customer.| array  \n  \n**Attributes for workspaces**\n\nAttributes| Description| Type  \n---|---|---  \n`workspace_ref`| A unique reference for the user\xe2\x80\x99s workspace. If not provided, and an account reference is passed, the user is directly attached to the account.| string  \n`display_name`| The name of the workspace that\xe2\x80\x99s shown on the widget.| string  \n  \n**Attributes for accounts**\n\nAttributes| Description| Type  \n---|---|---
Identify your users with PLuG — DevRev | Docs
ART-3235_KNOWLEDGE_NODE-24
[Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Reported by enricher](/docs/automations/ticket-reported-by)\n\nReported by enricher\n====================\n\nThe [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) snap-in automatically updates the **Reported By** field on tickets created with an email entered in a custom field. It verifies if the email belongs to an existing customer of the configured account and either links to that customer or creates a new
Reported by enricher | Automate | Snap-ins | DevRev