> ## 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. # What does Klipy suggest, and when? > Klipy surfaces to-dos, new and moving deals, and CRM updates as suggestions you approve — see every type, what triggers it, and Suggestion vs. Auto mode. Klipy surfaces suggestions — proposed to-dos, new deals, deal-stage moves, and CRM updates — whenever a delegation, a meeting, or a qualification pass spots something worth acting on. Suggestions sit in one queue, separate from message drafts. In Suggestion mode, the default, you approve each one; in Auto mode, a setting you choose per delegation, CRM writes apply directly instead. ## What types of suggestions does Klipy surface? A suggestion is always a proposed change to a to-do or a CRM record — never an outbound message, which is a draft instead. These are the types Klipy actually surfaces today: | Suggestion | What it proposes | | ------------------------------------- | --------------------------------------------------------------------------- | | `create_todo` | A new to-do — title, urgency, person, and due date | | `update_todo` | A field change on an existing to-do | | `mark_todo_done` / `reopen_todo` | Marks a to-do done, or reopens one already marked done | | `delegate_todo` | Reassigns a to-do | | `create_deal` | Opens a new deal — pipeline, contact or company, estimated value | | `update_deal` | A field patch, or a qualification-criterion update with supporting evidence | | `set_deal_stage` | Moves an existing deal to a different pipeline stage | | `create_contact` / `update_contact` | Adds or edits a person record | | `create_company` / `update_company` | Adds or edits a company record | | `create_pipeline` / `update_pipeline` | Adds or edits a pipeline | One type you won't see is a suggestion to attach a note to an existing interaction. It's reserved in Klipy for future use but nothing produces it today — don't expect it to show up. Todo suggestions and CRM-record suggestions can come from any Suggestion-mode delegation you have running, built-in or custom. Deal suggestions are the richest of the group, since more than one part of Klipy can propose one, and stage-change suggestions are the narrowest, since only a delegation ever produces one — both are covered in more detail below. The legacy names some earlier suggestions carried — `create_reminder`, `update_reminder`, `update_task`, `mark_reminder_done` — are normalized to the current to-do types automatically wherever they still exist; you won't see the old names in your queue today, only the current ones listed above. ## Where does each suggestion come from? Most suggestion types can come from any delegation — built-in or custom — running in Suggestion mode: whenever it calls a tool that would create a to-do, open a deal, or edit a CRM record, that write is routed to your suggestion queue instead of applied directly. Deal suggestions specifically have more than one source. `create_deal` can come from a delegation's own judgment that a conversation shows a real, untracked opportunity, or from a deterministic qualification check that runs right after Klipy processes an email, message, or meeting — confirmed criteria plus no existing open deal is enough to propose one. The one-time backfill that runs on first inbox connect also runs its own deal-discovery pass, independent of any delegation. `set_deal_stage` is the narrowest type: **it only ever comes from a delegation running in Suggestion mode.** Nothing in the reading or CRM-fill pipeline moves a deal to a new stage on its own — a stage-change suggestion means a delegation (built-in or custom) specifically called for it. ## Suggestion mode vs. Auto mode Every delegation has one of two settings for its record updates. **Suggestion mode** is the default: any CRM write the delegation would make — creating a deal, updating a contact, moving a stage — lands in your suggestion queue instead of being applied, so nothing changes on a record until you say yes. **Auto mode** is a setting you turn on yourself, per delegation. With it on, that delegation's CRM writes apply directly, with no suggestion step. It's never the default and has to be switched on deliberately for each delegation you want it for — turning it on for one delegation doesn't affect any other, so you can run some delegations hands-off and keep others on Suggestion mode at the same time. Either way, this setting only governs CRM writes; it has no effect on sending, which always stays a draft you approve regardless of mode. Hey Klipy, the chat interface, is a separate case entirely — its own CRM writes always require an in-chat approval, no matter what mode any of your delegations happen to be running in. ## How do I act on a suggestion? Every suggestion in your queue can be approved or rejected. The button label matches the type: **Create** for the four `create_*` types, **Apply** for field updates and `set_deal_stage`, and dedicated to-do actions (mark done, reopen, reassign) for the to-do lifecycle types. Approving applies the change immediately — the deal opens, the field updates, the stage moves — exactly as shown in the suggestion. Rejecting discards it without touching the underlying record at all. Every suggestion also links back to the conversation, meeting, or delegation run that produced it, so you can read the context before deciding rather than approving blind. Nothing about acting on a suggestion sends a message to anyone outside your workspace — that's a separate step, gated by the drafts queue instead. A `create_deal` suggestion also carries the qualification snapshot behind it when one exists, so you can see exactly which criteria were confirmed and from which conversation, rather than approving a new deal on faith. ## When to contact us If a suggestion you expected — for example, a `create_deal` after a clearly qualifying conversation — never appears, check first whether the delegation that should have produced it is enabled and not stuck on **Needs Configuration**. If the delegation looks healthy and a suggestion still doesn't show up, reach out through the **Get help** option in Klipy's Help menu with which conversation and delegation you expected it from. It's also worth double-checking the delegation's record-update setting: if it's already in Auto mode, the write you were expecting to see as a suggestion may have already been applied directly to the record instead of landing in the queue. That's expected behavior for Auto mode, not a missing suggestion. If a suggestion appears but the details in it look wrong — the wrong contact attached to a deal, or a stage that doesn't match what was actually discussed — reject it rather than approving and fixing it after the fact, then let us know which conversation it came from so the team can look at why the underlying read was off. No. That suggestion type is reserved for future use in Klipy but nothing produces it today — don't expect to see it. A suggestion proposes a change to a to-do or a CRM record. A draft is an outbound message — an email, LinkedIn message, WhatsApp message, or Telegram message — waiting for your approval before it sends. They're two separate queues. No. set\_deal\_stage only ever comes from a delegation running in Suggestion mode. It isn't part of the passive reading-and-CRM-fill pipeline the way a create\_deal suggestion can be. That delegation's CRM writes apply directly instead of landing in your suggestion queue. It's a setting you choose per delegation and it never affects whether Klipy can send a message — sending always stays a draft you approve. Suggestions surface in your suggestion queue in Klipy, alongside a link back to the conversation or delegation run that produced each one.