Approved Email Overview

Approved Email is a powerful feature that streamlines the creation and delivery of compliant emails within Vault CRM. Users can send Approved Emails from various entry points within Vault CRM, use BCC for privacy and data security, and integrate Key Messages to ensure alignment with overarching communication strategies.

Users require an Approved Email license

Approved Email leverages pre-approved HTML content ensuring brand consistency and compliance while providing flexibility for end-users to personalize emails with recipient-specific information. At the same time, Approved Email captures key metrics, for example, open rates, click-through rates, and content views to track email performance and optimize future communications.

Benefits:

  • Increased Efficiency - Reduces the time and effort required to create and send emails
  • Improved Compliance - Ensures all emails adhere to regulatory and brand guidelines
  • Enhanced User Experience - Provides a seamless and intuitive interface for creating and sending personalized emails

By leveraging Approved Email, organizations can enhance their communication strategies, improve efficiency, and drive better outcomes.

Customers have flexible options for managing Approved Email content in Vault CRM to simplify administration and allow centralized reporting on usage:

  • Approved Email as Document Model – Leverage the built-in content capabilities of the Vault Platform for managing content within Vault CRM using Documents, including content creation, approval, publishing, and sharing
  • Approved Email as Object Model – Manage content creation and approval in PromoMats/MedComms and sync the content to Vault CRM as object records

Customers can enable both models in the same Vault CRM instance, but end users can only be aligned to content via one of the content management methods based on their Application Profile-level Approved Email Settings.

Not all features are available on all platforms. For a list of available platforms for each feature, see Platform Functionality.