Kylon for tl;dv users
tl;dv already recorded it. Kylon does the part nobody gets to.
We use tl;dv for our own meetings. This page describes what we built on top of it, and what you get when you connect yours.
What Kylon reads from tl;dv
- Your meeting list: name, date, length, organiser, who was invited
- The full transcript, with speakers and timestamps
- The highlights and notes tl;dv generates, available once the transcript finishes
- The recording file itself, when it is needed
- Recordings imported from outside tl;dv
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 use it ourselves
Our own meetings are recorded in tl;dv. When a call ends, we do not re-read the transcript. An agent does, and comes back with the pieces that need a decision: what changed, what someone committed to, what needs to be written down. We review it and it is done. This page is that, connected to your account instead of ours.
How it works
- 01
Connect tl;dv to Kylon. Keep recording the way you already do.
- 02
Say what should happen after a call, once, in plain language.
- 03
An agent does it and hands the result back for review.
What Kylon does not do
Kylon does not record or transcribe. tl;dv does. Kylon picks up after the transcript exists.
Questions people ask
- Do you actually use tl;dv?
- Yes. Our own meetings run on it.
- Does Kylon replace tl;dv?
- No. It reads it.
- Does anything happen without me?
- No. Drafts come back for review.
The transcript exists. The work still does not.
Connect tl;dv, say what should happen after a call, and review the result instead of writing it.