Start by stating whether you want accounts with no opportunities at all or accounts with no opportunity matching a condition. Those sets are different.
Check four accounts before building the report
This original fictional fixture uses account IDs rather than customer names:
| Account | Related opportunity stages | No opportunities at all? | No Closed Won opportunity? |
|---|---|---|---|
| A | Closed Won, Closed Lost | No | No |
| B | Closed Lost | No | Yes |
| C | None | Yes | Yes |
| D | Closed Won | No | No |
The intended exception report contains B and C. A must be excluded even though one of its opportunity rows is Closed Lost. A child-row filter selecting only Closed Lost rows would return A and B and would omit C when the report requires a child row.
Salesforce's report-filtering lesson, checked October 24, 2026, explains WITH/WITHOUT cross filters and child-field subfilters. In this case, WITHOUT applies to the set of opportunities satisfying the Closed Won subfilter.
Ask for a report specification, then apply it yourself
Help specify a Salesforce Lightning report; do not connect to an org.
Question: which eligible accounts have no Closed Won opportunity?
Primary records: Accounts. Keep accounts with no opportunities.
Child relationship: Opportunities; child field: Stage.
Teaching records: A=[Closed Won,Closed Lost], B=[Closed Lost],
C=[], D=[Closed Won]. Expected account IDs are B and C.
Existing report type, standard filters, visibility and other filters:
[PASTE ACTUAL SETTINGS OR UNKNOWN].
Describe the Accounts WITHOUT Opportunities cross filter and its
Stage equals Closed Won subfilter. Trace inclusion for A through D.
Explain why child Stage not equal Closed Won is not equivalent.
Identify report-type or visibility constraints that must be checked.
Do not invent field API names, permissions or actions already taken.
OpenAI's prompting guidance supports giving the condition that defines a correct result. This request produces a reviewable specification; it does not imply ChatGPT has inspected or changed your Salesforce report.
Build and inspect a sandbox copy
Open a report type whose primary Account population can include accounts without Opportunities. A type that requires an opportunity may remove C before your filter is applied. Confirm the available cross-filter relationship in the actual builder rather than assuming every custom report type exposes it.
In the report's Filters area, add the cross filter for Accounts WITHOUT Opportunities. Add an Opportunity subfilter selecting Stage equals Closed Won. Use your org's actual field labels and stage values. Set standard scope and account date filters so the four sandbox accounts are eligible, then run the report and inspect account IDs.
If C is missing, check the report type and base Account filters. If A remains, check whether the Stage condition was applied to the cross filter's child records or merely to displayed opportunity rows. Record visibility also bounds the result: a report run is not proof that no qualifying opportunity exists outside the user's access.
The sales-dashboard guide covers a separate question about sales metrics. For this exception report, preserve the Account eligibility rules, WITHOUT relationship and child-stage subfilter in its description. Verify B and C in the sandbox before using the report to assign real follow-up work.