Kylon vs Close

Close is built around the lead page. Kylon is built around the conversation.

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 Close if

A lead page with the calls, emails and history on it.

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.

Close is the right answer when

The motion is outbound volume: dialling, sequencing and working a list every day, with calling and email in the same window as the record. Close is built tightly around that loop.

Kylon is the right answer when

The deal is carried in threads rather than calls, the context sits across a mailbox, a document and a chat, and the result has to come back to the same room for a person to approve.

02 Operating model

How each one works

Every statement about Close below cites Close's own documentation. Checked 2026-09-16.

Where the work happens
CloseWork centres on the Lead page, where a company carries its contacts and opportunities alongside tasks, custom fields and a chronological history of calls, emails, status changes, completed tasks and notes.Source: Leads, Close Help
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 instead of a page per lead.
Who keeps the records current
CloseLeads and contacts are created or updated through the importer with spreadsheet columns mapped to fields, and a connected email account logs sent mail and replies involving contacts in Close.Source: Importing Leads and Contacts from a file, Close Help
KylonAn agent reads the mailbox, the calendar and the thread you granted it, then writes the contact, the company and the stage change as a proposed change you can see before it lands.
What the assistant does
CloseLead summaries condense recent activity and record details. A notetaker transcribes and summarises calls, a rewrite assistant adjusts length, simplicity and tone of selected email text, and Chloe answers questions and can draft email, create tasks or update records.Source: Chat, Close Help
KylonAn agent answers with the work attached: the record changes it proposes, the view it built and the email it drafted, each with the message it came from.
Who approves what it does
CloseChloe shows an approval prompt before it takes an action, and the user confirms or cancels. A workflow email step either sends automatically or creates a draft the assigned user has to send.Source: Workflow Steps, Close Help
KylonApproval is the shape of every run, and it happens in the team's thread rather than one person's chat. A single approve control covers the records, the view and the draft together.
Reaching email and calendar
CloseA Google or Microsoft account is connected in settings, or another provider through SMTP and IMAP. Email syncs when the other address belongs to a contact, and Google or Office 365 calendars bring the associated meetings onto the lead page and the inbox sidebar.Source: Email configuration, Close Help
KylonThe mailbox and calendar are workspace connections the agent reads directly, including the threads that never mention a CRM contact, and outbound email comes back as a draft card in the thread.
What setting up automation takes
CloseA workflow starts as a draft and needs a name, one trigger and at least one step before it is activated. Triggers can be manual or based on lead, contact, opportunity, custom activity, call, meeting or form events, and steps include email, call, SMS, assignment, tasks, opportunities, record updates and filters.Source: Workflows, Close Help
KylonYou describe the outcome in the room. If it should repeat, the same request is saved as a scheduled or event driven run, and its output stays in the room.

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. Being the calling and sequencing console an outbound team lives in is a different job, and Kylon is not that tool.

Questions people ask

Do we have to leave Close?
No. Connect the account to the room and the agent reads and writes through it, so the leads stay where your team already works.
Chloe already asks before acting. What is different?
Where it lands. The proposal arrives in the team's room next to the discussion that prompted it, and one approval covers the records and the draft together.
What about the threads that are not linked to a contact?
The agent reads the mailbox you connected, so a thread that never became a CRM contact is still part of what it reads before it writes.

Keep reading

The call is one source. The thread is the rest.

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