> ## Documentation Index > Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # How does Klipy read my conversations? > Email, LinkedIn, WhatsApp, Telegram, and meetings are read into structured intelligence by three delegations you can see and turn off individually. Klipy reads email, LinkedIn, WhatsApp, and Telegram messages, plus meetings, into structured intelligence — not a copy of the conversation — through three delegations: Triage & log emails, Triage & log messages, and Take meeting notes. Turn one off and that channel stops being read; only the one-time backfill on first connect works without any delegation running. ## Which delegation reads which channel? There's no single "capture" process running underneath everything. Each channel has its own delegation, and reading that channel stops the moment its delegation is off: | Channel | Delegation | Route | | ------------------------------------- | --------------------- | -------------------------------------------------------------------------------- | | Email (sent and received) | Triage & log emails | [app.klipy.ai/delegation/emails](https://app.klipy.ai/delegation/emails) | | LinkedIn, WhatsApp, Telegram messages | Triage & log messages | [app.klipy.ai/delegation/messengers](https://app.klipy.ai/delegation/messengers) | | Meetings | Take meeting notes | [app.klipy.ai/delegation/notetaker](https://app.klipy.ai/delegation/notetaker) | Disable Triage & log emails, for instance, and Klipy stops turning new email into interactions, contact updates, and suggestions for that account — the same is true for messages and meetings under their own delegations. Nothing else picks up the slack; this is the actual switch, not a setting buried somewhere else. The one exception is the first time you connect an inbox: Klipy runs a one-time backfill, pulling up to 500 recent email threads and creating the interactions, contacts, and companies from them, without needing Triage & log emails to be on yet. See [What does Klipy do in the background?](/docs/guides/background/overview) for how that backfill fits alongside the rest of tier A. Each of the three delegations has its own status badge — Enabled, Needs Configuration, or Disabled — visible on its page under [app.klipy.ai/delegation](https://app.klipy.ai/delegation). Checking that badge is the fastest way to confirm whether a channel is actually being read right now, rather than assuming it is because you connected the account at some point. ## What does Klipy actually store from a conversation? For a message that passes Klipy's filter, it stores a structured summary — not the raw text. That includes a short business-focused summary, the conversation type (cold outreach, follow-up, proposal, objection handling, and so on), sentiment, the sender's main intent in one sentence, open concerns, unanswered questions, and buying signals like timelines or budget hints. For meetings, Take meeting notes joins the call, captures audio, and produces a transcript with speaker labels, a summary, and action items. Messaging channels (LinkedIn, WhatsApp, Telegram) are stored as interaction records that surface in Unibox in real time. On first connect, Klipy pulls in recent history so you aren't starting from zero — roughly the last 30 days for LinkedIn and the last 14 days for WhatsApp. That structured record, not the raw message thread, is what feeds instant recall, suggestions, and everything else downstream. Two people reading the same email would describe roughly what Klipy stores for it — a summary of what mattered, not a transcript of every line. ## What does Klipy never store? Full email bodies, attachment contents (filenames and types may be noted, not the text inside), private or blocked calendar events, anything on a channel you haven't connected, and routine internal team mail that was never forwarded into an external conversation. This holds regardless of which delegation is on — Klipy never expands its capture to cover more than these limits. Marketing and bulk mail, tool notifications, billing receipts, unsolicited cold email sent to you, and machine-generated calendar responses are also filtered out before they ever reach a delegation, so they don't turn into interactions, contact updates, or suggestions either. The filter runs the same way whether the message came in through the one-time backfill or through an active delegation. None of this is configurable per user today — the filter and the storage limits are the same for every workspace. If a conversation you'd expect to see missing from Klipy turns out to be one of the excluded types above, that's expected behavior rather than a gap in a specific delegation. ## When to contact us If Triage & log emails, Triage & log messages, or Take meeting notes shows **Enabled** but new conversations on that channel don't seem to be turning into interactions or contact updates, reach out through the **Get help** option in Klipy's Help menu. Mention which channel and which delegation, so the team can check the connection behind it. It's also worth checking the delegation's own status first: a channel stuck on **Needs Configuration** usually means the account it needs isn't connected yet, which looks similar to a channel that's silently not reading anything. Confirming the account connection before reaching out often resolves the issue faster than waiting on a reply. The same applies if a specific message you'd expect to see is missing — check whether it looks like one of the excluded types (marketing mail, a tool notification, an automated calendar response) before assuming it's a bug. If it clearly isn't one of those and the channel's delegation is enabled, that's the detail worth including when you contact us. No, for ongoing capture. Each channel is read by its own delegation — Triage & log emails, Triage & log messages, or Take meeting notes — and that delegation has to be on. Only the one-time backfill on first connect runs without a delegation. The backfill runs once, right when you connect an inbox, and pulls up to 500 recent threads regardless of any delegation setting. Ongoing capture of new mail after that is a separate process, gated by the Triage & log emails delegation. No. Klipy stores a structured summary — summary, conversation type, sentiment, main intent, open concerns, questions, and buying signals — not the raw email body. Attachment contents aren't ingested either, though filenames and types may be noted. Nothing. Klipy only reads channels you've explicitly connected — there's no data from LinkedIn, WhatsApp, Telegram, email, or meetings you haven't linked. No. Turning off a delegation stops new conversations from being read; it doesn't remove interactions, contacts, or companies that were already created while it was on.