UC is using an Einstein Generative AI feature (likely Einstein Sales Emails) to draft personalized emails, but placeholders (e.g., {!Contact.FirstName}) appear instead of actual data from the contact record. Let’s analyze the options.
Option A: The user does not have permission to access the fields.Einstein Sales Emails, built on Prompt Builder, pulls data from contact records to populate email drafts. If the user lacks field-level security (FLS) or object-level permissions to access relevant fields (e.g., FirstName, Email), the system cannot retrieve the data, leaving placeholders unresolved. This is a common issue in Salesforce when permissions restrict data access, making it the most likely explanation and the correct answer.
Option B: The user’s locale language is not supported by Prompt Builder.Prompt Builder and Einstein Sales Emails support multiple languages, and locale mismatches typically affect formatting or translation, not data retrieval. Placeholders appearing instead of data isn’t a documented symptom of language support issues, making this unlikely and incorrect.
Option C: The user does not have Einstein Sales Emails permission assigned.The Einstein Sales Emails permission (part of the Einstein Generative AI license) enables the feature itself. If missing, users couldn’t generate drafts at all—not just see placeholders. Since drafts are being created, this permission is likely assigned, making this incorrect.
Why Option A is Correct:
Permission restrictions are a frequent cause of unresolved placeholders in Salesforce AI features, as the system respects FLS and sharing rules. This is well-documented in troubleshooting guides for Einstein Generative AI.
[References:, , Salesforce Help: Einstein Sales Emails > Troubleshooting – Lists permissions as a cause of data issues., , Trailhead: Set Up Einstein Generative AI – Emphasizes field access for personalization., , Agentforce Documentation: Prompt Builder > Data Access – Notes dependency on user permissions., , , , , ]
