---
schema_version: "1"
id: b89d9f9ead138e066c99afc259543b206ec38a721a9318fdc2cb4ad621af7244
title: Batch Test Agentforce Engagement (Legacy) Nudge Emails 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_nudge_email.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_agent_sdr_batch_test_nudge_email.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 77a1a29364a42c71b1c37a6d13b9b56a2b4d5a82cb0abfd64747b6e8ebd5613b
description: To see how your Engagement agent generates nudge emails to prospects at scale by using the prospect record details and the Draft Nudge Email prompt template action, use Testing Center.
products:
  - Sales Cloud
  - Agentforce
release: "264"
---
# Batch Test Agentforce Engagement (Legacy) Nudge Emails in the Testing Center

To see how your Engagement agent generates nudge emails to prospects at scale by using the prospect record details and the Draft Nudge 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="d19486e61">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d19486e61 ">To set up and test Agentforce Engagement:</td>

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

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

Agents created before October 27, 2025 used an older configuration process in Setup. These agents show only three subagents in Agent Builder. Use these testing steps if your agent shows three subagents in Agent Builder.

In the Testing Center, set test conditions, upload a CSV file, and view the resulting nudge 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 Sales Development Rep 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 nudge emails, select the Record Type, Email Scenario, Action Cadence Step Tracker ID, Record, Email Body, and Test as Last Nudge variables.
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. You fill in only the columns needed for testing nudge 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 nudge email testing scenario. For nudge emails, the CSV file includes these columns.
    
    - Utterance: the request sent to the LLM to initiate drafting the nudge 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 Nudge.
    - Context Variable currentRecordId: This is a record ID of a lead, contact, or person account you want to test with.
    - 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.
    - 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 emailBody: The body of the previous email sent by the agent to the prospect. This can be an actual agent-generated email, or other email content you want to test with.
    - Context Variable testAsLastNudge: tells the LLM whether to treat this nudge as the last outreach that will be sent. Valid values are True or False.
    
    Fill the rows of your CSV file according to these guidelines.
    
       
    | Column NAME | Different Values Per Row? | Input Value | Details |
    | --- | --- | --- | --- |
    | Utterance | No | Draft a nudge email to a lead. Do not schedule the email. Your response should be a text-formatted email and not JSON. | Update to contact or person account if needed. |
    | Expected Subagent | No | Send Outreach |   |
    | Expected Actions | No | \['DraftNudgeEmail'\] |   |
    | Expected Response | No | A nudge email is successfully drafted. |   |
    | Context Variable OrchestrationStage (Email Scenario) | No | Nudge |   |
    | Context Variable currentRecordId | Yes | A valid record ID | For nudge email testing, this is the only column that contains different values per row. The record ID appears in the URL of the record detail page. |
    | Context Variable actionCadenceStepTrackerId | No | 8HF000000000000 | This is a dummy value used for testing. |
    | Context Variable currentObjectApiName | No | Lead or Contact | To test person accounts, use Contact. |
    | Context Variable emailBody | Yes | The body of the previous email sent by the agent to the prospect. | This can be actual agent-generated content, or other email content you want to test against. |
    | Context Variable Is\_Agent\_at\_Last\_Nudge | Yes | True | Can be True or False |
    
    Here’s an example of a valid CSV file for testing nudge emails to leads.![An example CSV file for batch testing SDR nudge 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_nudge_email_csv.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 a nudge 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.