Create unverified accounts from Vault CRM

When users submit an add request, the record can be immediately created as an unverified account in Vault CRM so users can quickly interact with and update the account while the DCR is sent to Network for processing.

Administrators must configure Vault CRM and Network to support unverified records.

Requirements

Settings must be enabled in Vault CRM and in Network to create unverified accounts.

Vault CRM setting

The following setting must be configured:

  • Data Change Request Mode custom setting must be set to 2.

Network setting

  • Enable the Create Unverified setting (Settings > Workflow Settings).

About the process

When the settings are configured, an add account request can immediately create records, including an unverified VID. The record is set to under_review__v state. When the record has been processed and approved in Network, the record state is updated.

This setting must be enabled for users to make changes to unverified records; otherwise, change requests are automatically rejected.

Supported objects

Unverified records can be created for all Vault CRM accounts:

  • HCPs

  • HCOs

  • Addresses

  • Child Accounts

Match and merge considerations

An unverified account can match to an existing account in Network and result in a merge (add request becomes a change request ).

  • If the winning account does not exist in Vault CRM, the losing account ID is updated to the winning account ID.

  • If the winning account is in Vault CRM, the losing account will be merged to the winner in Vault.

Rejected add requests

If the add request is rejected, the unverified account is deactivated and removed from the territory in Vault CRM.