Automated Vendor Coordination

Automated vendor coordination automates the process of prompting internal and external users to process DSRs when they are submitted, and it enables the customization of email digests and other associated settings for each vendor. This is useful when there is no automated programmatic integration available for a given vendor.

There are several reasons why we might not have direct integrations with certain vendors:

  • The vendor has no API for a certain type(s) of DSRs
  • The vendor expects you to send an email in a specific template
  • The vendor only provides a self-serve dashboard to submit DSRs, and someone on your team would need to log in and submit the request through their browser
  • You want to notify an internal team to perform a manual process against a database or internal tool that is not integrated

Creating AVC integrations is similar to any other integration type. Go to the Integrations page.

To configure an AVC integration for a supported vendor, you can use the search bar to find them. Transcend has presets for each vendor even if they are just email based integrations.

If you are setting up an internal AVC integration, or don't see the vendor you want to connect with:

  1. Search for the "Prompt a Person" integration.
  2. Click on the "Prompt a Person" card to open the configuration window.
  3. Review the Data Points that are in scope for this integration, and click on "+ Add"
  4. On this page, you can create an Integration title (to make it easier to find this integration in the future) and configure the assignee for requests reaching this integration.
Screenshot of the "Prompt-a-Person" configuration screen

See more in Connecting integrations.

When configuring an AVC integration, you have the option to change the email address, templates and notification frequencies to your liking.

To change,remove, or add an email address or email template for an existing integration, follow these steps:

  1. Navigate to Integrations

  2. Search for your integration and click on the tile to open the settings

  3. Navigate to the DSR Automation tab

  4. Scroll down to the "Email Automation" section.

    Screenshot of the Prompt-a-Person integrations editing screen
  5. Here you can specify whether emails should be batched across multiple requests ("Across Active Data Subject Requests") or sent for each request as they are ready ("Per Data Subject Request").

    • If you decide to batch notifications "Across Active Data Subject Requests", you can configure the "Email Frequency" to specify how often email notifications should be sent (per hour, per day, per week, etcâ€Ĥ)
  6. You can decide to include a CSV with the identifiers of the requests by clicking on the "Include identifiers in email" toggle.

  7. Additionally, you can configure how these integrations need to authenticate to process requests through the "Completion Link Authentication Type" field:

    • The default is set to "Require receiver(s) to log in with SSO or username/password", requiring the integration owner to have access to Transcend. This is the recommended setting for internal data silos.
    • When configuring an AVC integration for third party vendors, the recommended setting is to "Allow anyone receiving the email to view outstanding requests for this integration", which will authenticate the email address and expose the bulk respond interface even without access to the platform.
    • A third option of "Send no link and automatically mark datapoints as resolved once email is sent" can be selected. This disables the bulk respond interface entirely for the integration. Instead, an email will be sent to the vendor with the CSV of identifiers attached. The request will immediately mark those integrations as completed and continue processing the request without waiting for the vendor to respond.

Read more about connecting and configuring integrations.

Before you can configure specific elements of the workflow, you'll want to make sure that emails are sent from an internal email address. Most vendors require that DSR emails are sent from a domain that your company owns. Review our guide on setting up email domains to get started.

Each integration that you configure with email notifications can have its own custom email template. You can customize each email template to have instructions on how to fulfill the request, or you can simply use the default email template to notify a vendor to respond to a DSR.

By default, your organization will come with an email template named "Automated Vendor Coordination". Each integration will default to this email template. If you want to change the default language for all vendor emails, edit this template.

To learn more about how to create or adjust email templates, refer to our Configuring and Editing Email Templates article.

Configuring Email Templates for Specific Vendors

If you want to use specific email templates for each vendor, you will need to:

  • Navigate to the "integrations" page

  • Find the AVC integration you'd like to customize.

Tip: you can use the filter button to find all your AVC integrations

Integrations filter, AVC selected
  • Click on the integration to see the details of the integration

  • Navigate to the "DSR Automation" tab and scroll down to the "Email Automation" section

  • Configure the details of the integrations as you see fit.

Integrations > DSR Automation, Email Automation settings

Specific templates variables are available when sending emails relating to data subject requests.