Kylon vs Copper
Copper sits beside Gmail. Kylon reads it and writes back.
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.
01 Which one is the right answer
Not every team should pick the same one.
Copper is the right answer when
The team lives in Google Workspace and wants the CRM to appear inside Gmail, with contacts and email captured from the account they already use all day.
Kylon is the right answer when
Reading the mailbox is not enough. Someone still has to turn the thread into records and a reply, and that work should come back to the room for a person to approve.
02 Operating model
How each one works
Every statement about Copper below cites Copper's own documentation. Checked 2026-09-16.
Where the work happens
A web app holds pipelines, reports, settings and the records for leads, people, companies, opportunities, projects and tasks. A Chrome extension puts record management, tracked email and templates in a panel beside Gmail, while pipeline views stay in the web app.
Source: How to use the Chrome Extension in Gmail, Copper Support
The work happens in the room where the team already talks about the account. The request, what the agent read, and the records it produced are one thread rather than a panel and an app.
Who keeps the records current
Signing up with Gmail switches on email and file synchronisation. Contacts with no record appear as suggested contacts for a person to review and convert, and email after a person is added keeps syncing.
Source: Working with the Gmail Integration, Copper Support
An 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
Copper can generate email templates using the company domain and merge fields, and rewrite an email either for clarity, flow, formatting and tone or for grammar, structure and redundancy while keeping the original tone. Copper GPT is a read only assistant for exploring and summarising records in conversation.
Source: AI email rewriter, Copper Support
An 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
Copper tells users to review generated output before sending an email, updating a record or sharing details, and to edit drafts for accuracy, tone and next steps. Copper GPT is read only and follows the signed in user's record visibility.
Source: Using Ask Gemini with Contacts, Copper Support
The agent applies the change and asks once. The records, the view and the email draft arrive in the thread behind a single approve control, with the source next to each proposed write.
Reaching email and calendar
Gmail synchronisation starts when the account is created through Gmail, and users on other clients associate a message by copying their Copper mailbox address. Calendar events sync both ways with Google Calendar, and recognised events attach to records and appear in their activity history.
Source: Creating and syncing events to Google Calendar, Copper Support
The mailbox and calendar are workspace connections the agent reads directly, and outbound email comes back as a draft card in the thread rather than a send.
What setting up automation takes
An administrator opens the workflow automation tool, adds a rule, picks the record type, the triggering event and the conditions, then configures create or update actions, saves it, switches it on and tests it. Triggers cover record creation, creation or update, a specific field update, and a daily check.
Source: Create a Workflow Automation rule, Copper Support
You 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.
Questions people ask
- Do we have to leave Copper?
- No. Connect the account to the room and the agent reads and writes through it, so the records stay where your team already works.
- Copper already syncs Gmail. What does an agent add?
- Sync files the message next to the record. The agent reads the thread and writes what changed, then asks one person to approve the records and the reply together.
- Does anything send on its own?
- No. Email is drafted for a person to send, and anything that changes a record outside the room waits for approval.
Keep reading
Syncing the email is not the same as doing the work.
Put an agent in the room where the account is discussed, connect the mailbox and the CRM, and approve the records it writes back.