Kylon vs Salesforce

Salesforce is configured by an admin. Kylon is asked in the room.

Kylon is a workspace where agents sit with the team, read the thread and the tools you connected, and hand back the records, the dashboard and the email draft for one person to approve.

Choose Salesforce if

A system of record an admin configures and reps keep current.

Choose Kylon if

A room where you ask for the work and approve what comes back.

Get started

01 Which one is the right answer

Not every team should pick the same one.

Salesforce is the right answer when

The company runs a defined revenue process with custom objects, territory and forecasting hierarchies, and an admin team that owns it. Salesforce is built for that depth and an agent layer sits inside the model that team already maintains.

Kylon is the right answer when

The work starts as a message rather than a record. Someone asks a question in a room, the answer needs the mailbox, the thread and the CRM at once, and what comes back has to be reviewed by a person in the same place they asked.

02 Operating model

How each one works

Every statement about Salesforce below cites Salesforce's own documentation or product pages. Checked 2026-09-16.

Where the work happens
SalesforceSellers work in Sales Workspace, a Salesforce home that brings together agent activity, accounts, contacts, forecasts, metrics and recommended actions, and is used to prepare for meetings, assign leads and review opportunity updates.Source: Configure Sales Workspace for Optimal Team Performance, Salesforce Trailhead
KylonThe work happens in the room where the team already talks about the deal. The request, what the agent read, and the records it produced are one thread that people and agents both read.
Who keeps the records current
SalesforceEinstein Activity Capture syncs a Microsoft or Google account with Salesforce and links email and calendar activity to the related contacts, leads and opportunities. Salesforce writes that the feature automates data entry, and administrators configure access, connected apps, exclusions and activity sharing.Source: Einstein Activity Capture, Salesforce Help
KylonAn agent reads the mailbox, the calendar and the room thread you granted it, then writes the contact, the company and the deal stage as a proposed change you can see before it lands.
Reviewing a field change
SalesforceIn Sales Workspace an agent can read sales conversation transcripts and communications to identify possible pipeline changes such as a stage move or a next step, and the seller selects Review to verify and accept those field updates before they are applied.Source: Configure Sales Workspace for Optimal Team Performance, Salesforce Trailhead
KylonEvery write an agent proposes arrives in the thread as one approval, with the source it read next to it. Approving applies the whole set, including the CRM rows and the email draft that goes with them.
How an agent gets context and permission
SalesforceFor an internal use case an Agentforce agent runs in the context of the logged in user, and licenses, permissions, field level security and sharing settings determine what it can reach. Other agents run as a dedicated agent user that Salesforce says starts with limited permissions and must be granted what its work requires.Source: Designing Effective AI Solutions for Agentforce, Salesforce Trailhead
KylonAn agent reads the rooms it is a member of, the files and records attached to them, and the connected accounts granted to it. Access is the room and the grant, and the agent states what it read in its reply.
What an agent is allowed to do
SalesforceSalesforce structures an agent as subagents, each a job holding actions and instructions, and the assigned subagents together determine what the agent can do. Behaviour is set through instructions, action access, guardrails and escalation criteria configured up front.Source: Subagents, Salesforce Help
KylonAn agent is scoped by the tools connected to it and the approval step in front of anything that sends or changes something outside the room. A new task does not require a new configured action first.
What setting it up takes
SalesforceAgentforce reuses Salesforce workflows, prompt templates, Apex and APIs as agent actions, and administrators and developers use Agent Builder to define jobs, instructions, actions and guardrails, then enable the relevant features, grant permissions, configure data and channels, and test in an org.Source: How Does Agentforce Work?, Salesforce
KylonSetup is inviting the agent to a room and connecting the accounts it should read. The first useful run is a sentence in that room, not a build step.

What Kylon is for

Kylon is the layer where the work is asked for and approved. It reads the tools you already run, including a CRM, and returns records, dashboards and drafts into the conversation that produced them. Running a configured revenue process with custom objects and forecasting hierarchies is a different job, and Kylon does not try to be that system of record.

Questions people ask

Do we have to leave Salesforce to use Kylon?
No. Connect the Salesforce account to the room and the agent reads and writes through it, so the records stay where your process already lives.
Does anything get written without someone seeing it?
No. Record changes and outbound email arrive as one approval in the thread, with what the agent read shown beside it.
What happens to the work that lives outside the CRM?
That is the point of the room. The mailbox thread, the shared file and the CRM record are read together, and the result comes back in one place instead of three.

Keep reading

The CRM is not the hard part. Keeping it true is.

Put an agent in the room where the deal is discussed, connect the mailbox and the CRM, and approve the records it writes back.

Get started