On this page

Account

An account represents a customer organization, and it holds information about the company, including its name, address, industry, domain, and website address.

Accounts are associated with a workspace. An account can be a part of multiple workspaces at the same time. An account can also be linked to multiple opportunities. Accounts help you keep track of your customer contacts. Contacts are always linked to a workspace or an account.

Create an account

You can create accounts in the following ways:

Using the DevRev app

  1. Go to Accounts > + Account.
  2. Fill in the details like account name, description, websites, domains, type, annual revenue, forecast category, tags, tier, etc.
  3. Fill in the required fields like external references and owner of the account.
  4. Click Create.

Bulk import accounts

To bulk import an account from platforms such as Zendesk, Salesforce, Jira, and Linear:

  1. Go to Accounts > Actions > Upload CSV.

  2. In the Import Accounts dialog, 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 Accounts 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.

    Accounts

  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 are reflected in the accounts list. If not, refresh the website for the new accounts to be visible.

If any one of the values isn't in accordance with the field requirement, then the account 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.

You can also use AirDrop to migrate your accounts from various platforms such as Hubspot, Salesforce, Zendesk, Jira, Linear, ServiceNow and more.

Using DevRev APIs

You can create an account using the accounts.create API. Follow the Create accounts and contacts in DevRev tutorial.

Account attributes

Accounts have attributes that can be used to filter them. You can find all the stock attributes listed in Settings > Object customization > Account > Stock fields. These are the stock attributes that come with DevRev:

  • Domains: Domain names associated with the company to help map contacts to accounts when a contact isn't already linked. Use the format: '[subdomain].domain.com'
  • External references: Identifier for this company from your primary customer record, for example, company domain or account ID. This is used to match customer identity across channels to one record.
  • Created by: The user who created the account.
  • Created date: The date the account was created.
  • Modified by: The user who last modified the account.
  • Modified date: The date the account was last modified.
  • Owners: The users who are responsible for the account.
  • Tags: Tags are used to categorize accounts.
  • Tier: You can add Tier 1, Tier 2, and Tier 3 to classify accounts.
  • Subscribers: Dev users who are notified of changes to the account.

External reference

While ingesting accounts into DevRev, account information coming across channels must be matched to the same record.
For example, an account created by you using APIs should get resolved and matched when a customer contact is created under the account and it should not create a duplicate account.

This is achieved by using the external reference provided by you when creating an account.

External reference for an account A unique identifier for the account 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 account.

icon

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.