CRM workflow automation

A workflow needs someone to build it. Ask for the outcome instead.

Nothing is saved to the CRM until a person approves it. The agent reads the case, proposes the record change with the evidence behind it, and waits in the thread. A configured rule still covers what somebody anticipated and built. This is for the case that came up this morning.

Get started

Three CRM workflows, from the case to the reviewed record

Each one starts in the room where the account is discussed. When it should repeat, the same request is kept as a scheduled or event driven run, and every run keeps its history.

01

Inbound lead to a qualified record

A form arrives. The agent researches the company, writes the account note, fills the fields it can source, and drafts the first reply from the connected mailbox.

The record change and the email wait for approval.

02

Call notes to an updated deal

The agent reads the call notes and the thread above them, then proposes the stage, the next meeting and the open concerns as a change to the deal, field by field.

The deal changes only after someone approves it.

03

A quiet deal to a follow-up

A scheduled run finds deals with no recent activity, reads what was last agreed, and drafts a follow-up that picks up from there.

Each draft waits for the owner to edit or send it.

Before anything is saved

The change is proposed with its evidence, and it waits for you.

CRM reasoning is the current comparison point: Salesforce describes Koa as planning and carrying out multi-step CRM work, and its benchmark figures are the vendor's own. The questions a revenue team still has to answer are what gets written, by whom, and when. In Kylon each of those is a setting in the workspace rather than a sentence in a prompt.

Salesforce's Koa announcement, checked 21 September 2026

The decision
What you set
Where you see it
Which records it can reach
The CRM account the workspace connected, and the rooms the agent belongs to
The agent names the records and threads it read, and the grant can be taken back on its own
What it prepares without asking
Reading the thread, researching the account, writing the note and the reply
The proposed update sits in the conversation with the evidence beside it
What waits for a person
Every write to the CRM and every outbound email
An approval card in the same thread, showing the change it would make
What happens after approval
The update goes through the connected account, and the same work can be kept as a scheduled run
Run history next to the request that started it
How you stop it
Pause the run, or take back the CRM connection the step depends on
The run stops at its next step, and anything already drafted stays unsent

This page does not claim support for any particular vendor's CRM model. These controls belong to the workspace and hold for every agent in it.

The case
A configured rule
A request in the room
Writing to the record
The rule sets the field the moment the condition matches, whatever the rest of the record says.
The change is proposed with the evidence it came from, and it is written after a person approves it.
Getting it running
Choose the module, define the trigger and the conditions, attach the actions, test it, turn it on. Someone has to own the editor.
Describe the outcome in a sentence. If it should repeat, keep the same request as a scheduled or event driven run.
The case nobody anticipated
No rule matches it, so it is done by hand, or it is not done.
The agent reads the case as described, does the work, and shows what it read before anything is applied.
Judgement inside the step
A rule can set a field, assign an owner, create a task or call a function. Deciding which of three replies fits this customer is not a condition.
The agent drafts the reply from the thread, and the person who knows the customer approves or edits it in place.
Seeing what happened
An execution log, in a different place from the work.
The run, what it read and the result are one thread in the room, readable by the people it affects.

What the agent reads before it acts

The room and the thread where the work was asked for, the files and records attached to it, and the accounts you connected, inside the permissions you set. Anything that leaves the room, an email or a change in a connected system, waits for a person to approve it.

Where the result goes

CRM
Salesforce · HubSpot · Pipedrive · Close · Dynamics 365
Tasks
Linear · Jira · Asana · Trello · ClickUp · monday.com
Docs
Notion · Google Docs · Google Sheets · Confluence
Comms
Slack · Gmail · Outlook · Microsoft Teams

How it works

  1. 01

    Ask for the outcome in the room, in plain language.

  2. 02

    The agent names what it read and comes back with the work.

  3. 03

    A person approves the part that leaves the room.

  4. 04

    If the same thing should happen every week, keep it as a scheduled run.

  5. 05

    The runs and their output stay in the room where the team can read them.

What Kylon does not do

It does not replace a deterministic rule that must run the same way ten thousand times. Keep those rules where they are. This is for the work between them, the cases that need reading before acting.

Questions people ask

What is CRM automation?
A rule that watches records for a condition and runs actions when it matches: assign an owner, update a field, create a task, send a notification. It is set up once by whoever owns the configuration.
What does workflow automation help with in a CRM?
It removes the repeated steps nobody should do by hand, and it keeps a process consistent across a team. Its limit is that it only covers the cases someone predicted and built.
Do we keep our existing workflow rules?
Yes. The rules that already fire correctly should stay. An agent is for the work around them that never fit a condition.
Does anything run without a person seeing it?
Email is drafted for a person to send, and anything that changes a connected system waits for approval.
Does the agent write to the CRM by itself?
No. It prepares the update, shows the thread and the records it read, and the write happens after someone approves it. That holds for a one-off request and for the same work saved as a scheduled run.

Keep reading

The rule you never wrote is the one today needed.

Ask for the outcome in the room, approve what leaves it, and keep the ones that repeat.

Get started