Example: a seller's Account 360
Goal: a rep asks “what should I know before my call with Global Media?” and gets a useful briefing. Configuration only — no code.
What the answer needs
Decide what a good briefing contains before touching the Studio. For most sales teams:
- Who they are — size, industry, relationship status
- What’s in play — open opportunities, their value, whether they’re moving
- What’s on fire — open cases, escalations
- What’s been said — recent activity, who’s engaged
- What’s coming — renewal date, contract end
- What not to say — anything sensitive
That list is the design. Everything below implements it.
1. Start from the shipped entity
Open Studio → Entities → Account 360. Editing something that works beats starting from nothing.
2. Write the entity instruction
Accounts here are paying customers only — prospects live in Leads. A renewal inside 90 days with no open opportunity is at risk regardless of health score. Never quote a renewal date to a customer without checking the contract record; the field is populated by an integration that lags about a day.
Three things a rep learns in their second month, that no field says.
3. Curate the fields
Detailed — the briefing itself:
| Field | Why |
|---|---|
Name, Industry, NumberOfEmployees | Who they are |
Type | Customer vs partner changes the conversation |
Health_Score__c | The headline signal |
Renewal_Date__c | The clock |
Owner.Name | Who owns the relationship |
Description | Background, if your org keeps it current |
BillingAddress | One compound field, rendered in postal form |
List — enough to identify the account: Name, Industry, Type, Health_Score__c, Renewal_Date__c, Owner.Name. These are the columns wherever Accounts appear as rows: a related list, a Find Records result, a provider’s record set.
Standard sits between: the list fields plus employees, billing location, and description.
Left out: LastModifiedDate, CreatedDate, AccountNumber, Sic, Ownership, and the custom fields populated on 6% of records. None of them change what a rep would say.
4. Explain the ambiguous fields
| Field | Instruction |
|---|---|
Health_Score__c | 0–100, refreshed nightly. Below 60 warrants outreach; below 40 is escalation. |
Type | ”Partner” means a reseller, not a technology partner. |
Renewal_Date__c | From the integration; lags about a day. Confirm against the contract before quoting. |
The caution on Renewal_Date__c is what stops an agent stating a lagging value as fact.
5. Add the metrics
Numbers, not tables, for anything a rep would ask “how many” about:
| Label | Definition | Instruction |
|---|---|---|
| Open Pipeline | Sum of Opportunities.Amount where IsClosed = false | Open, unweighted. Excludes closed-lost. |
| Open Opportunity Count | Count of Opportunities where IsClosed = false | |
| Deals Won (12 mo) | Count of Opportunities where IsWon = true, CloseDate ≥ LAST_N_MONTHS:12 | Rolling 12 months, not fiscal year to date. |
| Open Cases | Count of Cases where IsClosed = false | A signal of active support load. |
Metrics that share a child object and the same filter cost one query, so these four cost three — roughly 30 tokens. The related-list equivalent would be hundreds.
6. Add the related lists
Only where individual rows matter:
- Open Opportunities — filter
IsClosed = false, columnslist, sortAmountdescending, max 5. Reps talk about specific deals, not just their total. - Open Cases — filter
IsClosed = false, columnslist, sortCreatedDatedescending, max 5. Paired with the metric: the count gives scale, the rows give specifics. - Recent Activities — filter
ActivityDate ≥ LAST_N_DAYS:90, max 5, newest first.
No Contacts list — the rep knows who they’re calling. Add it only if that’s wrong for your team.
7. Add a reference
Pick OwnerId as the Lookup Field, label it Owner, and set Embed Level to list. The owner then renders with the User entity’s list fields, which carry title, role and manager as well as the name you already curated.
8. Preview
Open Preview, set Level to Detailed, and read it as the agent would. Check that every value carries the meaning a new hire would need, and that no two metric labels could be confused. The open-opportunities columns come from the Opportunity entity’s list curation, so fix them there. Then switch to List and check the account is identifiable.
Token cost should land around 500–700. Well past that, look at the related lists.
9. Save and activate
Click Save, then Activate with a comment worth reading later:
Seller 360: renewal caveat, open-pipeline metrics, filtered lists.
Agents receive data assembled from the active version, never from the draft. If next week proves something wrong, rollback is one action.
10. Connect an agent and ask
Wire up Agentforce or MCP, then ask:
“What should I know before my call with Global Media?”
A good answer covers size, industry, open pipeline with the biggest deal, open cases, and the renewal date, carrying the caveat you attached. The caveat proves the agent reads your instructions, not just your fields.
11. Watch it
After a week of real traffic:
- Quality — FLS coverage below 100% means reps can’t see a field you curated. Low completeness means a field is empty in practice; drop it.
- Usage — rising tokens per load usually means a related list nobody capped.
- Issues — should be empty.