All articles
The Market

On Salesforce and Weighing Agentforce? Read This First

Agentforce is the obvious first look for a Salesforce business, and sometimes the right one. How to tell when it fits, when a self-serve agent that writes into Salesforce fits better, and what that agent actually writes.

11 min read
A dirt track splitting into two paths through a green forest

TL;DR: If you run Salesforce, Agentforce is the obvious first look for an AI agent on your website, and for some businesses it is the right answer. Its Inbound Lead Generation agent lives inside your org, on the Enterprise, Performance and Unlimited editions, and an admin builds it. A self-serve agent that writes into Salesforce from outside suits a different business: another edition, no admin time to spare, a need to be live soon. This guide covers what Salesforce's agent does, from its own documentation, the signals that point to each option, the questions to answer about your org first, and exactly what an outside agent writes into Salesforce, including ours, whose Salesforce connection is in beta.

If you run Salesforce, every conversation about AI on your website starts in the same place. Salesforce makes an agent platform. You already pay Salesforce. Why look anywhere else?

It is a fair question. Sometimes the answer is "don't look anywhere else". Sometimes it is "look hard". The difference depends less on which product is better and more on what your Salesforce org looks like, who maintains it, and how your sales team works.

We build Aijent, an inbound AI sales agent that writes into Salesforce, so we have an interest, and we declare it. Our page, Aijent for Salesforce, makes the case for us. This post helps you work out which kind of tool fits your business, even when the answer is not us.

First, name the job

Agentforce is not one product. It is Salesforce's platform for building AI agents, across service, sales, field service and internal workflows. To compare it with a website sales agent, you have to pick the part that does the same job.

The job here is specific. A stranger arrives on your website. Something answers their questions, works out whether they are a real prospect, and books a meeting with your sales team before they leave. Then the record lands in your CRM so the rep walks in prepared. If you want the longer definition of that job, our plain-English guide to AI sales agents covers it.

Inside Agentforce, that part is called Inbound Lead Generation. So that is the comparison: a sales agent against a sales agent. Agentforce's service and employee agents do other jobs, and they do not belong in this decision.

What Salesforce's own inbound agent does

Everything in this section comes from Salesforce's own help documentation, read in November 2026. Salesforce updates these pages often, so check them yourself before you decide.

Salesforce describes Inbound Lead Generation as an agent template that engages prospects through web chat or a messaging channel "to answer questions, capture leads, and schedule meetings with your sales team". It is available in Lightning Experience on the Enterprise, Performance and Unlimited editions.

Setting it up is a sequence of admin tasks: turning the feature on, managing permissions, giving the agent its own user record, assigning the reps who can take meetings, configuring a data library, building the agent from the template, and connecting it to a messaging channel on your website.

The considerations page is where the detail lives, and it is worth reading in full. A few points stand out for a buyer:

  • Meetings go to Inbox users. The agent can only assign meetings to users who have Salesforce's Inbox set up with a connected email account. You can choose a group of reps instead of one, as long as the group has no more than 15 users, and the agent shows their combined availability and assigns the meeting to one of them at random.
  • Unbooked leads can be passed on. When a prospect does not book, the lead can be handed to a Lead Nurturing agent. That handoff works for lead records only, not contacts or person accounts.
  • Qualification is optional, and it is a one-way switch. The agent can qualify prospects during the chat. Turning that on also requires one-time password authentication, which in turn needs a verified organisation-wide email address. Once qualification is on for an agent, it cannot be turned off; you build a new agent instead.
  • Your required fields become its questions. Salesforce lists field configurations, such as required dependent picklists, that need changing in Object Manager before records create cleanly.
  • The knowledge library is optional, but helps. Salesforce notes the chat performs better with a data library.

None of this is a criticism. An agent built into an enterprise CRM inherits your objects, permissions, users and rules. That is its great strength, and it is why it needs someone who knows your org to set it up.

On cost: Salesforce publishes its Agentforce pricing, with more than one model, and has a separate help page on billing for sales agents. Read it and confirm with your account team. We will not quote or predict it here.

When Agentforce is the right answer

Be honest with yourself about these. If most of them describe you, start with Agentforce.

You are already on Enterprise, Performance or Unlimited. The edition is the entry ticket. If you hold it, no upgrade stands in the way.

Your sales process runs on the Lead object. Many orgs are built around leads: web enquiries arrive as lead records, assignment rules route them, reps convert them. Salesforce's agent fits that model, and its Lead Nurturing handoff depends on it. If your reporting and routing start from a lead record, an agent that writes leads is the path of least disruption.

You have an admin with time. Not just a person with the admin badge, but someone with real hours for permission sets, user records, field requirements and a messaging deployment, and for maintaining them. If that person exists and is keen, the work is an investment in a tool that lives inside your org for years.

You want messaging channels as well as the website. Salesforce's agent works through web chat or a messaging channel. If your buyers reach you through more than your website, one agent across those channels has real value.

You want one vendor and one contract. Procurement, security review and vendor management all cost time. If that cost is high in your organisation, adding a line to your Salesforce agreement is a rational choice.

When a self-serve agent that writes into Salesforce fits better

Now the other list. If most of these describe you, an outside agent deserves a serious look.

Your edition is not Enterprise or above. Salesforce documents its inbound agent for Enterprise, Performance and Unlimited. An outside agent writes through Salesforce's API, so the edition question becomes whether you have API access. For a business on a smaller edition, that can be the difference between an upgrade conversation and a set-up task.

Nobody has admin hours to give. Plenty of Salesforce customers have a part-time admin or a consultant they call when something breaks. A self-serve agent still needs someone with admin rights for a one-time connection, but the agent itself is configured outside Salesforce, by whoever owns the website.

You need it live soon. Some businesses can plan a project. Others have a campaign starting or a sales team with empty calendars. A self-serve agent should be live in minutes, with the Salesforce connection added the same day. We wrote about why that gap matters separately.

You want the meeting fully booked inside the chat. Ask any vendor exactly what happens at the moment of booking: whose calendar is checked, whether a video link is created, whether the visitor gets an invite while they are still on the page. Our view on why that moment decides whether a hot lead becomes a meeting is in Booking links kill hot leads.

You want to try it before you commit. A free trial lets you put it on your real website, talk to it as a buyer would, and see records land in Salesforce before anyone signs anything.

Your CRM might change. An agent built inside one CRM goes wherever that CRM goes. An outside agent that writes to several CRMs is a decision you do not remake if yours ever changes.

Questions to answer about your own org first

Before you speak to any vendor, including us, answer these.

  1. Which edition are we on, and does it include API access? Your Salesforce admin, or the Company Information page in Setup, will tell you.
  2. Do new web enquiries arrive as leads or as contacts? This is the single most important question in this guide. It decides which agent fits your process without rework.
  3. Who takes the meetings, and in which calendar? Salesforce's agent needs Inbox users with connected email. An outside agent connects to the calendar your reps already use.
  4. Who will set it up, and who will maintain it? Name the person. If you cannot, that is your answer.
  5. What should happen to a visitor who does not book? A Lead Nurturing agent, or a record, a transcript and a human follow-up? Choose the one your team will act on.
  6. Who should not get a meeting? Write it down before you configure anything. Our guide to writing a door policy is a good place to start.

What an outside agent actually writes into Salesforce

"Integrates with Salesforce" can mean anything from a full set of linked records to an email with a form attached. So here is exactly what ours does, from the code, with the limits stated. Ask any other vendor for the same list.

First, the status. Aijent's Salesforce connection is in beta. It works, it is available on Starter, Growth and Pro, and we label it beta in the product, on our pricing page and in our help centre. It is the one CRM connection that is not a single click: you create a small app inside your own Salesforce org and paste its two credentials into Aijent. That step needs someone with admin rights in Salesforce, and the whole connection takes about 17 minutes.

When a visitor books a meeting, Aijent writes:

  • An account, matched by website address first, then by name, or created if neither matches.
  • A contact, matched by email address or created. When it matches an existing contact, it only fills in blanks such as a missing phone number, and never overwrites what is already there.
  • An opportunity, at the first active stage of your pipeline, with the contact attached in a contact role and a close date 30 days out.
  • An event for the meeting itself, with the time and the video link, attached to the contact and the opportunity.
  • A completed task holding the full conversation and the qualification summary, so the rep reads the whole exchange before the call.

Now the limits, plainly:

  • Aijent writes contacts, not leads. If your process starts from the Lead object, with lead assignment rules and lead conversion, Aijent does not feed it. Its records skip straight to contact, account and opportunity. For some teams that is cleaner. For a team built around leads, it is a real reason to prefer an agent that writes leads.
  • No company, no opportunity. Salesforce needs an account before an opportunity can exist. A visitor who books with a personal email address and gives no company name gets a contact, an event and the conversation, but no opportunity.
  • Records are created as the user you connect with. We suggest a dedicated integration user, so your audit trail stays clean.
  • One CRM at a time. Connecting Salesforce disconnects any other CRM you had connected. Records already written elsewhere stay where they are.
  • Attribution needs one picklist value. Aijent tags the contacts and opportunities it creates with a Lead Source of "Aijent", but only if you add that value to your Lead Source picklist. Without it, everything still syncs, just without the tag.

A visitor who leaves an email without booking still becomes a contact with the conversation attached, usually within about 25 minutes, once the chat has gone quiet. A visitor who has a real conversation but leaves no details at all is recorded as a contact named UNIDENTIFIED VISITOR, so genuine interest never disappears silently. When a visitor asks for a person, Live Human Handover, on every plan, brings your team into the chat if someone is online, and otherwise creates an open, high-priority call-back task in Salesforce with the conversation inside it.

The full detail, including the set-up walkthrough, is in our Salesforce help article.

Can you run both?

Yes, as long as each does a different job. A business might run Agentforce for service and internal workflows and an outside agent for inbound sales on the website, both writing to the same Salesforce. What does not make sense is two sales agents on one page, both trying to book the same visitor. Pick one for that job, and decide on evidence.

A fair way to decide

If you are still undecided after the questions above, here is a simple method.

Write down five real questions your best prospects asked last quarter, and one prospect you would have turned away. Put each candidate agent in front of those six conversations, on your own website, writing to your own Salesforce. Then check three things. Did it answer from your real content? Did the right people get a meeting, with a video link and an invite, without leaving the page? And could a rep open Salesforce afterwards and walk into the call knowing everything the visitor said?

That test takes an afternoon with a self-serve product, and Aijent's 14-day free trial on Starter needs no card. With Agentforce, the equivalent test is a configuration project in your org, which is a fine investment if that is where you expect to end up. Either way, decide on what the agent did with your visitors, not on what the slides promised.

The bottom line

Agentforce is the right choice for a Salesforce business on Enterprise or above, with a sales process built on leads, an admin with time, and a preference for one vendor. In that business, an agent that lives inside the org and inherits its rules is worth the set-up.

A self-serve agent that writes into Salesforce is the right choice for a business that needs the inbound job done now, on whatever edition it runs, without an admin project, and wants to see it working before committing. That is the business we built Aijent for, with flat published pricing from $99 a month and conversations included. Its Salesforce connection is in beta, it writes contacts rather than leads, and we would rather you knew both before you start.

Whichever way you go, start from your own org. The right agent is the one that fits the Salesforce you actually have.

Put one on your website.

Live in minutes, trained on your own site. 14 days free, no credit card.

Start free trialSee pricing