What should An Agentforce consider when using related list merge fields in a prompt template associated with an Account object in Prompt Builder?

When configuring prompt templates in Prompt Builder, it is crucial to understand the limitations of related list merge fields. The Activities related list, which comprises Task and Event records, cannot be used. This is because the WhoId (Name) and WhatId (Related To) fields on these objects are polymorphic, meaning they can link to multiple different types of objects (e.g., a Contact, an Account, an Opportunity). Prompt Builder's merge field functionality does not support this type of complex, polymorphic relationship, and therefore, the Activities related list is not available for use in prompt templates.

B. If person accounts have been enabled, merge fields will not be available for the Account object. This is incorrect. Prompt Builder supports Person Accounts. Merge fields remain available for the Account object, including fields specific to Person Accounts.
C. Prompt generation will yield no response when there is no related list associated with an Account in runtime. This is incorrect. If a specified related list has no records for a given Account, the prompt is still generated, but the section for that related list will simply be empty.

1. Salesforce Help Documentation

"Prompt Template Considerations":

Under the section "Related Lists

" the documentation explicitly states

"Polymorphic relationship fields aren't supported. For example

you can't use the Name field on the Task object (WhoId) or the Related To field on the Event object (WhatId)." This directly supports the correct answer (A).

The same document clarifies the behavior for empty related lists: "If a record has no related list records

the related list section in the prompt is empty." This directly refutes option C.

The documentation also notes support for Person Accounts under the "General" considerations

which invalidates option B.