---
schema_version: "1"
id: 7cb35fef03844962a079778f50bc680be5dff8deaaf4901ec1b53954a4037a1c
title: Batch Test Agentforce Engagement (Legacy) Introductory Emails in 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_intro_email.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_agent_sdr_batch_test_intro_email.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ed6c2871914eba3824fa2dcff5a3b60e6df6f5a864da398fee6eb12367a57208
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 (Legacy) Introductory Emails in 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
Available in: Lightning Experience in Enterprise, Performance, and Unlimited editions with Sales and Einstein for Sales.
User Permissions
Needed
To set up and test Agentforce Engagement:
Configure Engagement Agent
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 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 the Record Type, Email Scenario, Action Cadence Step Tracker ID, and Record 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 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 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.
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 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 | \['DraftInitialOutreachEmail'\] | |
| Expected Response | No | An initial outreach email is successfully drafted. | |
| Context Variable OrchestrationStage (Email Scenario) | No | Intro | |
| Context Variable currentRecordId | Yes | A valid record ID | For intro 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. |
Here’s an example of a valid CSV file for testing intro emails to leads.
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.