Salesforce Agentforce workflows save time when each AI agent has a narrow job, a clear set of topics and actions, access to clean CRM data and guardrails that define when it must hand over to a person. Agentforce is Salesforce’s platform for building autonomous AI agents that work inside Sales Cloud, Service Cloud, Marketing Cloud and other Salesforce products, using company data and existing automation.
At the time of writing, Agentforce includes prebuilt agents for roles such as service, sales development and campaign support, and a builder for custom agents. Product names, editions and pricing change often, so confirm details for your org before planning.
How does an Agentforce agent work?
An agent is configured with topics, which describe the jobs it can do, and actions, which are the steps it can take, such as running a Flow, calling Apex, querying records or using a prompt template. The Atlas Reasoning Engine decides which topic matches a request and which actions to run. The Einstein Trust Layer handles data masking, grounding and audit logging for model calls.
Agents work through channels such as Experience Cloud sites, messaging, Slack and the Salesforce interface itself. They rely on Data Cloud or standard CRM records for context.
Step 1: Pick one process with clear rules
Start where the work is repetitive and well documented. Good first candidates include answering order status questions, qualifying inbound leads, booking meetings, summarising cases for handover or drafting follow-up emails after calls.
Write the current process step by step as it is done today. If people disagree on how it works, fix that first; an agent will repeat confusion faster.
Step 2: Clean the data the agent will use
Agents ground their answers in CRM data and knowledge articles. Duplicate accounts, outdated contacts, empty fields and old knowledge articles lead to wrong answers.
- Deduplicate accounts and contacts in the objects the agent reads.
- Archive or update knowledge articles older than your review cycle.
- Fill required fields for the process, such as order status or lead source.
- Check field-level security so the agent only sees what it should.
Step 3: Define topics and actions
Each topic needs a description, scope and instructions in plain language. For a service agent handling order questions, the topic might be “Order status and delivery questions” with instructions such as “Only answer about orders that belong to the verified customer” and “Never promise a delivery date not shown in the order record”.
Example actions for an order status topic
- Verify the customer using email and order number via a Flow.
- Retrieve order and shipment records.
- Summarise status in plain language.
- Create a case and transfer to a human if the order is delayed beyond a set number of days.
- Log the conversation to the contact record.
Reuse existing Flows and Apex where possible. Many organisations already have automation that agents can call as actions.
Step 4: Write guardrails and handoff rules
Guardrails decide what the agent must never do and when it must escalate. Common rules include no refunds above a set value without human approval, no legal or medical advice, immediate transfer when the customer asks for a person, and transfer after a set number of failed attempts to understand the request.
Make handoffs smooth. When the agent transfers, it should pass a summary so the human does not ask the customer to repeat everything.
Step 5: Test in a sandbox with real scenarios
Agentforce Builder includes testing tools, and Salesforce provides a testing centre for running batches of test utterances. Build a test set of 50 to 100 realistic requests, including tricky ones: vague questions, angry customers, requests outside scope and attempts to get information about other customers.
Review which topic each request matched, which actions ran and whether the answer was correct. Adjust topic descriptions and instructions until results are consistent.
Step 6: Roll out gradually
Launch on one channel or a share of traffic first. Monitor conversations daily for the first weeks. Track resolution without handoff, handoff rate, customer satisfaction scores and errors found in review. Expand to more channels or topics only when the first one is stable.
Which workflows save the most time?
- Service: order status, password resets, appointment changes and simple returns.
- Sales: qualifying inbound leads, answering product questions and booking meetings for account executives.
- Marketing: drafting campaign briefs, building segments from natural-language descriptions and summarising campaign results, depending on your Marketing Cloud setup.
- Internal: summarising long case histories or account activity before calls.
What should you avoid in the first rollout?
Avoid giving the first agent too many topics. An agent with fifteen loosely described topics confuses similar requests and routes them badly. Avoid actions that change financial or contractual records without a human step, such as issuing credits or editing contract terms. And avoid launching on your highest-traffic channel first; a quieter channel gives you room to fix problems while customers are few. Each of these is easy to add later once the agent has proven reliable on a narrow job.
How Alien Road applies Salesforce Agentforce
In a typical engagement, discovery maps the client’s Salesforce org: clouds in use, data quality in key objects, existing Flows and the processes that take the most staff time. We rank candidates by volume, rule clarity and data readiness.
Setup covers data cleanup for the chosen process, topic and action design, guardrails and handoff rules written with the client’s team leads, and a sandbox test set built from real past conversations. We reuse the client’s existing automation wherever it fits.
For measurement, we track resolution rate, handoff rate, average handling time for handed-over cases and satisfaction scores, compared with the period before launch. Reporting is weekly during rollout and monthly afterwards, with conversation samples so stakeholders can see how the agent actually behaves.
Where to start this week
Pull last month’s top ten case reasons or inbound lead questions from Salesforce reports. Pick the one with the highest volume and the clearest rules, and write its current process in ten steps or fewer. Note which records and fields each step uses and whether that data is complete. That document is the blueprint for your first Agentforce agent.
Keep reading: CRM System · Crm System