What is Agentforce Agent Builder?<\/h2>\n\n\n\n
An AI agent is a helper that reads a request, decides what to do and then does it. For example, a student types “When does the Apex course start?” and the agent looks up the course and replies with the date. Agentforce Agent Builder is the Setup tool where you configure such agents.<\/p>\n\n\n\n
Think of training a new front desk employee. You tell them which kinds of questions they handle, give them simple rules, and show them which forms and systems to use. Agentforce Agent Builder lets you do the same for an AI agent.<\/p>\n\n\n\n
Why Agentforce Agent Builder Matters<\/h2>\n\n\n\n
Students and staff ask the same questions every day. An agent can answer many of them at any hour, and hand the rest to a person. Here is why Agentforce Agent Builder matters at Bright Path Tutors.<\/p>\n\n\n\n
- \n
- First, students get course dates and fees instantly, even at midnight.<\/li>\n\n
- Also, the agent can create an enquiry lead without a human typing anything.<\/li>\n\n
- Next, admins control exactly what the agent may do.<\/li>\n\n
- Agents reuse flows and templates the team already built.<\/li>\n\n
- Finally, hard questions still go to a human through a handoff.<\/li>\n<\/ul>\n\n\n\n
So agents free the team for the conversations that need a person.<\/p>\n\n\n\n
How Agentforce Agent Builder Works<\/h2>\n\n\n\n
An agent built in Agentforce Agent Builder follows a simple loop. First, a user sends a message. Next, the reasoning engine reads it and picks the best topic. Then it follows that topic’s instructions and chooses one or more actions. After that, the actions run, such as a flow that finds a course. Finally, the agent writes a reply using the results.<\/p>\n\n\n\n
![\"Agentforce](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/10\/agentforce-agent-builder-topics-actions-diagram-1-1024x640.png\")
How an agent picks a topic and runs an action.<\/figcaption><\/figure>\n\n\n\n Topics<\/h3>\n\n\n\n
A topic is one job the agent can do, such as “Course Information” or “Enrolment Help”. Each topic has a description that tells the reasoning engine when to use it. It also has a scope that says what the topic covers and what it does not. In newer releases, Salesforce calls topics subagents, but the idea stays the same.<\/p>\n\n\n\n
Instructions<\/h3>\n\n\n\n
Instructions are short rules inside a topic, written in plain words. For example, “Always ask for the course name if the student does not give one.” Good instructions keep the agent on track.<\/p>\n\n\n\n
Actions<\/h3>\n\n\n\n
Actions are the things the agent can actually do. An action can be a flow, an Apex method, a prompt template or a standard action. Each action has a clear name and description, so the reasoning engine knows when to use it.<\/p>\n\n\n\n
The Reasoning Engine<\/h3>\n\n\n\n
The reasoning engine is the AI that connects everything. It reads the message, picks a topic, follows the instructions and calls actions. You do not program it directly. Instead, you guide it through clear topics, instructions and action descriptions.<\/p>\n\n\n\n
Topics vs Instructions vs Actions<\/h2>\n\n\n\n
The table below compares the three building blocks.<\/p>\n\n\n\n
Building block<\/th> What it answers<\/th> Example<\/th><\/tr><\/thead> Topic<\/td> Which job is this?<\/td> Course Information<\/td><\/tr> Instructions<\/td> How should I behave?<\/td> Ask for the course name if missing<\/td><\/tr> Action<\/td> What can I do?<\/td> Flow: Get Course Details<\/td><\/tr> Written by<\/td> Admin<\/td> Admin, often with a developer for Apex<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n When to use which comes naturally. Add a topic for each new kind of request. Then write instructions for rules and tone. Finally, connect actions when the agent needs to read or change data.<\/p>\n\n\n\n
![\"Agentforce](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/10\/agentforce-agent-builder-topics-actions-diagram-2-1024x640.png\")
Topics vs instructions vs actions.<\/figcaption><\/figure>\n\n\n\n How to Build Agentforce Agent Builder Agents Step by Step<\/h2>\n\n\n\n
Let’s use Agentforce Agent Builder to create a course enquiry agent for the Bright Path Tutors website.<\/p>\n\n\n\n
Step 1: Prepare the Actions<\/h3>\n\n\n\n
- \n
- Build an autolaunched flow called “Get Course Details”. It takes a course name and returns the level, fee and start date.<\/li>\n\n
- Next, build an autolaunched flow called “Create Enquiry Lead”. It takes a name, email and course and creates a lead.<\/li>\n\n
- Then test both flows with debug before you use them.<\/li>\n<\/ol>\n\n\n\n
Step 2: Create the Agent<\/h3>\n\n\n\n
- \n
- Go to Setup and open Agentforce Agents.<\/li>\n\n
- Click New Agent and pick a service agent template.<\/li>\n\n
- Next, give it the name “Course Helper” and a short description.<\/li>\n<\/ol>\n\n\n\n
Step 3: Add the Topics<\/h3>\n\n\n\n
The table below shows the topics for this agent.<\/p>\n\n\n\n
Topic<\/th> Description<\/th> Actions<\/th><\/tr><\/thead> Course Information<\/td> Questions about course dates, level and fee<\/td> Get Course Details<\/td><\/tr> Enrolment Enquiry<\/td> Student wants someone to contact them<\/td> Create Enquiry Lead<\/td><\/tr> Escalation<\/td> Student is unhappy or asks for a person<\/td> Hand off to a human<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Step 4: Write the Instructions<\/h3>\n\n\n\n
For Course Information, add instructions such as these.<\/p>\n\n\n\n
- \n
- Always confirm the course name before looking it up.<\/li>\n\n
- Share the fee only in Indian rupees.<\/li>\n\n
- If no course matches, suggest the nearest course name.<\/li>\n<\/ol>\n\n\n\n
Step 5: Test in the Builder<\/h3>\n\n\n\n
- \n
- Open the conversation preview in Agentforce Agent Builder.<\/li>\n\n
- Next, type “When does Apex Basics start?” and check the reply.<\/li>\n\n
- Then open the plan view to see which topic and action the agent picked.<\/li>\n\n
- Finally, try an off-topic question and confirm the agent declines politely.<\/li>\n<\/ol>\n\n\n\n
Step 6: Activate and Deploy<\/h3>\n\n\n\n
- \n
- Activate the agent.<\/li>\n\n
- Then connect it to a channel, such as website messaging.<\/li>\n\n
- Next, assign the agent user the permissions it needs to read courses and create leads.<\/li>\n<\/ol>\n\n\n\n
Writing Good Descriptions<\/h2>\n\n\n\n
The reasoning engine relies on words, so clear descriptions matter most in Agentforce Agent Builder. Describe each topic in one or two plain sentences. Use words students actually use, such as “start date” and “fee”.<\/p>\n\n\n\n
Also give each action a name that says what it does, such as “Get Course Details”. Vague names like “Flow 1” confuse the agent. As a result, it may pick the wrong action.<\/p>\n\n\n\n
Testing Agents at Scale<\/h2>\n\n\n\n
One preview chat is not enough. So prepare a list of 30 to 50 real questions from past emails and chats. Then run them through the agent and check each answer. Salesforce offers a testing center for batch tests, which saves time.<\/p>\n\n\n\n
Repeat these tests whenever you change a topic, an instruction or an action. Small wording changes can shift which topic the agent picks.<\/p>\n\n\n\n
Keeping Agentforce Agent Builder Agents Safe<\/h2>\n\n\n\n
Agents run through the Einstein Trust Layer, which adds protections like data masking. However, admins still decide what the agent can touch. Give the agent user only the permissions it needs. Also keep sensitive actions, such as refunds, out of public agents.<\/p>\n\n\n\n
Common Mistakes with Agentforce Agent Builder<\/h2>\n\n\n\n
- \n
- Writing vague topic descriptions that overlap with each other.<\/li>\n\n
- Giving the agent user broad admin-like permissions.<\/li>\n\n
- Testing with three questions and calling it done.<\/li>\n\n
- Building actions without debugging the flows first.<\/li>\n\n
- Forgetting a handoff to a human for hard or angry conversations.<\/li>\n<\/ul>\n\n\n\n
Best Practices for Agentforce Agent Builder<\/h2>\n\n\n\n
- \n
- Start with two or three focused topics and grow slowly.<\/li>\n\n
- Write instructions as short, clear rules.<\/li>\n\n
- Name and describe every action in plain words.<\/li>\n\n
- Keep a test list of real questions and rerun it after each change.<\/li>\n\n
- Review conversation logs every week to find gaps.<\/li>\n<\/ul>\n\n\n\n
Practice Task<\/h2>\n\n\n\n
Add a fourth topic called “Batch Timings” to the Course Helper agent. It should answer which weekday or weekend batches a course has. Hint: build a small flow that reads a Batch Type field and add it as the topic’s action.<\/p>\n\n\n\n
Most Asked Interview Questions on Agentforce Agent Builder<\/h2>\n\n\n\n
Questions on Agentforce Agent Builder are now common in admin interviews, as more companies roll out agents. Here are the ones asked most.<\/p>\n\n\n\n
Basic Questions on Agentforce Agent Builder<\/h3>\n\n\n\n
Q1. What is a topic in Agentforce?<\/strong><\/p>\n\n\n\n
A topic is one job the agent can do. It has a description, a scope, instructions and a set of actions.<\/p>\n\n\n\n
Q2. What are actions?<\/strong><\/p>\n\n\n\n
Actions are what the agent can do, such as running a flow, an Apex method or a prompt template. Each action needs a clear name and description.<\/p>\n\n\n\n
Q3. What does the reasoning engine do?<\/strong><\/p>\n\n\n\n
It reads the user’s message, picks the right topic, follows its instructions and calls actions. Then it writes the reply.<\/p>\n\n\n\n
Q4. What are instructions?<\/strong><\/p>\n\n\n\n
They are plain-language rules inside a topic. They guide how the agent behaves, such as asking for missing details.<\/p>\n\n\n\n
Practical Questions on Agentforce Agent Builder<\/h3>\n\n\n\n
Q5. The agent keeps picking the wrong topic. What do you check?<\/strong><\/p>\n\n\n\n
First, check the topic descriptions for overlap. Next, make them clearer with words users actually use. Then retest with the same questions.<\/p>\n\n\n\n
Q6. How do you let an agent create a record?<\/strong><\/p>\n\n\n\n
Build a flow that creates the record, test it, then add it as an action in the right topic. Also give the agent user create access.<\/p>\n\n\n\n
Q7. How do you test an agent before go-live?<\/strong><\/p>\n\n\n\n
Use the conversation preview and plan view for single tests. Then run a batch of real questions with the testing tools.<\/p>\n\n\n\n
Q8. How do you keep an agent safe?<\/strong><\/p>\n\n\n\n
Give the agent user minimal permissions, keep sensitive actions out of public agents, and add a handoff to humans.<\/p>\n\n\n\n
Official Resources<\/h2>\n\n\n\n