---
title: "Team Email Collaboration With AI Agents | Kylon"
description: "Customer and vendor email, worked on together. The agent reads the thread and the account, drafts the reply in the room your team uses, and a person sends it."
url: "https://kylon.io/solutions/email-collaboration"
language: "en"
---

Email collaboration

# Customer and vendor email, written together.

The email lands in the room your team already works in. The agent reads the thread, the account and the files it touches, drafts the reply there, and says what it read. Teammates add what they know, and a person sends it. Nothing leaves the mailbox until someone does.

[Get started](https://app.kylon.io/sign-up)

[See a reply come together](https://kylon.io/solutions/email-collaboration#solution-scene)

The product, running

## Six emails in, four drafts ready, one person on Send

Someone asks in the support room. The agent reads the inbox, the billing thread and each account, drafts the replies it can stand behind and names the ones that need a person. Every draft waits in the room until someone sends it.

![Kylon](https://kylon.io/v2/kylon-logo-square.svg)MI

Inbox

Harbor & Pine

We were charged twice in March

Juniper Hall

Can we move to annual billing?

Bluegate Travel

Invoice address needs updating

**support**Chat6 members

MI

**Mira**9:14 AM

@Saul draft replies to this morning's billing emails. Use the plan sheet and each account, not memory.

![Saul](https://kylon.io/v2/hero/agent.svg)

**Saul**Support agent9:14 AM

Read six emails, the #billing thread and each account. Four replies are ready. Two need someone who owns the account, and I have said why.

support@ inbox, 6 emailsAccounts, 6 recordsPlan sheet#billing thread

This morning's billing emailIllustrative figures

4

Drafts ready

2

Need an owner

0

Sent without a person

Waiting in the roomEach row opens the email and the account it came from.

FromAboutStatus

Harbor & Pine

Charged twice in March

Draft

Juniper Hall

Annual billing

Draft

Bluegate Travel

Invoice address

Draft

Lark Supply Co.

Contract renewal

Owner

Re: Charged twice in MarchDraftTo finance@harborpine.example · from support@

Ready to send to Harbor & Pine

Nina added the refund date. The draft stays here until someone sends it.

Message support

The Kylon interface. Companies, people and figures are invented.

## Three kinds of email teams hand an agent first

Each one starts in the room that owns the relationship. When it should repeat, the same request runs as a workflow on new email or on a schedule, and every run keeps its history.

01

### A customer question to a reviewed reply

A customer writes to support@. The agent reads the email, the account and earlier conversations, and drafts the answer in the support room. Anyone who knows the customer adds a line before it goes.

A person sends it from support@.

02

### A vendor invoice to a checked response

An invoice or a contract change arrives. The agent checks it against the agreement and the last payment, says what does not match, and drafts the reply in the finance room.

Finance reads the draft and sends it, or does not.

03

### Threads waiting on someone else

A scheduled run finds conversations that have waited on the other side for a week, reads where each one stopped, and drafts a follow-up that picks up from there.

Each follow-up waits as a draft until its owner sends it.

Before an email leaves

## The agent drafts. A person sends.

Email is the one place a mistake cannot be taken back, so every outbound message waits for a person. What the agent can read and where it can draft are settings in the workspace, not lines in a prompt.

| The decision | What you set | Where you see it |
| --- | --- | --- |
| Which mailboxes it can read | The Gmail or Outlook accounts your team connects, shared with the rooms that need them | The agent lists the emails and records it read under its reply |
| What it prepares on its own | Reading, summarising, drafting replies and the note on the account | The draft sits in the thread next to the email it answers |
| What waits for a person | Every outbound email from a connected Gmail or Outlook account | A draft with a Send button that only a person can press |
| How you stop it | Take the room's access to the mailbox back, or pause the workflow | Drafts already written stay unsent |

| The email | Today | In the room |
| --- | --- | --- |
| Who sees it | Whoever's inbox it reached, and anyone they forward it to. | The team that owns it, in the room where that work is already discussed. |
| Getting the context | Search the CRM, the old threads and chat before writing a word. | The agent reads the thread, the account and the files first, and lists what it read. |
| Writing the reply | A draft in a doc or a cc chain, copied into the mail client at the end. | The draft is written in the room, and teammates edit it in place. |
| Sending it | Whoever has the mailbox open presses Send. | A person sends it from the connected mailbox. Outbound email waits as a draft until then. |
| Afterwards | The decision lives in one person's sent folder. | The reply, who sent it and the discussion around it stay in the room's thread. |

## What the agent reads before it drafts

The email and its thread, earlier conversations with the same contact, the records and files your team keeps about them, and the room where the work is discussed, inside the permissions you set. The reply waits as a draft in that room until a person sends 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 we run our own support and vendor email

This is how our own support and vendor email works. A customer question or a vendor invoice lands in the room that owns it. An agent reads the thread and the records and drafts the answer. Whoever knows the account adds what the agent could not know, and one person sends it. The thread keeps the decision, so the next person does not have to ask what was agreed.

## How it works

1.  01
    
    Connect the team mailbox, Gmail or Outlook, and share it with the room that owns the work.
    
2.  02
    
    Ask in the room for a reply, or let a workflow draft the routine ones as email arrives.
    
3.  03
    
    The agent reads the thread and the account and drafts the reply where the team can see it.
    
4.  04
    
    Teammates edit the draft in place, and a person sends it.
    
5.  05
    
    The reply and the discussion around it stay in the room for the next person.
    

## Questions people ask

### Can the agent send email on its own?

No. Outbound email from a connected Gmail or Outlook account is held as a draft until a person sends it.

### Do we have to move to a new inbox?

No. Mail stays in Gmail or Outlook. Kylon reads it through the connection your team sets up and sends through the same account.

### Can several people work on the same reply?

Yes. The draft lives in the room, so anyone in it can edit or comment before it is sent.

### Which mailbox does the team share?

The one you connect, for example support@ or billing@. You decide which rooms can use it, and you can take that access back at any time.

### Can it draft follow-ups on a schedule?

Yes. A workflow can run on new email or on a schedule and draft the replies. Each draft still waits for a person to send it.

### Keep reading

-   [Email operations use cases](https://kylon.io/use-cases/topics/email-operations)
-   [AI workflow automation](https://kylon.io/solutions/ai-workflow-automation)
-   [CRM workflow automation](https://kylon.io/solutions/crm-workflow-automation)
-   [AI agent governance](https://kylon.io/solutions/ai-agent-governance)

## The reply your team would write, sent by the person who should send it.

Connect the mailbox, let the agent draft in the room, and keep a person on Send.

[Get started](https://app.kylon.io/sign-up)
