The three tiers, at a glance
What runs with zero setup?
Only two things in Klipy are genuinely automatic, with no toggle anywhere: instant recall and the one-time backfill that fires when you first connect an inbox. Instant recall is a read surface, not a triggered job — it searches whatever Klipy has already captured for your workspace the moment there’s anything to search. It has no setting because nothing switches it on or off; you just ask it a question. What it can find still depends on tier B having produced something to find, so a freshly connected inbox with every delegation off will search a much thinner index than one that’s been running a while. The one-time backfill is different: it’s a real job, but it fires once, off the connect action itself, not off any delegation toggle. The moment you connect an email account, Klipy pulls up to 500 recent email threads, creates the interaction, contact, and company records from them, and runs a single deal-discovery pass over what it finds — all before you’ve turned on a single delegation. After that first pass, ongoing capture of new mail is a different code path, and it is gated by the Triage & log emails delegation described below. Neither of these two is a claim that capture keeps running on its own indefinitely — see How does Klipy read my conversations? for what actually keeps running after that first connection, and which switch controls it.What turns on with a connected channel?
Everything else people usually picture as “Klipy quietly working in the background” — reading new email and messages, keeping contacts and companies current, building the interaction timeline, and surfacing most suggestions — isn’t a separate always-on process. It’s the output of six built-in delegations, each visible and switchable at app.klipy.ai/delegation:
Think of this tier as the sales manager and SDR you don’t otherwise have: it’s the layer of Klipy that keeps your pipeline current while you’re the one actually talking to buyers. Turn any one of these off, and the specific slice of work it produces — email triage, message logging, meeting notes — stops with it; nothing underneath keeps running independently. Each delegation shows its own status badge — Enabled, Needs Configuration, or Disabled — so you always know which ones are actually doing something for you right now, not just which ones exist.
Beyond the six built-in delegations, you can also build a custom one from scratch: pick a trigger (an event on a CRM record, or a schedule) and describe in plain language what you want Klipy to watch for and do. A custom delegation follows the exact same rules as a built-in one — it’s visible on the same page, it can be paused, and anything it would send still waits for your approval. See How delegations work for status badges, pausing a delegation, and walking through building a custom one of your own.
What always waits on my approval?
No matter which tier produced it, two things never happen without you saying yes first. Klipy never sends an email, a LinkedIn message, a WhatsApp message, or a Telegram message on your behalf — every outbound message is a draft until you approve that exact wording. And by default, a delegation running in Suggestion mode routes its CRM writes — a new deal, a stage change, a new contact — into your suggestion queue instead of applying them directly, so you confirm before anything on a record changes. The one exception is Auto mode, a per-delegation setting you turn on yourself: with it on, that delegation’s CRM writes apply directly, with no suggestion step in between. It’s never the default, and it never touches whether Klipy can send a message on your behalf — sending stays approval-gated no matter what mode a delegation is in. Even Klipy’s own chat interface, Hey Klipy, follows this same rule for anything it would change in your CRM: it always shows you an approval card first, regardless of any delegation’s mode setting. See What does Klipy suggest, and when? for the full breakdown of Suggestion mode versus Auto mode, and every type of CRM suggestion Klipy can surface.Where to go for more detail
Reading your conversations
Which delegation reads which channel, and what’s captured versus never stored.
Your CRM filling itself in
How contacts, companies, and deals show up without manual entry.
Suggestions Klipy surfaces
The real suggestion types, what triggers each one, and Suggestion vs. Auto mode.
How delegations work
Status badges, pausing a delegation, and building a custom one.
Is reading my email really automatic, with no toggle?
Is reading my email really automatic, with no toggle?
Only the one-time backfill when you first connect an inbox is toggle-free. Ongoing capture of new email, after that first pass, runs through the Triage & log emails delegation — turn it off and new mail stops being read into Klipy.
What's the difference between tier A and a built-in delegation?
What's the difference between tier A and a built-in delegation?
Tier A (instant recall, the one-time backfill) has no on/off switch anywhere — it isn’t tied to a delegation at all. A built-in delegation is also automatic once it’s on, but it has its own page under app.klipy.ai/delegation where you can see its status and turn it off.
Will Klipy ever send a message or change my CRM without asking me first?
Will Klipy ever send a message or change my CRM without asking me first?
Sending is never automatic — every outbound message is a draft you approve. CRM writes follow the delegation’s own setting: Suggestion mode (the default) asks first, Auto mode — a setting you turn on yourself, per delegation — applies changes directly instead.
Where do I turn off a built-in delegation I don't want running?
Where do I turn off a built-in delegation I don't want running?
Each of the six built-in delegations has its own page under app.klipy.ai/delegation, where you can see its status and turn it off. Tier A (instant recall, the backfill) has no equivalent switch — there’s nothing to turn off.