---
schema_version: "1"
id: 11dfabbd8a005a088bbf623c8d6fda1350916cd239cc868044dadcd2f35577c3
title: Batch Test Agentforce Engagement Introductory Emails with Modular Actions in the Testing Center
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/sales_agent_sdr_batch_test_modular_intro_email.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_agent_sdr_batch_test_modular_intro_email.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 68439ddcef215b3f445b05e45e7342109215907c067c5a33182471b8d3f50d2c
description: To see how your Engagement agent generates initial emails to prospects at scale by using the prospect record details and the Draft Initial Outreach Email prompt template action, use Testing Center.
products:
  - Sales Cloud
  - Agentforce
release: "264"
---
# Batch Test Agentforce Engagement Introductory Emails with Modular Actions in the Testing Center

To see how your Engagement agent generates initial emails to prospects at scale by using the prospect record details and the Draft Initial Outreach Email prompt template action, use Testing Center.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience in <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> editions with Sales and Einstein for Sales.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d18706e63">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d18706e63 ">To set up and test Agentforce Engagement:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d18706e63 ">Configure Engagement Agent</td>

          </tr>
        </tbody>
      </table>

Agents created after October 27, 2025 by using the guided configuration process in Setup use six modular subagents. Use these steps if your agent shows 6 modular sub agents in Agent Builder.

In the Testing Center, set test conditions, upload a CSV file, and view the resulting intro emails.

1. In Setup, enter Testing Center in the Quick Find box. Then click **Testing Center**.
2. Click **New Test**.
3. Give your test a name and select the Agentforce Engagement agent as the agent to test. Add a description for your test if you want. Click **Next**.
4. On the Test Conditions page, click **Include context variables**. Context variables define the conditions for your testing scenario, such as whether you’re testing leads, contacts, or person accounts, intro emails or nudges, etc.
5. From the list of context variables, select the variables needed for your test. Then click **Next**.
    
    For testing intro emails, select these variables:
    
    - currentObjectApiName
    - Contact ID
    - emailBody
    - End User Id
    - End User Language
    - actionCadenceStepTrackerId
    - isFinalMessage
    - currentRecordId
6. On the Test Data tab, **Upload Test Cases (.csv)** is selected by default. Use this option to create and upload a CSV file. Click **Template** to download a CSV file containing the columns you need for your test. Fill in only the columns needed for testing intro emails.
7. Open the template CSV file in a spreadsheet editor like Microsoft Excel or Google Sheets. Delete the placeholder data beginning on row two. Then populate the rows with the lead, contact, or person account records and the associated context values that define your intro email testing scenario.
    
    For intro emails, the CSV file includes these columns.
    
    - Utterance: the request sent to the LLM to initiate drafting the intro email.
    - Expected Subagent: the subagent used to draft the email.
    - Expected Actions: the agent action used to draft the email.
    - Expected Response: the type of response requested from the agent.
    - Context Variable OrchestrationStage: the email testing scenario. In this case the scenario is Intro.
    - Context Variable currentObjectApiName: the name of the object you’re testing. Valid values are Lead and Contact. To test with person accounts, use Contact.
    - Context Variable currentRecordId: This is a 15-digit record ID of the lead, contact, or person account you want to test with. Use the first 15 digits of the ID found in the record’s URL.
    - Context Variable $Context.ContactId: This is a 15-digit record ID of the lead, contact, or person account you want to test with. Use the same value as the currentRecordId.
    - Context Variable emailBody: the body of the email the agent will reply to. Use only for testing reply emails.
    - Context Variable isFinalMessage: indicates whether a nudge email should be considered the last email to be sent to the prospect. Use a value of TRUE only for testing final nudge emails.
    - Context Variable EndUserId: the 18-digit ID of the agent’s user record.
    - Context Variable actionCadenceStepTrackerId: Your agent uses Sales Engagement Cadences to orchestrate its outreach. This is the ID of the email cadence step tracker associated with the lead, contact, or person account record. In Testing Center, use the dummy ID 8HF000000000000.
    
    Fill the rows of your CSV file according to these guidelines.
    
       
    | Column NAME | Different values Per Row? | Input Value | Details |
    | --- | --- | --- | --- |
    | Utterance | No | Draft an initial outreach email. |   |
    | Expected Subagent | No | sales\_sdr\_agent\_InitialOutreach |   |
    | Expected Actions | No | \['GetRecordDetails'\] |   |
    | Expected Response | No | An initial outreach email is successfully drafted. |   |
    | Context Variable OrchestrationStage (Email Scenario) | No | Intro |   |
    | Context Variable currentObjectApiName | No | Lead or Contact | To test person accounts, use Contact. |
    | Context Variable currentRecordId | Yes | A valid 15-digit record ID | For intro email testing, this column will contain different values per row. The record ID appears in the URL of the record detail page. Use only the first 15 digits. |
    | Context Variable $Context.ContactId | Yes | The ID of the prospect record. | This is the same value as the currentRecordId. |
    | Context Variable emailBody | No | The body of the previous email sent by the agent to the prospect. | Not used for testing intro emails. |
    | Context Variable isFinalMessage | No | False | Use a value of False for testing intro emails. |
    | Context Variable EndUserId | No | The ID of the prospect owner’s user record. |   |
    | Context Variable actionCadenceStepTrackerId | No | 8HF000000000000 | This is a dummy value used for testing. |
    
    Here’s an example of a valid CSV file for testing intro emails to leads.![An example CSV file for batch testing SDR intro emails.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_agents-264-0-0-production-enus/3bcb4a4b-868d-4b4f-b735-d76004124785/sales_agents/images/sales_agents_sdr_intro_email_csv2..png)
8. On the Test Data page, click **Upload Files**. Select the CSV file that you created and click **Open**. When the upload is complete, click **Done**.
9. On the Evaluations page, a list of the available output quality evaluations appears. Select the evaluations that you want to see for the generated output. Then click **Save & Run**.
    
    Your new test appears in the Tests list in the Testing Center.
10. To run your test, click the test name in the Tests list.

The agent generates an introductory email to each of the prospects by using the parameters in your CSV file. The generated output and evaluations appear in the Test Results list. Because you aren’t actually sending the generated email during testing, email scheduling errors can appear in the results. You can ignore these errors.

Check the results to see if the generated emails meet your business requirements.