Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/SendAE/RecommendedEmails.htm

## Recommended Emails

Recommended emails empower business admins to create pre-approved emails for target accounts. Organizations can use recommended emails to share new information, for example recent studies or product updates, with many HCPs at once.

Business admins can tailor the message content to the targeted accounts, and Vault CRM creates scheduled emails or drafts for end users to review, modify, or send to the recipients.

Recommended emails simplify the process for end users, allowing them to quickly and easily send targeted messages to HCPs.

This streamlined approach to email communication enhances efficiency, ensures compliance, and empowers users to deliver timely and impactful messages.

**Who can use this feature?**

* Business Admin Users — Browser
  + [Creating Campaigns](#Creating)
  + [Creating Activities](#Creating2)
  + [Adding Campaign Targets](#Adding)
  + [Testing Recommended Email Campaigns](#Testing)
  + [Viewing Publish History](#Viewing)
  + [Troubleshooting Errors](#Troubles)
  + [Data Loading Campaigns, Targets, and Activities](#DataLoadingCampaignsTargetsandActivities)
* End Users — iPad, iPhone, Windows
  + [Reviewing and Sending Recommended Emails](#Sending)
* Users require an Approved Email license

### Configuring Recommended Emails for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Integration Users](#)

The Approved Email process uses the integration user's credentials to create the emails defined in the Recommended Email campaign and publish them as drafts or scheduled emails.

To configure this feature:

1. Ensure [Configuring Approved Email](../InitialConfig/ConfiguringAE.htm) is complete.
2. Ensure the integration user has the following permissions:
   * Read access to all object types on Territory Fields (tsf\_\_v)
   * Read access to the allowed\_document\_ids\_\_v field on the approved\_document\_\_v object
3. Navigate to **Admin > Users and Groups > Permission Sets**.
   * Select the appropriate permission set
   * Grant users the following permissions:

| Object | Object Permission | Object Types | Fields | Field Permission |
| --- | --- | --- | --- | --- |
| sent\_email\_\_v | CRE | campaign\_\_v | * campaign\_activity\_\_v * campaign\_target\_\_v | Edit |
| campaign\_execution\_id\_\_v | Read |
| campaign\_\_v | CRED | core\_crm\_campaign\_\_v | * name * description\_\_v * external\_id\_\_v * start\_date\_\_v * end\_date\_\_v * product\_\_v * detail\_group\_\_v * status\_\_v * parent\_campaign\_\_v * country\_user\_\_v * objectives\_\_v | Edit |
| campaign\_activity\_\_v | CRE | recommended\_email\_\_v | * name * campaign\_\_v * description\_\_v * external\_id\_\_v * start\_time\_\_v * end\_time\_\_v * scheduled\_send\_datetime\_\_v * publish\_date\_\_v * account\_email\_source\_\_v * vault\_instance\_id\_\_v * email\_template\_vault\_doc\_id\_\_v * email\_fragment\_vault\_doc\_ids\_\_v * email\_template\_\_v * email\_fragments\_\_v   Multi-product Approved Email Content users require Edit field permission to product\_\_v and detail\_group\_\_v. | Edit |
| campaign\_target\_\_v | CRED | n/a | * name * target\_account\_\_v * campaign\_\_v * external\_id\_\_v * target\_owner\_user\_\_v * territory\_\_v | Edit |
| campaign\_activity\_target\_execution\_\_v | CRED | recommended\_email\_publishing\_\_v  Ensure the recommended\_email\_publishing\_\_v object type is Active. | * name * campaign\_activity\_\_v * campaign\_target\_\_v * sent\_email\_\_v * outcome\_\_v * vexternal\_id\_\_v | Edit |
| campaign\_job\_history\_\_v | CRED | recommended\_email\_publishing\_\_v | * name * campaign\_\_v * campaign\_activity\_\_v * external\_id\_\_v * failed\_\_v * successful\_\_v * total\_\_v * job\_type\_\_v * job\_id\_\_v * job\_start\_time\_\_v * job\_end\_time\_\_v | Edit |

1. Grant users **Read** field permission to all fields referenced in tokens within the Approved Email template and fragments, for example, fields on the Account object used to insert the recipient’s name, or on the user object to insert the sender’s name or email address for replies.
2. Navigate to **Admin > Configuration > Objects > sent\_email\_\_v > Fields > sent\_email\_status\_\_v**.
3. Verify the status for the draft\_\_v picklist value is **Active**.

#### Configuring Recommended Emails for Scheduled Emails (Optional)

1. Enable Consent Capture for integration users if your Vault is using consent capture. A permission set is available to provide the end user permissions.
2. Grant Integration users Read permission to the **scheduled\_send\_date\_time\_\_v** field on the campaign\_activity\_\_v object.

### Configuring Recommended Email for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif) Business Admin Users](#)

Business Admins create Recommended Email campaigns and associate them with targets, and the account details and email template needed to create the email messages. They can also preview the email message and view the status of campaign activities.

To configure this feature:

1. Ensure [Configuring Approved Email](../InitialConfig/ConfiguringAE.htm) is complete.
2. Grant users Execute permission to the **Download Log** action on the Campaign Job History object.
3. Navigate to **Admin > Configuration > Objects > Campaign Job History > Object Types > Actions**.
4. Add the **Download Log** action to the appropriate object types.
5. Navigate to **Admin > Users and Groups > Permission Sets**.
   * Select the appropriate permission set
   * Grant users the following permissions:

| Object | Object Permission | Object Types | Fields | Field Permission |
| --- | --- | --- | --- | --- |
| sent\_email\_\_v | R | campaign\_\_v | * campaign\_activity\_\_v * campaign\_target\_\_v | Read |
| campaign\_\_v | CRED | n/a | * name * description\_\_v * external\_id\_\_v * start\_date\_\_v * end\_date\_\_v * product\_\_v * detail\_group\_\_v * status\_\_v * parent\_campaign\_\_v * country\_user\_\_v * objectives\_\_v | Edit |
| campaign\_activity\_\_v | CRED | recommended\_email\_\_v | * name * campaign\_\_v * description\_\_v * external\_id\_\_v * start\_time\_\_v * end\_time\_\_v * scheduled\_send\_datetime\_\_v * publish\_date\_\_v * account\_email\_source\_\_v * vault\_instance\_id\_\_v * email\_template\_vault\_doc\_id\_\_v * email\_fragment\_vault\_doc\_ids\_\_v * email\_template\_\_v * email\_fragments\_\_v   Multi-product Approved Email Content users require Edit field permission to product\_\_v and detail\_group\_\_v. | Edit |
| campaign\_target\_\_v | CRED | n/a | * name * target\_account\_\_v * campaign\_\_v * external\_id\_\_v * target\_owner\_user\_\_v * territory\_\_v | Edit |
| campaign\_activity\_target\_execution\_\_v | R | recommended\_email\_publishing\_\_v | * name * campaign\_activity\_\_v * campaign\_target\_\_v * sent\_email\_\_v * outcome\_\_v * vexternal\_id\_\_v | Read |
| campaign\_job\_history\_\_v | R | recommended\_email\_publishing\_\_v | * name * campaign\_\_v * campaign\_activity\_\_v * failed\_\_v * successful\_\_v * total\_\_v * job\_type\_\_v * job\_id\_\_v * job\_start\_time\_\_v * job\_end\_time\_\_v | Read |

#### Configuring Recommended Emails for Scheduled Emails (Optional)

Grant Business Admin users Edit field permission to the **scheduled\_send\_date\_time\_\_v** field on the campaign\_activity\_\_v object.

### Configuring Recommended Email for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure this feature:

1. Ensure [Configuring Approved Email](../InitialConfig/ConfiguringAE.htm) is complete.
2. Enable the [Email Tab](ApprovedEmailTab.htm) for end users.

### Using Recommended Emails as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

Business admins can take advantage of recommended emails by:

* [Creating Campaigns](#Creating)
* [Creating Activities](#Creating2)
* [Adding Campaign Targets](#Adding)
* [Testing Recommended Email Campaigns](#Testing)
* [Requirements for Successful Email Publishing](#Requirements)
* [Viewing Publish History](#Viewing)
* [Troubleshooting Errors](#Troubles)
* [Data Loading Campaigns, Targets, and Activities](#DataLoadingCampaignsTargetsandActivities)

Recommended emails should only be created for users on the iPad and iPhone platforms as users can only review and send Recommended Emails from the Email Tab on the iPad or iPhone.

#### Creating Campaigns

Campaign admins can use Recommended Emails to select an email to send as part of a campaign. For example, create a single campaign called “New Product Study” to group all recommended product study emails for your targets.

See [Vault CRM Campaigns](../../../Accounts/UsingAccounts/Veeva_CRM_Campaigns.htm) for information on creating a campaign.

#### Creating Activities

To create an activity for a Recommended Email campaign activity:

1. Select **New** from the Campaign Activities related list.
2. Select the **recommended\_email\_\_v** object type.

   ![](../../../../Resources/Images/Multichannel/ApprovedEmail/Sending/CampaignActivityEmail.png)
3. Enter a name for the Campaign Activity, for example, New Product Study.
4. Enter a **Scheduled Send Datetime** that is between the campaign activity start and end date to schedule the message, or leave the field blank to create draft emails.

   Vault CRM schedules the email to be sent at the specified time when the Scheduled Send Datetime field is populated. End users can view, unschedule, or reschedule messages from the Scheduled folder of the [Email Tab](ApprovedEmailTab.htm).
5. Enter a **Publish Date** between the campaign activity start and end date. The [Approved Email Integration Process](../ConfiguringAE/AECRMVaultIntegration.htm#SchedulingtheIntegrationProcess) creates the Sent Email records on this day.

   The Publish Date should be at least one day before the Scheduled Send Datetime value when publishing scheduled recommended emails.

   ![](../../../../Resources/Images/Multichannel/ApprovedEmail/Sending/CampaignActivityEmail2.png)
6. Enter up to five fields from the Account or Address objects in the Email Source field, to use as sources where the process should look for the recipient’s email address. For more than one address, enter a comma-separated list. For example:

   account\_\_v.email\_cda\_\_v,account\_\_v.personal\_email\_\_c,address\_\_v.office\_email\_\_c

   * If a single value is configured on the Campaign Activity, this field's value is used to determine the email source field
   * If a delimited list is populated, each field is checked sequentially, following the order of configuration

     Example value: account\_\_v.email\_cda\_\_v,account\_\_v.personal\_email\_\_c,address\_\_v.office\_email\_\_c

     In this example, the process checks account\_\_v.email\_cda\_\_v and finds no value. The process checks account\_\_v.personal\_email\_\_c and finds 'test@email.com', looks no further, and uses this email address as the recipient of the email. (address\_\_v.office\_email\_\_c is not checked.)
   * If email fields are configured from the address\_\_v object, the process finds the email as follows:
     + Use the Preferred Address from the Target Owner's TSF record
     + Use the Primary Address (if no TSF Preferred Address exists)
     + Use the First Address (if no Primary exists) that has an email value
7. Enter a **Vault Instance ID**. This is the URL of the PromoMats/MedComms instance where the email template and email fragments for the Campaign Activity are stored. For example: https://yourvault.veevavault.com
8. Enter an **Email Template Vault Doc ID** using the template's [Vault Doc ID](https://support.veeva.com/hc/en-us/articles/4405622230427-How-to-Retrieve-the-Document-Related-IDs-in-Veeva-Vault-). This template is used to render the message.

   When an Email Template Vault Doc ID has multiple associated approved\_document\_\_v records, the Campaign Activity Product (product\_\_v) and/or Detail Group (detail\_group\_\_v) fields are used to determine and return the appropriate Approved Document.

   * When product\_\_v is populated and detail\_group\_\_v is empty, the rendered record is an exact match on the Approved Document's product\_\_v field. The detail\_group\_\_v field on the Approved Document must also be empty.
   * When both fields are populated on the Campaign Activity, the rendered record is an exact match on the product\_\_v and detail\_group\_\_v fields

   For information on creating Approved Email templates and fragments, see [Creating Approved Email Templates](../CreatingContent/CreatingAETemplates.htm).

   Only templates with the email\_template\_\_v object type are supported.

   It is not recommended to configure Scheduled Recommended Emails with an email template that has [User Input Tokens](../CreatingContent/ConfigTokens.htm#UserInputTokens). Those are not resolved automatically and require end-user input.

   The {{insertEmailFragments[Minimum,Maximum]}} token is not supported
9. Enter any fragments to include in the message, in the Fragment IDs field. For more than one ID, enter a comma-separated list. For example: 5,29,92839
10. Save the **Campaign Activity**.
11. Preview the message to ensure everything looks as expected. If errors display, review the [Requirements for Successful Email Publishing](#Requirements).

    The email template preview may render differently from the sent email. We recommend using the email [test process](#Testing) to view the final format of the email.

#### Adding Campaign Targets

Campaign admins can add targets using the following methods:

* One at a time through the CRM interface
* Multiple at a time using Vault Loader

For each target, specify the Account (email recipient) and Target Owner User (email sender).

#### Testing Recommended Email Campaigns

After creating a Recommended Email campaign, admins can test the campaign using a test email address. Emails are sent to the test address instead of the HCP email addresses.

The Email Template specified in the Activity must have a status of Approved in order for the test to work.

To test a Recommended Email campaign, populate the Vault-wide or integration security profile’s approved\_email\_test\_address\_\_v Approved Email setting with a test email address, for example test@verteo.com. When the Vault Process Scheduler runs the Approved Email Process, the test address is used in place of all target account email addresses. The process creates draft or scheduled emails that a test user (target owner) can view on their iPad, and either reschedule them or send them to the test email address.

The integration user's Approved Email Admin setting is not taken into consideration for Recommended Email campaigns.

For more information, see [Testing Staged Approved Email Content](../ManagingContent/TestingAEContent.htm).

#### Requirements for Successful Email Publishing

* Campaign must have a status of Active
* Campaign Activity must be of type recommended\_email\_\_v
* Campaign Target (Account) must have a Campaign Target Owner (User) assigned
* Campaign Target (Account) and Campaign Target Owner (User) must have a matching Territory
* Campaign Target Owner (User) must have access to the Product and Detail Group (if applicable) the Approved Email template is linked to (via MySetup)
* Email Template and Fragments must exist in CRM and must be in Approved status
* Campaign Target (Account) must be a person account
* Campaign Target (Account) must have an email address
* Consent is valid for the Campaign Target (Account) and the Email Template
* Email Template product cannot be listed as restricted for the Campaign Target Account
* If Allowed Products verification is enabled, the Email Template and Email Fragment product(s) are listed as allowed products on the Campaign Target's (Account) TSF record

#### Viewing Publish History

Admins can view the Publishing History from the Approved Email Admin tab and the Campaign Activity record. The Publishing History shows the status of the process and the number of processed campaign activities. Admins can select the number of processed campaign activities to download a CSV file with details for each processed activity.

Campaign Activity Target Executions allow campaign admins to see a detailed overview of the publishing outcome. A record is created for each Campaign Target picked up during email publishing and contains a history record for the Sent Email created.

#### Troubleshooting Errors

Errors that can occur during the publish process are displayed in the logs. Campaign Job Histories store a summary of a recommended email publishing run. The related list can be added to either the Campaign or Campaign Activity layouts.

To access a log, select a Campaign Job History record from the related list and select the Download Log action.

For example, if a recommended email is created from a Campaign Activity that includes a template that is no longer valid, an error displays in the log. The recommended email cannot be published until the error is resolved.

After any errors are resolved, the next scheduled Integration Process will try publishing the recommended email.

Errors must be resolved within the same day for successful email publishing. The Integration Process only retries the publishing of recommended emails that have a Publish Date of the current day.

#### Data Loading Campaigns, Targets, and Activities

Admins can data load campaigns, campaign targets, and campaign activities ready to be published. To data load recommended email campaign information, follow the sequence below and map the fields.

* campaign\_\_v
  + name\_\_v
  + start\_date\_\_v
  + end\_date\_\_v
  + product\_\_v
  + status\_\_v
  + detail\_group\_\_v (optional)
  + parent\_campaign\_\_v (optional)
  + objectives\_\_v (optional)
  + description\_\_v (optional)
  + country\_user\_\_v (optional)
* campaign\_activity\_\_v
  + name\_\_v
  + campaign\_\_v
  + publish\_date\_\_v
  + account\_email\_source\_\_v
  + vault\_dns\_\_v
  + email\_template\_id\_\_v
  + email\_fragment\_ids\_\_v
  + scheduled\_send\_datetime\_\_v (optional)
  + description\_\_v (optional)
* campaign\_target\_\_v
  + campaign\_\_v
  + target\_account\_\_v
  + target\_owner\_user\_\_v
  + territory\_\_v
  + external\_id\_\_v

The data loading process validates the following details. The record is not saved if validation errors occur.

* Schedule Send Datetime, if populated, must be greater or equal to the parent campaign's Start Date and lower or equal to the parent campaign's End Date
* Schedule Send Datetime, if populated, must have a Publish Date at least 1 day earlier than the date of the Scheduled Send Datetime
* The Publish Date cannot be later than the campaign's End Date
* The account\_email\_source\_\_v field is limited to no more than 5 fields

### Using Recommended Emails as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

#### Reviewing and Sending Recommended Emails

End users can access recommended emails from the [Email Tab](ApprovedEmailTab.htm). A Recommended label displays in the List View and Preview View to indicate a message was created by a Recommended Email campaign.

After reviewing recommended emails, users can send, [discard](ApprovedEmailTab.htm#DiscardDrafts), or [reschedule](UnschedulingEmails.htm) the emails created for the campaign.

When an organization creates a recommended email, that email displays on the Email Tab as a draft or scheduled email in the list of email messages for each campaign target. Draft emails remain in the Drafts tab until the user decides to send, schedule, or delete them; they are not automatically deleted when the campaign ends.

![](../../../../Resources/Images/Multichannel/ApprovedEmail/AdvanceFunct/RecommendedEmails/RecEmailIndicatorUVCAfter.png)

### Related Topics

[Composing Approved Emails](ComposingAEs.htm)

[Email Tab](ApprovedEmailTab.htm)

[Recommended Email Flightpath](https://vaultcrmflightpath.veeva.com/doc/Content/ApprovedEmail/RecommendedEmail/1-Intro.htm)