Restricting Calls by Account Object Type
Customers can restrict their users from making calls against certain types of accounts. This helps ensure users comply with organization policies or local regulations concerning interactions with HCPs. For example, an organization has two sets of users based on profile: one set of users can only call on individual HCPs, while another set of users can only call on pharmacies. Calls are restricted by account object types for each set of users. If a user tries to record a call via the account profile page for a restricted account, an error message displays.
Who can use this feature?
- Browser, iPad, iPhone Users
- Users do not require an additional license
- End Users
Configuring Call Restrictions by Account Object Type for
End Users
To configure this feature:
- Ensure Configuring Call Reporting is complete.
- Navigate to Business Admin > Objects > veeva_settings__v.
- Enter a double semicolon delimited list of the restricted account object type field names in the allowed_call_record_types__v Veeva Setting. Text should be formatted as follows:
<account_object_type1>,<call_object_type1>,<call_object_type2>;;
For example, the following text restricts users so they can only make calls of type meeting_brief__v or event__v against accounts of type hospital__v:
hospital__v,meeting_brief__v,event__v;;
Increasing Text Length
To configure an allowed object types list greater than 255 characters:
- Navigate to Business Admin > Objects > veeva_settings__v.
- Populate the allowed_call_record_types__v Veeva Setting with ALLOWED_CALL_RECORD_TYPES;;Common.
- Navigate to Business Admin > Objects > message__v.
- Populate the text field on the ALLOWED_CALL_RECORD_TYPES Veeva Message with the list of allowed object types, following the <account_object_type1>,<call_object_type1>,<call_object_type2>;; format. Use best practices for cloning and editing Veeva Messages.
Disabling Calls for an Account Type
If there is only one account object type listed (with no call object types after it), all call report entry points throughout the system are disabled for this account type. When call object types are not listed, this indicates calls are not supported for the account object type.
For example, the following text restricts any calls from being made against accounts of type professional__v:
professional__v
Restricting Calls Against Multiple Account Types
To restrict users from making calls against multiple account types, list the account object types with a double semicolon delimiter between each object type.
For example, the following text restricts any calls from being made against accounts of type professional__v, personaccount__v, and hospital__v:
professional__v;;personaccount__v;;hospital__v;;
Using Call Restrictions by Account Object Type as
End Users
If users attempt to create a call report for a restricted account type, an error message displays and they are prevented from creating the call report. Call restrictions only apply to the primary account on the call.
Group call attendees and Swapping the Signee functionality are not restricted. For example, even if accounts of type Professional are restricted using this feature, users can still add attendees of type Professional to a group call (which results in individual calls being created against the attendees). Swap Signee is similarly unrestricted, because the restrictions only apply at the initial entry point of the primary account on the call.
If an API is used for creating call records, there are no restrictions. The API operates like a data load where records are not checked against restrictions on accounts (Do Not Call, Object Type restrictions, etc.).
