On this page


Your customers and their identity are a crucial part of the DevRev offering and ecosystem. Conversations on DevRev rely on rev identity to capture information about the customer initiating the conversation. Similarly, tickets on DevRev can capture who the ticket was reported by (or reported for).


Customer identity in DevRev includes the following important constructs:

  • External User/contact: Your end user or customer or users associated with organization Accounts or Workspaces.

  • Account/workspace: Any logical grouping that an external user is part of. It could represent a customer account for your B2B product (for example Stripe as a customer of Slack) or a workspace in your software product (such as a Slack workspace).

Add new customers

To create a new customer record:

  1. Go to Customers > + Account.
  2. Fill in the following fields as Add Display Name, Description, Domains, Tags, Tiers.
  3. Click Create.

While creating new customer records, be sure to specify the External Reference so customer information coming from other channels (like PLuG, email, and WhatsApp) can be matched to the right customer record.

Creating a new customer

Bulk import customer records

To bulk import a customer record from platforms such as Zendesk, Salesforce, Jira, and Linear:

  1. Go to Customers > Upload CSV.

  2. Select the accounts or users you want to import in the Import contacts dialog and click Upload CSV file.

  3. Select the CSV file from your device. If the file contains any unsupported field name then it's reflected in the Import contacts dialog. If you go forward with this file unedited, only the fields that are in the schema are uploaded. To verify the required fields, you can download a sample CSV file by clicking Download Sample CSV.


  4. Click Import. A successful import message is displayed if the file is valid.

    If validation errors are found in a row entry, then that row isn't ingested. An error notification is shown in the bottom left corner providing information about the number of successful imports and the number of errors found.

    By clicking Learn More in this notification, a sidebar opens listing all rows along with their errors.

  5. Newly created accounts/users are reflected in the customer list. If not, refresh the website for the new accounts/users to be visible.

If any one of the values isn't in accordance with the field requirement, then the account/user against that row entry isn't created. Some of the fields are mandatory for validating the file. To understand which fields are required, refer to the downloaded sample CSV. Mandatory fields have mandatory in their sample row entry.

Customer records offer a place to do the following:

  • Find all conversations and tickets linked to a customer in one view.
  • Have internal discussions related to a customer.
  • Add description or notes about a customer.
  • Assign an owner or tags to the customer.

Customer view

Apart from customer records that get automatically created from your PLuG integration, new customer records can be created through the app.

External reference

While ingesting customer identity into DevRev, customer information coming across channels must be matched to the same record.
For example, a customer record created by you using APIs should get resolved and matched when the same customer engages with you on the PLuG widget for a support interaction.

This is achieved by using the external reference provided by you when creating customer identity.

External reference for a customer user_ref
A 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.
If none is available, a good alternative is the email address or phone number that could uniquely identify the user.
If none is specified, a system-generated identifier is assigned to the user.

External reference for a workspace org_ref
A unique identifier for the customer organization from your primary customer record. If none is available, a good alternative is the customer’s company domain. If none is specified, a system-generated identifier is assigned to the organization.


For ingestion channels where providing an external reference isn't possible, the system relies on custom logic to identify and match incoming customer identity.

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.

Identity ingestion

The identity of your customers can be brought to the DevRev system in multiple ways.

Your PLuG integration automatically brings customer identity to DevRev with each widget conversation.

Workspace and external user information provided as part of the PLuG integration identifies or creates corresponding customer identity in the DevRev system and links it to PLuG conversations.

DevRev's integrations like Slack, Email for conversations, WhatsApp are additional channels available with DevRev's Omnichannel Support offering. Integrating these channels automatically brings customer identity to DevRev.

APIs or UI
Apart from automatic ingestion, new customer records can also be created manually using APIs or UI. With DevRev's APIs, you can create automations to ensure your customer records in DevRev stay in sync with your primary customer data.