Salesforce Agentforce Setup & Guardrails

Start with One Controlled Agentforce Use Case

We begin by defining one specific business outcome, the users or customers the agent will serve, the questions it may answer, the tasks it may perform, the records it may access, the decisions it must not make, and the situations that require human involvement. Agentforce is then configured around this bounded use case so instructions, subagents or topics, actions, grounding, permissions, testing, guardrails, and escalation all support one clear operating model rather than an open-ended AI deployment.

Prepare One Agentforce Environment

One client-provided Salesforce org with active Agentforce and required Salesforce licenses is reviewed and prepared for the included use case. The setup includes basic feature-readiness confirmation, one supported agent type, one primary deployment context, foundational naming conventions, and focused administrative settings. Additional Salesforce orgs, multiple production agents, multi-brand programs, complex environment strategies, and enterprise AI operating-model design remain separate.

Define the Agent’s Role and Boundaries

One agent purpose, role description, company voice, response approach, and approved scope boundary are documented and configured. The agent receives clear instructions for what it should do, what it should avoid, which information it must request before acting, and when it should stop and transfer control. Legal decisions, medical decisions, financial advice, employment decisions, autonomous high-impact decisions, and any other regulated or high-risk activity are excluded unless separately reviewed and approved by qualified client stakeholders.

Structure Topics or Subagents

Up to four approved topics or subagents can be configured for the included use case, each with a focused classification description, scope, reasoning instructions, available actions, and clear transition or exclusion guidance. Up to 24 approved topic-level instructions can be written or refined across the included structure. Large topic libraries, complex subagent networks, multilingual behavior, custom orchestration frameworks, and broad enterprise assistants remain separate.

Configure Trusted Agent Actions

Up to eight approved standard or straightforward custom Agentforce actions can be configured using supported Salesforce capabilities such as existing Flow, prompt templates, record actions, or other client-authorized reference actions. Each included action receives a clear name, purpose, input expectations, output expectations, and action instructions. New Apex development, external APIs, MuleSoft development, complex integrations, high-risk transactions, payment actions, destructive record operations, and large automation redesigns are not included.

Ground Responses in Approved Business Data

One focused grounding approach can be configured using approved Salesforce records, Salesforce Knowledge, or another supported source available in the client’s licensed environment. Up to two approved grounding sources and up to 10 relevant objects, fields, article categories, or content groupings can be aligned with the included use case. Data 360 ingestion, unstructured-data pipelines, large content migrations, website crawling, custom retrieval systems, vector-database design, and extensive content remediation remain separate.

Apply Least-Privilege Data Access

One focused access model is prepared for the agent and up to 10 named pilot users using the Salesforce permissions required by the included use case. The setup includes an object, field, action, and record-access review together with up to five approved permission sets or permission set groups. Agentforce does not replace Salesforce security configuration, so the agent’s effective behavior remains dependent on licenses, user context, sharing, permissions, action security, and the access controls of the underlying data and automation.

Create Practical Guardrails

One use-case risk and guardrail review identifies approved boundaries for privacy, sensitive information, restricted topics, unsupported requests, uncertain answers, action confirmation, record changes, and human escalation. Up to 15 approved behavioral guardrail instructions can be configured across the agent and included topics or subagents. Formal compliance certification, legal review, model-risk management, red-team programs, automated policy engines, bias audits, and regulated-industry validation remain the client’s responsibility or require separate scope.

Design One Human Escalation Path

One straightforward human-handoff path can be configured for the included deployment context where the required Service Cloud, Omni-Channel, Flow, messaging, or employee-channel capabilities are licensed and available. The handoff can include approved triggers, a concise interaction summary, relevant Salesforce context, and routing to one queue, group, or supported destination. Multiple channels, complex skills-based routing, telephony, voice escalation, after-hours orchestration, workforce management, and contact-center redesign remain separate.

Test Expected and Restricted Behavior

One controlled manual test cycle covers up to 30 approved scenarios across topic or subagent selection, instruction adherence, action selection, data access, grounded responses, restricted requests, uncertain conditions, record updates where included, and human escalation. Where Agentforce Testing Center is licensed and available, up to 20 structured test cases can also be prepared or loaded for the included use case. Testing reduces risk but cannot guarantee that every generative response will always be correct, complete, or identical.

Prepare Monitoring and Launch Controls

One focused launch-readiness review covers activation status, assigned users, action availability, grounding access, escalation readiness, test results, and approved usage boundaries. Up to six supported Agentforce or Salesforce reports, views, or monitoring references can be configured or documented where the required data is available. Advanced observability, external security monitoring, custom event pipelines, conversation-quality analytics, automated evaluation systems, and enterprise AI supervision programs remain separate.

Document, Train, and Hand Off

The client receives an Agentforce use-case map, configured scope and guardrail summary, action and access inventory, grounding summary, test record, launch checklist, two 60-minute handoff sessions, and 21 calendar days of launch support. One fixed-scope correction round is included when the original approved requirements remain unchanged. Salesforce, Agentforce, Data 360, Service Cloud, Digital Engagement, Slack, Knowledge, CRM Analytics, MuleSoft, model, conversation, request, action, Flex Credit, storage, processing, and other consumption or license fees are separate. Additional agents, use cases, channels, languages, topics or subagents, actions, grounding sources, custom development, integrations, production content creation, compliance review, continuous monitoring, and third-party fees are separate.