Scoring Context Fields decides which fields of a Lead or Opportunity the AI actually reads when it scores the record. It is the setting with the biggest effect on score quality. This article explains how to choose the fields and how the optional web verification works.
How it works#
- Fields ticked: exactly those fields of the record are sent, plus the record's name. There is no limit on how many you tick.
- Nothing ticked: scoring falls back to a built-in set of business fields plus the fields ticked for the object in Agent Objects (when that object is active there), up to 25 fields in total.
- Empty values are left out. A field that is blank on a record is not sent at all, so the AI treats it as unknown rather than as a negative signal.
- Fields the user cannot read are left out. Scoring reads the record as the user who runs it: the user on the record page, the user whose change started automatic scoring, or the admin who started a batch.
Besides these fields, every scoring request also contains a short summary the package builds itself: days since the record was created and since its last activity (and, on an Opportunity, days to the close date), the subjects and dates of up to five recent tasks (with their status) and five recent events, your won/lost examples, and your scoring instructions from the AI scoring setup.
The picker is separate from the Agent Objects field list on purpose. The chat needs many fields to answer questions. Scoring works best with a small set of fields that carry a real signal.
Choose the fields#
- Open Ai Agent Admin Setup → AI Scoring and select Lead or Opportunity.
- In Scoring Context Fields, tick the fields that tell a good record from a poor one.
- Click ✓ Save Scoring Config.
The picker lists the fields of the object itself that you can read. The counter shows how many fields are selected. Clear removes all of them; once you save, scoring switches back to the fallback.
What to tick#
Five to ten fields are usually enough. A long list dilutes the prompt.
| Object | Typical choices |
|---|---|
| Lead | Title, Company, Lead Source, Industry, Number of Employees, Country, Website, a description or notes field, and any custom qualification fields |
| Opportunity | Stage, Amount, Close Date, Type, Lead Source, Next Step, any custom fields on the Opportunity that carry account information (for example formula fields for the account's industry or size), and custom deal fields |
Leave out fields that describe the record's administration rather than the prospect, such as record type, system dates or AI Engine's own score fields. Record age and last activity are already in the summary above.
Email and phone fields help only when Allow PII is on in the Org Profile. With it off, the AI sees a token such as EMAIL_1 instead of the value.
If a score reason says the record has no company or title although it has both, those fields are not ticked here.
Personal data#
Masking follows the Org Profile: when Allow PII is off, the values of email, phone and address fields, and of fields you marked as PII (Custom PII Fields in the Org Profile, or Mask as PII in Agent Objects), are replaced with tokens before scoring, as elsewhere. Email addresses and some other identifiers inside free text are masked too. See PII masking.
Verify Company On The Web#
The Verify Company On The Web switch sits in the same card and is off by default. Turn it on and click ✓ Save Scoring Config. When it is on, scoring runs one web search per record before scoring it. The search checks that:
- the company exists
- its domain and website are genuine
- on a Lead, the person really holds the stated role at that company (only when Allow PII is on, see below)
The result is added to the scoring prompt. This is a strong signal for inbound web-form leads, where fake or mistyped entries are common. If the record has no company name, email domain or website, or the search fails, the record is scored without it.
Keep in mind:
- Cost. It adds one AI request per scored record, so a 200-record batch makes 400 requests.
- What is sent to the provider's web search. On a Lead: the company name, the email domain and the website, plus the person's name and title only when Allow PII is on. On an Opportunity: the account's name and website. The web search does not include the email address or phone number.
- Azure OpenAI. With Azure OpenAI as the provider, the web search goes to OpenAI through a Named Credential named
OpenAI.
Good to know#
- Scoring context fields are set per object. Configure Lead and Opportunity separately.
- Changing the fields affects the next scores. Existing scores stay until the records are scored again. Use Re-score already scored records with ▶ Score All … Now to re-score up to 200 records per click. Repeated clicks with the box ticked can pick the same records again, so they do not work through a larger set in turn.