---
schema_version: "1"
id: 8373f356322bfdb9ee859ceba97b48d7bfbc8fcbd8d0b6422733eb44759f413f
title: Agentforce Platform | Draft or Revise Email
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/copilot_actions_ref_draft_or_revise_email.md
canonical_url: https://help.salesforce.com/s/articleView?id=ai.copilot_actions_ref_draft_or_revise_email.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3abd05c499d52ec74b291df5a24f57e40364dba6caaa26939a0d307b239a67b3
description: Creates or revises a draft of an email to a recipient based on the user’s request and available email types. Email drafts include a recipient, subject, and email body. Email drafts can be sent through the Salesforce email composer or copied to another email client.
products:
  - Agentforce
  - Cross Cloud
release: "264"
---
# Agentforce Platform | Draft or Revise Email

Creates or revises a draft of an email to a recipient based on the user’s request and available email types. Email drafts include a recipient, subject, and email body. Email drafts can be sent through the Salesforce email composer or copied to another email client.

### 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</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Foundations, or <strong>Agentforce 1</strong> or <strong>Einstein 1</strong> Editions</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="d213534e77">User Permissions
            Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d213534e77 ">To draft or revise sales emails:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d213534e77 ">Einstein Sales Emails</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" colspan="2" style="vertical-align:top;" headers="d213534e77 ">See <a href="https://help.salesforce.com/s/articleView?id=ai.agent_actions_common_perms.htm&amp;type=5&amp;language=en_US" target="_blank">Common User Access for Standard Agent
              Actions</a>.</td>

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

## Action Details

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">API Name</td>

            <td class="slds-cell-wrap" style="vertical-align:top;">DraftOrReviseEmail</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Reference Action Type</td>

            <td class="slds-cell-wrap" style="vertical-align:top;">Standard Action</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Reference Action</td>

            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Draft or Revise Email</p>
              <p style="margin-bottom:0;">(draftOrReviseEmail)</p>
            </td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Does this action execute one or more prompt templates?</td>

            <td class="slds-cell-wrap" style="vertical-align:top;">Yes</td>

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

## Chain Multiple Actions Together

The Draft or Revise Email action can be combined with other actions. For example, the AI agent can help a user summarize a call and then email it to a prospect. Behind the scenes, the Summarize Record action passes the action’s output (a summary) to the Draft or Revise Email action as an input.

The user can combine their requests into a single utterance, or they can make two separate requests.

**Examples**

- Single Request: “Find the return policy for the Studio Pro headphones and email it to this customer.”
- Single Request: “Summarize the Acme campaign and email it to Sofia Rodriguez.”
- Multiple Requests: “Summarize this case.” And then: “Email the summary to John Smith.”

**Best Practices**

For optimal results, break up lengthy or complex requests into more specific steps. Also, if the request involves more than one object or the type of object is unclear, include the object name in the utterance.

- Less Effective: “Email the activities of the latest case for Acme to John Smith.”
- More Effective: “Summarize the activities of the latest case for the Acme account, and email it to John Smith.”

## Draft or Revise Email and Prompt Templates

This action calls the Draft or Revise Email standard invocable action, which uses internal-only prompt templates to generate and revise email drafts.

## Considerations

- If the recipient is a contact or lead, the action assumes the user has the persona of a sales rep. For example, if a service agent uses the action to draft an email to a contact, the generated email could introduce the agent as a salesperson. But if the service agent uses the action to draft an email related to a different object, the email isn’t tailored to a particular persona.
- If the email recipient is a contact or lead, the action can generate a sales introduction email, as well as other types of sales emails, such as a follow-up or check-in. The agent analyzes the user’s request to determine whether the draft is created as an introductory email or other type of email.
- The email’s tone is set by default. For introduction emails, the conversational style is professional and neutral. For other types of sales emails, the conversational style is professional and friendly.
- Draft or Revise Email uses the agent’s language settings. It writes the email in the language the user uses in the request, as long as that language is the agent’s default language or one of its allowed languages. To add a language, see [Update Language Settings](https://help.salesforce.com/s/articleView?id=ai.copilot_setup_tone.htm&release=264.0.0&type=5 "Change the language and tone of your agent’s messages to better suit your company’s brand."). For the languages Agentforce supports, see [Agentforce Language Support](https://help.salesforce.com/s/articleView?id=ai.agent_language_support.htm&release=264.0.0&type=5 "Learn about supported languages, multi-language setup, and agent testing with Agentforce Builder.").
    
    For example, if Spanish is an allowed language for the agent and a user asks the agent to draft an email in Spanish, the email is in Spanish. To change the language of an existing draft, a user can ask the agent to translate it.
- The Draft or Revise Email action relies on the [Send Email global action](https://help.salesforce.com/s/articleView?id=sales.send_email_action_global_layout.htm&type=5&language=en_US). Changing the API name of the Send Email global action can cause the Draft or Revise Sales Email action to fail.
- A user can’t send an email directly from the Agentforce panel. They can open the draft in the Salesforce email composer or select **Copy** to paste it into a client of their choosing.
- Users can’t add a link or attach a file to an email draft directly from the Agentforce panel, but they can make these changes in an email composer.
- The Draft or Revise Email action works best when users specify complete requests, including:
    - The recipient of the email (required).
    - Whether the email is intended for a recipient the user is engaging for the first time.
    - Specific information to include in the draft, such as an invitation to an upcoming conference or a reference to an earlier conversation.
    - When revising, specific elements of the email to change, such as style, tone, or length. If the changes are significant, it can be easier to start over with a new draft.For example: “Shoot an email to Luca Donovan to schedule a meeting to check on progress, review the latest features, and introduce Jaxon Reyes as their account representative. Offer multiple time options for them to choose from.”
- If a user’s request doesn’t contain all required inputs or a required input isn’t valid, the AI agent can’t execute the action and generates an error message. The user must make a new request.
- If users specify more than one record in their request, the action can fail. For example, if a user requests an email to a contact and also mentions the name of an opportunity, the agent can return an error. It’s a best practice for users to mention only the record name of the recipient.
- If PII masking is turned on, the generated email can sometimes contain placeholders for the Salesforce data. Users can replace the placeholders with the relevant information before sending the email.
- Supports drafting for multiple recipients (up to 10).
- CC and BCC fields aren’t supported.
- A limit of 10 recipients is enforced to help prevent triggering spam filters.