Case Study

Agentforce for Setup

Role Lead Designer · UX Point of Contact · Patterns Liaison
Team 5 UX, 6 PM, 3 CX, 5 EM · 6 scrum teams
Status Generally Available
Timeline 2025 – 2026

Setup that comes to you.

For decades, Setup made admins come to it: hundreds of pages to navigate and dig through just to find the one thing they needed. Agentforce for Setup inverts that. Instead of sending people hunting, it brings what they need to them, a conversational interface that interprets intent and renders the right components on the fly by pulling from the metadata already in the org. I helped design that agentic layer, shifting the admin experience from manual navigation to natural dialogue.

This is human-AI interaction at its most consequential: an agent acting directly on a customer's production system. The design challenge wasn't just understanding intent; it was building the trust and control that let admins hand real configuration work to an AI.

Across the program, I led the observability experience on Setup Home, designed the agent's recommended utterances, and led user permissioning.

Setup, before and after Setup Home A two-part diagram. On the left, the old Salesforce Setup is a tangled gray labyrinth of scattered menu labels connected by thin threads, with a single meandering path struggling to reach a faint target. On the right, Setup Home is calm and ordered: a central command field reading "Describe your task" with relevant tasks converging inward along clean blue arrows, so what the admin needs comes to them. BEFORE A maze of nested menus Users Profiles Permission Sets Objects Fields Flows Email Apps Security Identity NOW Setup Home brings it to you Reset a password Security health User licenses Add a user Automation Describe your task
For decades, admins hunted through hundreds of nested pages to find one setting. Setup Home inverts the model: describe what you need, and it comes to you.

Where I went deep, and how it scaled.

Agentforce for Setup is a large program. Here's where I went deepest, trust and the agent's on-ramp, and how the same pattern carried across the rest. Jump into any one.

The home, reimagined around the agent.

Setup Home is the surface admins land on. I led its data visualizations and the agentic layer that turns a wall of nested menus into a place that brings the right components to you. It is also where the whole program had to read as one product, since the cards here are rendered from many teams' work.

Setup Home with the Agentforce agentic layer for natural-language admin configuration
Setup Home, reimagined around an agentic layer. Admins configure the platform through conversation instead of nested menus.

A note on this screen: Setup Home is an amalgamation of many teams' work, and several of the cards shown here come from other teams rather than our designs. That's real evidence of cross-team alignment, and also exactly why I owned shared patterns across the program. The friction shows too: notice the competing primary buttons across the suggestion cards, where a clear hierarchy should point to a single next step. Driving toward the shared patterns that resolve that kind of inconsistency was a core part of the work.

An agent you can hand the keys to.

Letting an AI change a production org is a trust problem before it's an interface problem. When the agent isn't certain it understands what an admin wants, it asks a clarifying question instead of guessing, so it never shows the wrong thing or acts on a bad assumption. Before any change is applied, the admin can preview exactly what it will do. Nothing touches the org until they confirm.

This wasn't a hunch. In pre-pilot research, admins' top concerns were exactly these: the agent making changes without confirmation, output they couldn't verify, and losing control of their org. Designing for trust was the way to turn that anxiety into adoption.

"I appreciate it when it comes back with confirmations or questions. When it says 'you requested this, the best way to accomplish it is this action, do you confirm?', that instills a lot of confidence."Pre-pilot research participant

A real request, start to finish. Each step on the left lights up as the agent works through it.

One pattern, everywhere it needed to be.

Trust and recommended utterances were where I went deepest. The same agentic move carried across the other surfaces I owned: ask in plain language, and the agent returns a structured, actionable result right in the flow, with nothing applied until you confirm.

Metrics that start a conversation. I led the observability experience on Setup Home: org health, license availability, and storage. Each visualization doubles as an entry point to the agent, so an admin goes from seeing a number to asking about it and acting on it without leaving the page.

An admin asks the agent to summarize active user license consumption; the agent renders a License Breakdown by License Type table inline alongside a structured summary
Ask about license usage and the agent renders a live breakdown right in the flow, ready to act on.

Lead Designer. Managing permissions and access control by talking to the agent instead of hand-assembling permission sets, profiles, and sharing rules. Access is the highest-stakes thing an admin touches, so it follows the trust pattern exactly: the agent drafts a clear, reviewable change, and nothing applies until the admin confirms. Shipped across two beta cycles in Spring '26.

An admin asks whether a user can modify all data; the agent renders a User Access Summary and the underlying user details inline, instead of digging through permission screens
Ask a plain access question (“Does Emily White have access to accounts?”) and the agent renders a structured summary instead of making an admin hunt through profiles.

Sole designer. Six months of change history used to mean exporting a CSV and parsing it by hand. I designed it as a conversation: ask “show me all changes by John Doe in the last 7 days,” and the agent returns a filtered, sorted table inline, then names exactly how to narrow it further.

Setup Audit Trail in a conversation: an admin asks to see all changes made by John Doe, and the agent returns an inline, filterable table of audit entries and explains how to narrow the results
The audit trail as something you interrogate in plain language, not a spreadsheet you export.

Holding one vision across six scrum teams.

This was a large, fast-moving launch: partners, PMs, and six scrum teams building in parallel. As the UX point of contact and Patterns Liaison, my job was to keep one coherent experience from fragmenting across all of them. In practice that meant collaborating across 15+ teams, including SLDS, Digital Wallet, Formula Management, Content Design, and Setup Audit Trail, and representing our work to the broader Agentic Patterns workgroup. Everything shipped while the patterns were still being written.

1

Single Source of Truth

Owned the shared patterns so they stayed documented and consistently lived across every team, managing pattern changes to prevent the experience from fragmenting.

2

Liaison Function

Acted as the bridge between the core UX vision and individual scrum teams, delivering tailored designs without breaking global standards.

3

Patterns Representative

Represented our team's agentic patterns to the broader Agentic Patterns workgroup, presenting our decisions and reconciling them with the standards forming across the company, so Setup's work strengthened the wider effort instead of diverging from it.

Taking it to customers.

Represented Agentforce for Setup across two booths at Dreamforce: ran live product demos, delivered my team's Dreamforce presentation, and gathered feedback directly from admins and customers.

Tori Rice presenting Agentforce for Setup at a Dreamforce booth, mic in hand, in front of a screen branded Setup powered by Agentforce
Delivering my team's Agentforce for Setup presentation at the Dreamforce booth.

Enablement was the real risk.

I flagged it from the start. Admins would need an onboarding flow and an obvious way to find the feature and turn it on, or a capable agent would sit unused.

It moved up the priority list later, and when it did, I already had a direction: a proposal built on an existing onboarding surface, with an exploration of how it could work.

What once took 20+ minutes or hundreds of clicks
now resolves in seconds
Most-attended AI app-dev session, TDX 2026
337 attendees

Generally available June 2026, free to every admin tier. Featured by Salesforce Ben.

What I'd do differently.

Looking back, I'd make one big call differently. We tried to ship every area at once for the pilot, when the smarter move would have been to pick a single surface, user access, or data models, or flows, and make that one work really well. Supporting that many scrum teams without a shared, reusable component library led to inconsistent implementation. Because the agent's underlying actions weren't built out as fully as they needed to be, it often misread intent and sent people to the wrong place, which is the fastest way to lose trust and lose users.

If we had spent that same energy going deep on one area and earning trust there first, I believe the outcome would have been stronger and far less chaotic. It's the clearest lesson I carry forward: with agents, focused depth and hard-won trust beat broad coverage every time.

Now generally available
Want to talk through it?
Agentforce for Setup shipped and has been generally available since June 3, 2026, and the full story is right here on this page. If you want to go deeper on the research, the flows, or the decisions behind them, I'd love to walk through it together.
Next Project
Agentforce Coworker →
Designing the setup layer for platform-wide agentic search.