Skip to main content
Implementation Guide · Module 7 of 9 · ~10 minutes

Why this matters

Endgame ingests all standard Salesforce fields automatically, but your org likely has custom fields that carry important context: ARR, product line, customer segment, health scores, and so on. By selecting these fields for ingestion, you tell Endgame to reference them by default when answering questions. Without this step, Endgame won’t have access to the fields your team relies on most.

What you’ll do

  • Navigate to the Salesforce configuration page
  • Identify 5-10 custom fields per object that your team asks about most
  • Select fields to ingest

How to prioritize

You don’t need to select all 100 fields right away. Start with the ones your team references in day-to-day conversation: “What’s the ARR on this deal?” or “Which segment is this account in?” If people ask about it regularly, select it for ingestion. You can always add more later as patterns emerge.
Not sure which fields matter most? Ask your top-performing rep what they check in Salesforce before a call. Those fields are your starting list.

Walkthrough

1

Open the Salesforce configuration page

Navigate to Settings > Integrations > Salesforce. You’ll see a list of Required Objects (Account, Contact, Opportunity, User).
2

Start with Opportunities

Click on the Opportunity object. This is where most teams have the highest-value custom fields. Think about the questions your reps and managers ask most often. Common picks include:
  • Revenue fields (ARR, MRR, TCV if tracked separately from Amount)
  • Product or solution fields (Product Family, Use Case, SKU)
  • Qualification or methodology fields (MEDDIC score, stage progression criteria)
  • Forecast category or commit status
  • Renewal or expansion indicators
3

Select fields to ingest

Search for each field, check the box, and click Save Changes. Changes take a few minutes to be reflected in responses.
You can select up to 100 fields per object. Fields that are populated on 1 or fewer records are omitted from the list.
4

Repeat for Account, Contact, and User

Move to the Account object next. Common picks: industry, segment, tier, customer since date, health score, territory. For Contacts, consider: title, role, department, and any custom engagement scoring fields.

Configure additional objects

Below the Required Objects, you’ll find an Additional Objects section. You can sync up to 50 objects total (including required objects). Toggle on any additional Salesforce objects you want Endgame to reference — all fields on selected objects (standard and custom) will be synced. Changes take up to an hour to take effect.

Vendor account exclusion

If your org has vendor accounts in Salesforce, exclude them so internal-only calls aren’t associated with those accounts. Search for and add any vendor accounts under the Vendor Account Exclusion section on the same configuration page. Changes may take a few hours to refresh.

Checkpoint

You’ve completed this module when you’ve selected at least one custom field for ingestion on any Salesforce object. You’ll validate that it’s working in Module 7 (Test Drive) when you ask Endgame questions that reference those fields.

Go deeper


Previous Module

Build Your First Skill

Next Module

Test Drive