When a user works on a record, the AI sees more than that record's own fields. Two admin settings decide which related records come along: Child Objects in Agent Objects, for the record context used by the chat, record actions and Meet Prep, and Meeting Prep — Additional Objects in Org Profile, which adds further related data to Meet Prep briefs only. This article covers both.
Child Objects: related records in the record context#
On a record page, the Sales Agent sends the record's ticked fields to the AI as context. Child objects add related lists to that context, for example the Opportunities and Cases of an Account.
- Open Ai Agent Admin Setup → Agent Objects and click the parent object, for example Account.
- Select the Child Objects subtab. It lists the objects related to the parent, with the relationship field that links them. History, share, feed and change-event objects are not listed.
- Tick a child object. Its field list opens.
- Tick the fields the AI should read on those related records. All and Clear help with long lists.
- Click ✓ Save Child Objects.
Every ticked child object needs at least one ticked field, otherwise the save is refused with a message naming the object.
Child Objects has its own save button: ✓ Save in the header saves the object's fields, ✓ Save Child Objects saves the related lists. If the parent object has never been saved before, saving its child objects also enables it for the agent.
Limits#
- Up to 10 related records per child object are included. They are not sorted by date, so on a record with many related records the ten are not necessarily the most recent.
- Up to 15 fields per child object are read, counting the record Id and, where the object has one, the Name field, which are always added.
- Address and geolocation fields of related records are not included.
- The user's own access applies: related records the user cannot see are left out. If the user cannot read one of the ticked fields, that whole related list is left out for that user.
Once at least one child object is saved for a parent, the record context of that parent also includes up to 10 recent tasks, up to 10 events and up to 10 Chatter posts linked to the record (tasks and events through their Related To field).
Child object data counts toward the size of each request. Pick the related lists that actually help with the record, not every list the object has.
Meeting Prep: additional objects#
Meet Prep builds a one-page meeting brief from the record, its contacts, recent tasks and events, open opportunities (for an Account) and, when enabled, recent web news. For how users run it, see Meet Prep. The additional objects add your own related data to the brief, for example Cases, Quotes or a custom project object. They are used when Meet Prep runs on an Account or an Opportunity.
- Open Ai Agent Admin Setup → Org Profile and click your profile in the list to open it.
- Scroll to 📅 Meeting Prep — Additional Objects.
- Click Account or Opportunity to choose the parent. The related objects of that parent are listed.
- Tick the related objects the brief should use. For each ticked object:
- Limit sets how many records are read, from 1 to 20. The default is 5. The newest records are used first.
- Show list also shows those records as a clickable list under the brief. Without it, the records are used only as context for the AI.
- Repeat for the other parent if needed. Each selected object is stored once, so an object related to both Account and Opportunity follows the parent under which you last changed the selection.
- Click ✓ Save at the top of the profile.
What Meet Prep reads from these objects#
Unlike Child Objects, Meeting Prep additional objects do not use a field list. The brief reads every field of those related records that the running user can see, apart from a few system fields (such as owner, record type and audit fields) and very long text areas. Long text values are shortened. When Allow PII is off, the same masking as in the record context applies, including fields you flagged as PII. Choose objects with this in mind, and use field-level security to hide fields that should not be part of a brief.
Web search in briefs#
Meet Prep: include web search in the AI settings of the Org Profile adds recent company news to each brief. It is off by default because it adds roughly 30,000 input tokens per brief.
Output length#
A full brief is a long, structured answer. Meet Prep uses Max Output Tokens from the Org Profile or 3,500 tokens, whichever is higher. If briefs come back incomplete or empty, especially in languages other than English, raise Max Output Tokens above 3,500. See Org Profile settings.
Troubleshooting#
- A related list is missing from chat answers about a record. It is not ticked under Child Objects for that parent, the user cannot see those records, or the user cannot read one of its ticked fields.
- A brief has empty sections on a record with plenty of data. The related objects are not selected under Meeting Prep — Additional Objects, or they were selected for the other parent.
- Meeting Prep changes are not applied. The selection is part of the Org Profile. Click ✓ Save on the profile after changing it.