# Integrations Source: https://docs.komo.ai/integrations Connect Komo to your inbox, LinkedIn, CRM, and the rest of your revenue stack Integrations let Komo run inside your existing motion instead of replacing it. Connect your inbox once — campaigns ship from your real sender. Connect LinkedIn — Sales Nav, signals, and DMs all run under your account. Connect your CRM — Komo reads and writes the records you already trust. 100+ pre-built integrations. Custom integrations for enterprise. ## Connect these first ### Inbox (Gmail / Outlook) Powers [Campaigns](/product/campaigns) (sending), [Inbox](/product/inbox) (reply triage), [New Task](/product/new-task) (grounded answers). **Connect:** Inbox → Settings → Connect. OAuth 2.0 — no plain-text credentials. Connect multiple mailboxes per user to rotate senders. ### LinkedIn Powers [Sales Nav scrapes](/product/lists#1-linkedin-sales-nav-url), [Signal Agents](/product/signals), LinkedIn-channel [campaign steps](/product/campaigns). **Connect:** Settings → LinkedIn → Connect account. Sales Nav seat limits + safe daily-send caps automatic. Multiple accounts supported. ### Apollo (built in) Powers [People Search](/product/lists#2-people-search-powered-by-apollo). No separate connection needed. ### Salesforce / HubSpot Two-way CRM sync. Pull existing accounts/contacts/opportunities in; push enrichment, signal leads, inbox activity back. **Connect:** Settings → CRM. Field mapping is configurable per object. ### Slack Notifications for high-fit Signal Agent leads, critical inbox replies, deal-stage changes. Mention `@komo` in any channel to invoke a playbook. **Connect:** Settings → Slack → Add to workspace. ### Calendar (Google / Outlook) Powers the [pre-call brief](/product/playbooks) playbook — reads tomorrow's meetings, generates briefs for external attendees. **Connect:** Settings → Calendar. ## Other categories **Productivity & knowledge**: Notion, Google Workspace, Confluence **Meeting intelligence**: Fireflies, Granola, Zoom **Customer engagement**: Front, Intercom, Zendesk, Pipedrive **Finance**: Stripe, QuickBooks, Xero **Communication**: Microsoft Teams, Discord **Engineering**: GitHub, Jira, Linear ## Custom enterprise integrations * Internal systems (proprietary CRM/ERP, data platforms) * API-based (REST, GraphQL, webhooks) * On-premise / self-hosted (air-gapped) * Custom auth (SAML SSO, mTLS, custom OAuth) Contact [admin@komo.ai](mailto:admin@komo.ai) for your specific stack. ## Why connect everything **Eliminate tool switching.** Stop copying data between LinkedIn, Apollo, Salesforce, Outreach, Gmail, Slack. Komo orchestrates the cross-platform motion — Signal Agent → outbound draft → campaign → reply triage → CRM update — without human coordination. **Grounded answers.** With CRM + inbox + calendar + notes connected, every [`/new`](/product/new-task) answer is cited from real data, not a generic web search. **Bidirectional.** Most integrations are two-way. Komo doesn't just read — it pushes enrichment, signals, inbox activity, and campaign outcomes back. Your CRM stays the source of truth. ## Getting started Unlocks [Campaigns](/product/campaigns) and [Inbox](/product/inbox). Unlocks Sales Nav, [Signals](/product/signals), LinkedIn campaign steps. Salesforce or HubSpot — bring existing data in, keep it in sync. Notifications and pre-call brief playbooks. Run a one-step playbook that touches each integration. ## Security * **OAuth 2.0** with encrypted storage. No plain-text credentials. * **Granular permissions** — only the scopes you authorize. * **Audit trail** — every integration call logged. * **Revocable access** anytime from Komo or the connected platform. * **SOC 2 Type II**, GDPR + CCPA compliant. Encryption in transit and at rest. * **No data mining**, no training on your data, no third-party sharing. ## FAQ **How many integrations can I connect?** Unlimited. **What if an integration breaks?** Komo detects it and alerts you. Most self-resolve via OAuth refresh. **Can Komo integrate with \[tool]?** Check the integrations directory. Not listed? Request custom — common for enterprise stacks. **Do integrations slow things down?** No. Komo caches and parallelizes calls. **Can I limit what Komo accesses?** Yes — scope per integration to specific folders, channels, projects, or accounts. **On-premise?** Enterprise can deploy self-hosted or hybrid. *** Connect your inbox, LinkedIn, and CRM in under 5 minutes at [komo.ai](https://komo.ai). # MCP Server Source: https://docs.komo.ai/mcp/overview Use Komo from Claude, Cursor, Codex, and any MCP-compatible app Komo ships a hosted [MCP](https://modelcontextprotocol.io) server so your AI assistant can run your prospecting directly from chat: search 200M+ people and companies, manage your CRM, build lists, run signal agents, and launch LinkedIn + email outreach — using your existing Komo plan and credits. ## Server | | | | ------------- | ---------------------------------------------------------------------------------------------------------- | | **Endpoint** | `https://mcp.komo.ai/mcp` | | **Transport** | Streamable HTTP (stateless) | | **Auth** | Komo API key (`pk_…:sk_…`) | | **Tools** | 42, across 8 categories | | **Prompts** | `prospect`, `daily_briefing`, `campaign_review` (shown in your client's prompt picker / as slash commands) | | **Cost** | Included with your plan — actions draw from the same credit balance as the app | Step-by-step setup for Claude, Claude Code, Cursor, and Codex — or create a key and get pre-filled snippets at [app.komo.ai/connect](https://app.komo.ai/connect). ## Authentication Create an API key at [app.komo.ai/settings/api-keys](https://app.komo.ai/settings/api-keys). The key is a public/secret pair (`pk_…:sk_…`) shown once at creation. Send it any of three ways: ```text theme={null} Authorization: Bearer pk_xxx:sk_xxx # most MCP clients x-api-key: pk_xxx:sk_xxx # alternative header https://mcp.komo.ai/mcp/pk_xxx:sk_xxx # key-in-URL, for clients that can't set headers ``` Access is scoped to the workspace that owns the key. Revoking the key at any time disconnects every client using it. ## Your guardrails travel with you Every tool call goes through the same server-side enforcement as the Komo app — an AI client can never do more than your account can: * **Credits & plan.** Credit-consuming tools (search, enrichment, sends) check your balance first and fail with a clear top-up message when it's insufficient. Paid-plan gates (e.g. starting a campaign, connecting a LinkedIn seat) apply unchanged. * **LinkedIn safety caps.** Standalone sends and campaign sends draw from one shared per-seat budget: daily and weekly invitation/message limits, plus pacing between actions. When a cap or the pacing window is hit, the tool returns a retry time instead of sending. * **Review mode.** Campaigns with review mode on still hold every recipient for human approval, whichever surface enrolled them. Tools that send real outreach (`start_campaign`, `send_linkedin_invitation`, `send_linkedin_message`, `engage_linkedin_post`) are annotated as destructive and instruct the assistant to confirm with you first. In Claude, we recommend keeping these on "ask before running". ## What you can ask * *"Find 25 VPs of Sales at Series B fintech companies in New York and save them to a new list called 'Q3 fintech'."* * *"What's in my CRM for Acme Corp? Summarize recent activity before my call."* * *"Run my signal agent and tell me who engaged with competitor posts this week."* * *"Draft a 4-step LinkedIn + email campaign for the 'Q3 fintech' list — review mode on."* * *"Check my LinkedIn inbox for replies and summarize them."* * *"How many credits do I have left?"* ## For agents A machine-readable overview lives at [`https://api.komo.ai/llms.txt`](https://api.komo.ai/llms.txt), and the public REST surface (the same endpoints the MCP tools wrap) is described by [`https://api.komo.ai/api/public-openapi.json`](https://api.komo.ai/api/public-openapi.json). # REST API Source: https://docs.komo.ai/mcp/rest-api Headless access to the same surface the MCP tools wrap Everything the Komo app does is backed by a REST API at `https://api.komo.ai/api`, and your API key works on all of it — the MCP tools are a curated wrapper over this surface. ## Authentication Create a key at [app.komo.ai/settings/api-keys](https://app.komo.ai/settings/api-keys). Two equivalent header forms: ```bash theme={null} curl -H "x-api-key: pk_xxx:sk_xxx" https://api.komo.ai/api/usage/summary curl -H "Authorization: Bearer pk_xxx:sk_xxx" https://api.komo.ai/api/usage/summary ``` Every response carries `X-API-Version: 1`. ## Discovering endpoints * **Public OpenAPI subset**: [`https://api.komo.ai/api/public-openapi.json`](https://api.komo.ai/api/public-openapi.json) — the curated public surface (CRM, search, lists, campaigns, LinkedIn actions, inbox connection, usage). * **llms.txt**: [`https://api.komo.ai/llms.txt`](https://api.komo.ai/llms.txt) — agent-oriented summary of the API + MCP server. ## Python SDK ```python theme={null} import komo client = komo.Komo(api_key="pk_xxx:sk_xxx") ``` The `komo` package (beta) currently wraps agents and threads; use the REST endpoints directly for CRM/campaign/LinkedIn operations. ## Errors & limits | Status | Meaning | | ------ | ---------------------------------------------------------------------- | | `401` | Key missing, malformed, revoked, or expired | | `402` | Insufficient credits or plan gate (body includes the reason) | | `409` | Conflict — e.g. LinkedIn seat not connected (`LINKEDIN_NOT_CONNECTED`) | | `422` | Validation error (body lists the offending fields) | | `429` | Rate limit or LinkedIn safety cap — honor `Retry-After` | Per-key rate limits: **120 requests/min** overall, **20/min** on expensive search/enrichment routes. Credit-consuming endpoints reserve credits before running and refund on failure. ## Staging The same API and MCP server run on Trybase staging: `https://api.trybase.ai/api` and `https://api.trybase.ai/mcp`. # Set up your client Source: https://docs.komo.ai/mcp/setup Connect Claude, Claude Code, Cursor, Codex, or any MCP app to Komo The fastest path is [app.komo.ai/connect](https://app.komo.ai/connect) — it creates a key and renders every snippet below with your real key filled in. All clients need two things: the server URL `https://mcp.komo.ai/mcp` and an API key from [app.komo.ai/settings/api-keys](https://app.komo.ai/settings/api-keys). Replace `YOUR_API_KEY` below with the full `pk_…:sk_…` pair. Claude's connector UI can't set custom headers, so the key goes in the URL path: 1. Open **Settings → Connectors → Add custom connector** 2. Name: `Komo` 3. URL: `https://mcp.komo.ai/mcp/YOUR_API_KEY` 4. Click **Add** — no restart needed Ask *"What can Komo do?"* to confirm the connection. ```bash theme={null} claude mcp add --transport http komo https://mcp.komo.ai/mcp \ --header "Authorization: Bearer YOUR_API_KEY" ``` Verify with `/mcp` inside a session. Add to `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project): ```json theme={null} { "mcpServers": { "komo": { "url": "https://mcp.komo.ai/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } } ``` Add to `~/.codex/config.toml`: ```toml theme={null} [mcp_servers.komo] url = "https://mcp.komo.ai/mcp" http_headers = { "Authorization" = "Bearer YOUR_API_KEY" } ``` Any client that supports remote MCP servers over **Streamable HTTP** works: * URL: `https://mcp.komo.ai/mcp` * Auth: `Authorization: Bearer YOUR_API_KEY` or `x-api-key: YOUR_API_KEY` * Header-less clients: `https://mcp.komo.ai/mcp/YOUR_API_KEY` ## Optional: the Komo prospecting skill For noticeably better results in Claude, add the **komo-prospecting skill** — a workflow guide that teaches Claude Komo etiquette (qualify the ICP before spending credits, always save results to lists, never send without showing you the message first). Download the zip from [app.komo.ai/connect](https://app.komo.ai/connect) and upload it at claude.ai → **Settings → Capabilities → Skills** (or drop the folder into `~/.claude/skills/` for Claude Code). The MCP server works fine without it. ## Connecting LinkedIn and email from chat Sending tools need a connected LinkedIn seat or email inbox. You can start either connection from chat — the tool returns a secure browser URL: 1. Ask: *"Connect my LinkedIn account."* 2. The assistant calls `connect_linkedin_account` and gives you a hosted sign-in link — your credentials go to LinkedIn's flow, never through the chat. 3. Finish in the browser, then ask the assistant to verify with `list_linkedin_accounts`. Email works the same way via `connect_email_account` (Gmail / Outlook OAuth). ## Troubleshooting | Symptom | Fix | | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "API key invalid or revoked" | Create a new key at [settings/api-keys](https://app.komo.ai/settings/api-keys) and update your client config. | | "Payment required" on a tool | Your credit balance can't cover the action — top up at [settings/billing](https://app.komo.ai/settings/billing). | | "Rate/safety limit hit" on LinkedIn sends | The seat's daily/weekly cap or pacing window is active; the message includes when to retry. Limits are adjustable per seat at [settings/linkedin](https://app.komo.ai/settings/linkedin). | | Client can't connect at all | Confirm the URL is exactly `https://mcp.komo.ai/mcp` and your client supports Streamable HTTP (SSE-only clients are not supported). | # Tool reference Source: https://docs.komo.ai/mcp/tools All 42 Komo MCP tools, with credit costs and safety notes Legend: **💳 credits** = draws from your credit balance · **✉️ sends** = contacts real people (the assistant is instructed to confirm with you first) · unmarked read/write tools are free. ## Usage | Tool | What it does | | ------------------- | -------------------------------------------------------- | | `get_usage_summary` | Credit balance, plan tier, and usage against tier limits | ## CRM records Accounts (companies) and contacts (people) share one tool set via a `record_type` parameter. | Tool | What it does | | ------------------------- | --------------------------------------------------- | | `list_crm_records` | List accounts or contacts, with free-text search | | `get_crm_record` | One record with all fields | | `create_crm_record` | Create an account or contact | | `update_crm_record` | Partial update of a record | | `enrich_crm_record` 💳 | Enrich with external data (\~20 credits) | | `get_crm_record_activity` | Activity timeline (emails, LinkedIn touches, notes) | ## Find people & companies | Tool | What it does | | ------------------------------ | -------------------------------------------------------------------------------- | | `search_people` 💳 | B2B database search by title/seniority/location/company (\~5 credits per result) | | `import_sales_nav_search` 💳 | Import a LinkedIn Sales Navigator search URL into a list (\~5 credits per lead) | | `find_prospects_with_ai` 💳 | AI web research against plain-English match criteria (\~10 credits per match) | | `save_findall_results_as_list` | Persist a completed AI discovery run as a list | ## Lists | Tool | What it does | | ------------------------------- | --------------------------------------------------------------------- | | `list_lists` | All lists in the workspace | | `create_list` | New list (manual, search, or Sales Nav source) | | `get_list_contacts` | List members + fields; also the progress check for background imports | | `add_contact_to_list` | Manually add one person | | `find_email_for_list_member` 💳 | Waterfall email finder (\~5 credits) | ## Signal agents | Tool | What it does | | ------------------------- | -------------------------------------------------------------------- | | `list_signal_agents` | All signal agents | | `create_signal_agent` 💳 | AI-generated targeting config from a plain-English description | | `run_signal_agent_now` 💳 | Trigger a run (\~500 credits): scrape → ICP filter → enrich engagers | | `get_signal_agent_runs` | Latest run status per agent | ## Campaigns | Tool | What it does | | --------------------------- | ---------------------------------------------------- | | `list_campaigns` | Campaigns with status and recipient counts | | `get_campaign` | One campaign + engagement analytics | | `draft_campaign_with_ai` 💳 | Generate a draft sequence from a prompt (draft only) | | `create_campaign` | Persist a campaign in draft state | | `update_campaign` | Change settings (never status) | | `attach_lists_to_campaign` | Set recipient lists and sync members | | `get_campaign_recipients` | Per-person send status — the progress tracker | | `review_campaign_recipient` | Approve/reject one recipient in review mode | | `start_campaign` 💳 ✉️ | **Activates real outreach** (paid plan required) | | `pause_campaign` | Stop queued sends immediately | ## LinkedIn | Tool | What it does | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | `list_linkedin_accounts` | Connected seats with status and send limits | | `connect_linkedin_account` | Returns a hosted sign-in URL (browser flow) | | `send_linkedin_invitation` 💳 ✉️ | Connection request, optional note (\~20 credits) | | `send_linkedin_message` 💳 ✉️ | DM, thread reply, or InMail; optional file attachment or voice note via `attachment_url` (\~20–30 credits) | | `get_linkedin_profile` 💳 | Profile fetch; `visit=true` makes it a visible profile visit | | `search_linkedin_people` 💳 | Live LinkedIn search through the seat (classic / Sales Nav / Recruiter; \~5 credits per result, unused refunded) | | `list_linkedin_conversations` | LinkedIn inbox: chats, or one chat's messages | | `list_linkedin_network` | 1st-degree connections, or pending sent invitations (check before re-inviting) | | `list_linkedin_posts` | A person's recent posts (personalization research) | | `engage_linkedin_post` 💳 ✉️ | Comment or react as the connected seat (\~5 credits) | ## Email | Tool | What it does | | ----------------------- | ----------------------------------- | | `list_email_accounts` | Connected Gmail/Outlook senders | | `connect_email_account` | Returns an OAuth URL (browser flow) | ## Coverage notes The MCP surface is a curated subset designed to stay within AI-client context limits and exclude destructive operations. Notable capabilities that are **REST-only today** (same API key works — see [REST API](/mcp/rest-api)): * CRM notes/tasks/meetings/files, CSV import/export, bulk enrichment, custom columns * Campaign step-level editing, schedules, per-recipient force-send, deletes/archives * Inbox email reading/reply/compose * Parallel research sessions, Komo web research, AI Worker (agent) runs * LinkedIn seat disconnect Deletion tools are intentionally absent from MCP v1. ## Security model Every LinkedIn tool takes a `linkedin_account_id` that must be a seat **owned by the workspace behind your API key** — the server resolves it against your account before any Unipile call, and chat-level operations additionally verify the conversation belongs to that seat. Komo's Unipile credentials never leave the server, and no tool can act through another customer's seat. # Accounts Source: https://docs.komo.ai/product/accounts Companies in your CRM — researched and ready to work The **Accounts** page is the company side of your CRM. Every row is an organization; every column is a data point Komo can research and cite. Click an empty cell → Komo fills it in with sources. ## Standard fields | Field | What it is | | ---------------- | ---------------------------- | | Account | Name + logo | | Industry | Auto-detected (chips) | | Last interaction | Last touch in your workspace | | Revenue | Range (e.g. $10M–$50M) | | Headcount | Employee range | | Last funding | Stage, amount, date | | LinkedIn | Company handle | | Website | Primary domain | Hide any column. Add as many custom columns as you need. ## Adding accounts Accounts come from four places: * **Manual** — type a name + domain * **From a list** — Sales Nav, CSV, or Find with AI auto-creates accounts * **From a Signal Agent** — the engager's company becomes an account * **From an inbound reply** — a new sending domain creates a stub account ## Custom columns Anything you'd research by hand becomes a column. Examples: * "Are they hiring SDRs?" * "Tech stack" (cited from BuiltWith / job posts) * "Recent leadership posts about cold email?" * "Renewal date" (pulled from inbox) * "Buying committee" ### Add a column Click **+ Add column**. Two options: * **Manual** — name + description of what to research * **AI-suggested** — give Komo a goal ("evaluate enterprise readiness") → it proposes 5–10 columns to toggle on Once added, every row gets an **Enrich** button. Click on a cell, row, column, or the whole table — Komo runs cells in parallel. ### Cell citations Click any value to see the source panel: exact value, reasoning, and 1–4 sources with direct quotes. Manual edits are locked — Komo won't overwrite them on the next enrichment. ## Views The tab bar is **Views**. Default: `All`. Click **+ New view** to save a combination of: * Column visibility * Filters (e.g. only `SaaS`) * Sort order Use views to slice the same CRM into working surfaces — `Hot — Series B SaaS`, `Renewals Q3`, `Enterprise pilot`. ## Side panel Click an account name to open the panel: * **Summary** — AI-generated overview * **About their business** — narrative from web research * **Activity timeline** — every campaign step, inbox reply, agent action * **Fields** — every field with sources, editable inline Resize by dragging the left edge. ## Bulk actions Select rows → Add to list, Enrich, Delete, or Export CSV. ## Connected to [Contacts](/product/contacts) (belong to accounts) · [Lists](/product/lists) (source of accounts) · [Signals](/product/signals) (surface leads at accounts) · [Campaigns](/product/campaigns) (outbound to contacts at accounts) · [Inbox](/product/inbox) (replies linked back) · [New Task](/product/new-task) (the agent reads all of it) ## Tips Try AI-suggested columns first — they surface fields you'd forget to ask for. Evaluating a new ICP? Start with 50 accounts, add 8–10 columns, click **Enrich all**. \~10 minutes to a full comparison. Empty cells aren't errors — they're invitations to click **Enrich**. # Campaigns Source: https://docs.komo.ai/product/campaigns Multi-step outbound across email and LinkedIn — drafted by AI, sent by your senders A **Campaign** is a multi-step outbound sequence. Pick a [list](/product/lists), define the steps (email + LinkedIn), and Komo ships under your connected senders. Replies flow back into the [Inbox](/product/inbox). Every step is **human-reviewed before send** — Komo drafts and queues; you approve. No autonomous AI SDR blasts. ## Creating a campaign `/campaigns` → **Create campaign**. Two paths: **Create with AI** (recommended) — Describe target, offer, and goal in one sentence: ``` Reach out to GTM leaders at SaaS Series A-B that recently announced funding, position our outbound automation, target a 15-min intro call. ``` Komo drafts a 4–7 step sequence across email and LinkedIn — subject lines, body, timing, sender selection. You review every step before saving. **Create manually** — empty builder, add steps one at a time. ## Step types | Step | Channel | What it does | | ------------------------- | -------- | -------------------------------------------------- | | Send email | Email | Personalized email from a connected inbox | | Send invitation | LinkedIn | Plain connection request | | Send invitation with note | LinkedIn | Connection request + short note | | Send message | LinkedIn | DM (requires existing connection) | | Voice message | LinkedIn | Short audio DM | | Visit profile | LinkedIn | Triggers a profile-view notification (soft signal) | Add a **delay in days** between steps. Komo respects per-sender daily caps and warming. ## Connect senders * **Email** — connect Gmail/Outlook from **Inbox → Settings**. Same connection powers sending and reply triage. * **LinkedIn** — connect from **Settings → LinkedIn**. Connect multiple of each — Komo rotates to stay inside safe daily caps. ## Campaign tabs | Tab | What it does | | ----------------- | ------------------------------------------------------------------------- | | **Workflow** | The sequence. Edit, reorder, add/remove. Live metrics per step. | | **Scheduled** | Send window — days, hours, timezones, throttles. | | **Contacts** | Enrolled contacts with status (queued, sent, replied, paused, completed). | | **Last launches** | Run history — timestamps, sender used, success/error counts. | | **Insights** | Send rate, open rate, reply rate, positive-reply rate, conversion. | ## Settings Gear icon opens: * **Lists attached** — new list members auto-enroll * **Senders** — which inboxes/LinkedIn accounts can send * **Pause** — stop sending without losing state * **Archive** — close the campaign ## Sequence patterns **LinkedIn-first** (SMB / mid-market): ``` Day 0: Visit profile Day 1: Send invitation with note Day 4: Send message (if accepted) Day 9: Send email (if no LinkedIn reply) Day 14: Send message (final touch) ``` **Email-first** (enterprise): ``` Day 0: Send email (opener) Day 3: Send email (value / case study) Day 7: Send email (calendar link) Day 12: Send invitation (LinkedIn fallback) Day 14: Send message (if accepted) ``` **Signal-triggered** (from a Signal Agent — speed matters): ``` Day 0: Send invitation with note (references the triggering signal) Day 2: Send email (if no LinkedIn response) Day 5: Voice message (if accepted) ``` ## Replies Every reply lands in the [Inbox](/product/inbox). Komo: * Categorizes (Hot Lead, Interested, Meeting Request, Objection, Not Now, Unsubscribe, etc.) * Pauses the contact so they don't get the next step * Links the reply to the contact's timeline * Fires any matching [routing rule](/product/inbox#routing-rules) ## Tips **Use AI draft first, edit second.** Komo lands 80% of structure, timing, and personalization. Editing beats starting from scratch. **Keep step 1 short.** Reply rate correlates with brevity. Personalize step 2 — by then you know who opened. **Attach lists, not snapshots.** New list members (Signal Agent runs, Sales Nav refreshes) auto-enroll. Static imports don't. **Use Insights as a stop-loss.** Reply rate under 1% after 100 sends? Pause and rewrite step 1 — don't burn sender reputation. # Contacts Source: https://docs.komo.ai/product/contacts People in your CRM — researched, linked to accounts, ready to outreach The **Contacts** page is the people side of your CRM. Same enrichment model as [Accounts](/product/accounts) — but tuned for individuals and linked to a parent account. ## Standard fields | Field | What it is | | ---------------- | --------------------- | | Name | Display name + avatar | | Account | Parent account chip | | Last interaction | Last touch | | Job title | Current role | | Email address | Primary work email | | LinkedIn | Handle (clickable) | Hide any column. Add custom columns as needed. ## Adding contacts * **Manual** — type name, email, title, account, LinkedIn * **From a list** — Sales Nav, People Search, CSV, or Find with AI * **From a Signal Agent** — matched LinkedIn engagers auto-created * **From an inbound reply** — new senders auto-created with parent account ## Custom columns Examples that drive replies: * "Recent LinkedIn posts (last 30 days)" * "Personal hook — shared connection, alma mater, hometown" * "Buying authority — decision maker or champion?" * "Tenure at current company" * "Pain point hypothesis for our offer" Click **+ Add column** → type a column manually or get AI suggestions. Click **Enrich** on any cell, row, column, or whole table. Komo runs cells in parallel and cites every value. Manual edits are locked. ## Filters Three facet toggles: * **Has email** — deliverable email * **Has LinkedIn** — LinkedIn handle * **Has account** — linked to a parent Combine with **Views** to build working surfaces — `Outbound-ready` (email + account), `LinkedIn-only` (handle, no email), etc. ## Side panel Click a contact name: * **Summary** — AI brief * **Account context** — parent account * **Activity timeline** — campaign steps, inbox replies, agent actions * **Fields** — sourced, editable inline ## Bulk actions Select rows → Add to list, Enrich, or Delete. ## Connected to [Accounts](/product/accounts) (parent records) · [Lists](/product/lists) (source) · [Signals](/product/signals) (intent-driven contacts) · [Campaigns](/product/campaigns) (outbound targets) · [Inbox](/product/inbox) (reply trail) · [New Task](/product/new-task) (agent reads all of it) ## Tips Add "recent LinkedIn activity" as a column before launching a campaign — gives every outreach a personal hook. Filter to **Has email + Has account** before pushing to a campaign — those are reliably reachable. When a Signal Agent surfaces a contact, read the timeline first. The triggering signal is great opener material. # Dashboard Source: https://docs.komo.ai/product/dashboard Your sales CRM workspace at a glance The Dashboard is your workspace home — a morning-standup screen showing what's running, what's pending, and what to do next. ## What you see **1. Getting-started checklist** (new workspaces only) Four setup steps with a progress bar: 1. Connect your [inbox](/product/inbox) (Gmail / Outlook) 2. Create [accounts](/product/accounts) and [contacts](/product/contacts) 3. Build a [prospect list](/product/lists) 4. Create a [campaign](/product/campaigns) draft Disappears once complete. **2. Primary metrics** * **Accounts** — total + active count * **Contacts** — total + with email count * **Inbox Emails** — current + archived Each card links to its page. **3. Quick actions** One-click shortcuts: Build List, Add Account, Draft Campaign, Review Inbox. **4. Overview** State of your lists, campaigns, and inbox settings. Each row links through. ## Start Agent button Top-right of the Dashboard. Opens `/new` to ask Komo a question or hand off a task. See [New Task](/product/new-task). ## Tips Connect your inbox first — it unlocks both Campaigns (sending) and Inbox (replies). Dashboard is read-only. Create and edit from each dedicated tab. *** Next up: [Accounts](/product/accounts), [Contacts](/product/contacts), [Lists](/product/lists), [Signals](/product/signals), [Campaigns](/product/campaigns), [Inbox](/product/inbox). # Inbox Source: https://docs.komo.ai/product/inbox Smart, AI-categorized inbox for sales replies — route to an agent or a teammate, never miss a hot lead The **Inbox** is your sales reply hub. Connect Gmail or Outlook once — every reply is auto-categorized, linked to its contact and campaign, and (optionally) auto-routed to an agent or teammate. You stay in control. Komo drafts; you approve before send. ## Three-pane layout | Pane | What it shows | | ------------- | ----------------------------------------------------- | | **Left rail** | Accounts, categories, Archived folder | | **Middle** | Email list, filtered by category and account | | **Right** | Open thread — conversation, contact context, reply UI | Category counts update in real time. ## Connect your inbox Gear icon top-right, or `/inbox/settings`. Pick **Gmail** or **Outlook** → OAuth. Komo stores only short-lived OAuth tokens — never plain-text credentials. Many teams connect 2–3 inboxes per rep to distribute send volume and warming. Disconnect or pause any inbox from the same page. ## Eight default categories | Category | Means | Example subjects | | ----------------------- | ------------------------------------------------------------ | ---------------------------- | | **Hot Lead** | High-intent inbound, signal-triggered lead, or warm referral | "Inbound from your website" | | **Interested** | Engaging positively, wants to continue | "Tell me more about pricing" | | **Meeting Request** | Scheduling, rescheduling, confirming | "Can we meet next week?" | | **Objection** | Pricing, fit, timing, security, competitor concern | "Too expensive for us" | | **Renewal & Expansion** | Existing customer renewing or upselling | "Renewal coming up" | | **Not Now** | Pause or follow up later | "Circle back next quarter" | | **Unsubscribe** | Remove from outreach | "Stop emailing me" | | **Other** | Doesn't fit primary categories | "Quick question" | Re-classify any thread manually — Komo learns from corrections. Create **custom categories** from Inbox Settings for verticals (`legal_review`, `partner_intro`, etc.). ## Routing rules Map a category to an agent or workflow that runs automatically. Click **Add routing rule**. e.g. `Meeting Request`. **Agent** (custom or default) or **Workflow** (saved [playbook](/product/playbooks)). Live immediately. Future replies in that category trigger the agent. Drafted responses appear for you to approve, edit, or send. ### Common patterns * **Interested → reply-drafting agent** — "great, let me share more" + calendar link * **Meeting Request → scheduling agent** — propose times via Calendar availability * **Objection → objection-handler agent** — draft pricing/security/timing response * **Unsubscribe → suppression workflow** — remove from all campaigns + add to do-not-contact * **Not Now → reminder workflow** — schedule follow-up touch in X weeks * **Hot Lead → notification workflow** — Slack DM to the owning rep ## Compose Top-right **Compose** opens a new email dialog — sender, recipient, subject, body. Useful for one-off outbound outside a campaign. ## Thread view Right pane shows: * Full conversation * Linked [Contact](/product/contacts) and parent [Account](/product/accounts) * Campaign context (if it came from one) * Inline reply composer * Actions: archive, change category, mark read, link to different contact Replies go out from the original sender, preserving threading. ## Archive vs. delete * **Archive** — out of active view, keeps thread + contact link + analytics. Default for "done." * **Delete** — removes Komo's copy entirely. Use rarely. ## Connected to [Campaigns](/product/campaigns) (produce replies) · [Contacts](/product/contacts) (timeline entries) · [Signals](/product/signals) (monitored-lead replies) · [Playbooks](/product/playbooks) (triggered by routing) · [New Task](/product/new-task) (agent can answer "what objections came up this week?") ## Tips Set up routing rules for **Hot Lead, Meeting Request, Unsubscribe** before your first campaign. The others can stay manual until volume justifies automation. Use custom categories for vertical motions. Default 8 cover B2B SaaS — verticals win by extending. Re-classify misrouted threads weekly. After a few weeks, expect 95%+ accuracy on your motion. # Lists & Prospecting Source: https://docs.komo.ai/product/lists Six ways to source the right people — then turn them into pipeline A **List** is a working set of people you're sourcing or pursuing. Build a list once via one of **six paths** — Komo dedupes, enriches, and hands it off to campaigns. Click **New list** at `/lists` to start. ## The six paths Paste a Sales Nav search URL — Komo pulls up to 10 pages of leads. Search Apollo by title, location, industry, headcount. Drop a CSV with email, name, or LinkedIn URL. Add people one at a time. 24/7 [Signal Agent](/product/signals) — auto-adds matching LinkedIn engagers. Describe the buyer; AI builds a cited list with editable match criteria. *** ## 1. LinkedIn Sales Nav URL **Best for:** narrow, high-precision outbound where you've already built the Sales Nav search. **Settings → LinkedIn**. Komo scrapes under your account, respecting Sales Nav seat limits. Use Sales Navigator to filter. Copy the URL when ready. **Lists → New list → LinkedIn Sales Nav URL**: * **List name** * **Sales Nav URL** * **Pages to fetch** (1–100, default 10; \~25 leads/page) * **LinkedIn account** Leads stream in as they're found. Each row carries name, title, current company, LinkedIn URL, and (where Sales Nav surfaces it) location and headcount. Komo dedupes against existing contacts and accounts. *** ## 2. People Search (powered by Apollo) **Best for:** net-new TAM when you don't have a Sales Nav search, or filters LinkedIn doesn't expose. **Lists → New list → People Search**. Left rail: Keywords, Job Title, Person Location, Company HQ Location, Industry, headcount, seniority, department. Pick or create a list. Selected people are added to your CRM and enriched in the background. You get auto-dedup against existing CRM data and inherited AI enrichment columns. *** ## 3. Upload CSV **Best for:** warm lists from events, webinars, or any spreadsheet you already have. Minimum one of: **email**, **name**, or **LinkedIn URL** per row. Common other columns: title, company, company domain. **Lists → New list → Upload CSV** → name → drop the file. Komo dedupes against your CRM and enriches missing fields. Toast confirms imported count. Don't pre-clean your CSV. Missing emails are inferred from name + domain; missing companies from email domains. *** ## 4. Manual **Best for:** warm intros and hand-picked lists. **Lists → New list → Manual** → name it. Click **Add person**. Provide any combination of: name, email, title, company, company domain, LinkedIn URL. Any single identifier triggers background enrichment for the rest. *** ## 5. Signal Monitoring (Signal Agent) **Best for:** always-on pipeline. Mine LinkedIn engagement for in-market buyers continuously. **Lists → New list → Signal Monitoring** opens the Signal Agent creator. You define: * A name * Any combination of **five signal sources**: keywords, influencer profiles, competitor companies, your own profile, your company page * **ICP filters** — titles, locations, industries + matching mode (high precision vs. discovery) * **Caps** — daily lead, raw engager, enrichment Saved agents run twice a day and auto-add matched engagers. → Full guide: [Signal Agents](/product/signals) *** ## 6. Find with AI **Best for:** narrow ICPs you can describe in a sentence. Komo does open-web research instead of database filtering. **Lists → New list → Find with AI**. Examples: * `VP Sales at B2B SaaS companies with 50-500 employees that recently hired SDRs` * `Pre-seed founders working on developer tools, raised in the last 6 months` * `Heads of RevOps at Series B companies that went through a layoff in 2025` Click **Continue**. Komo turns your brief into structured criteria (name + description). Edit, add, or remove. Pick a result limit (default 20). Candidates stream into a table: **Generated**, **Matched** (with citations), **Unmatched** (with reasoning). Match conditions are preserved; matched candidates become contacts in your CRM. **Find with AI vs. People Search:** People Search filters a database. Find with AI reads the open web — it'll find buyers Apollo hasn't seen yet. Slower, smaller result set, higher precision. *** ## Working inside a list Each list behaves like a focused [Contacts](/product/contacts) table: * AI-enrichable custom columns (e.g. "recent LinkedIn activity," "tech stack") * Filters and views * Side panel for full contact + parent account * Bulk actions: add to campaign, enrich, delete ### List → Campaign Lists feed [Campaigns](/product/campaigns). Attach a list and every new person flowing in (via Sales Nav refresh or Signal Agent) is auto-enrolled. ## Tips **Mix sources in one list.** Sales Nav for bulk TAM + a Signal Agent attached for ongoing in-market flow. **Enrich after sourcing, not before.** Build the list, add 5–10 columns, click **Enrich all** — cells run in parallel. **Use Find with AI for narrow ICPs.** "Series B SaaS CFOs who switched ERPs" won't be in Apollo. Find with AI surfaces them with citations. # New Task — Your Sales Agent Source: https://docs.komo.ai/product/new-task Ask any question about an account or contact. Hand off any multi-step sales task. Komo runs it grounded in your CRM. The **New Task** page (`/new`) is the agent that knows your CRM. Pin an [Account](/product/accounts), ask a question, get a cited answer. Or hand off multi-step work ("research the buying committee at Acme, draft a one-page brief, email it to me by 9 AM") and let Komo run it. This is the **Research** and **Prepare** moment — between "I have a list" and "I'm on the call." No more research tax before every meeting. ## Two modes The mode selector inside the chat input: **Assistant** (`ask`) — fast, conversational answers from your CRM and the web. No sandbox. Good for: ``` What's the right contact at Acme for a security pitch? Has anyone replied positively from the SaaS Series A list this week? Draft a 3-sentence follow-up to Jane referencing her last funding round. Who at Brex engaged with my last three LinkedIn posts? ``` **Task** (`task`) — sandboxed agent run. Browses, runs code, creates files, uses any connected integration. Multi-step work. Good for: ``` Research the buying committee at Acme and draft a one-page pre-call brief. Run my "Weekly Pipeline Review" playbook against my top 20 deals. Build a competitive battlecard comparing us to Outreach and Salesloft. For each account on my list, find a recent product launch and write a 2-line opener. ``` Default is **Task**. Switch to **Assistant** for quick questions. ## Pin an account The **Account** chip below the input pins one CRM account to the conversation. When pinned: * Komo treats that account as the implicit "they" / "the customer" * All account fields, contacts, campaign history, and inbox history are pre-loaded * Citations point to your CRM, not just the web Pin for account-specific questions; leave unpinned for workspace-wide questions. ## Templates Under the chat input is the **template showcase** — one-click starter prompts. Each is a saved [playbook](/product/playbooks). Common ones: * **Pre-call brief** — buying committee, recent activity, talking points * **Account QBR** — renewal date, usage, inbox tone → one-page deck * **Competitive battlecard** — up-to-date pricing and feature evidence * **Weekly pipeline review** — score every open deal on fit, timing, recency * **Renewal risk scan** — flag churn-at-risk accounts from inbox + usage * **Signal-to-touch** — for a new [Signal Agent](/product/signals) lead, draft and queue personalized outreach Click any template to pre-fill the input; edit before sending. ## Example workflows **Pre-call prep (Assistant)** ``` Pin: Acme Corp Prompt: "What's the right opener for tomorrow's call? Reference their most recent funding round and any change-of-role on the buying committee." ``` → 2–3 sentence opener with citations. \~10 seconds. **Multi-account research (Task)** ``` Prompt: "Take the 'Q3 SaaS expansion' list. For each account, find their tech stack (focus on data warehouses) and add it as a column. Then sort by accounts using Snowflake." ``` → \~10 minutes for 50 accounts, written back to your CRM. **Inbox triage (Assistant)** ``` Prompt: "Summarize today's positive replies from the 'Outbound — Series B' campaign. Group by industry. Flag anyone who mentioned a timeline." ``` → Structured digest in seconds. ## History Every conversation is preserved at `/history`. Reopen any past run to continue or fork into a new task. Useful for re-running last week's QBR with this week's data. ## What's different from a generic chatbot 1. **Knows your CRM.** Pinning an account, referencing a contact, asking about a campaign — all resolve against your real workspace. 2. **Runs end-to-end work.** Task mode does file creation, browser, code, integrations. 3. **Cited output.** Every fact links to its CRM field, inbox thread, or web source. ## Connected to [Accounts](/product/accounts) + [Contacts](/product/contacts) (CRM grounding) · [Playbooks](/product/playbooks) (templates) · [Lists](/product/lists), [Signals](/product/signals), [Campaigns](/product/campaigns), [Inbox](/product/inbox) (all readable, most writable) · [History](#history) (every run preserved) ## Tips Pin the account when talking about a specific deal — otherwise Komo guesses which Acme you mean. Use Assistant first, then Task. Most motions start with a question ("who?") and become work ("draft the follow-up"). Switching modes mid-conversation is supported. Running the same prompt weekly? Save it as a [playbook](/product/playbooks) and put it on a [schedule](/product/schedules-triggers). # Playbooks Source: https://docs.komo.ai/product/playbooks Reusable sales motions — define once, run every week A **Playbook** is a reusable sales motion captured as an executable workflow. Define it once — pre-call prep, QBR generation, weekly pipeline review, signal-to-touch — and run it as a one-click action, a schedule, or an automatic response to a signal. Playbooks are how institutional sales knowledge compounds into the agent layer. ## How they fit the four pillars | Pillar | What playbooks do | | ------------------ | ------------------------------------------------------------------------------------- | | **Discover** | Auto-route new [Signal Agent](/product/signals) leads → personalized 2-touch sequence | | **Research** | Pre-call briefs, account QBRs, competitive battlecards | | **Prepare** | Pull buying-committee context, draft talking points | | **Close & manage** | Weekly pipeline review, renewal risk scan, inbox routing | ## Four ways to create ### 1. Agent Builder (recommended) In [New Task](/product/new-task), click **Prompt to build** in the right panel. Describe the goal in one sentence: ``` Run every Monday at 8 AM. For every open opportunity, pull the latest inbox activity, the buyer's recent LinkedIn posts, and any changes to their company page. Email me a one-page digest ranked by closest close date. ``` Komo wires up the steps, tools, and schedule. You review before saving. ### 2. Playbook Editor Notion-like editor where you write the workflow in markdown: ```markdown theme={null} ## Goal Pre-call brief for tomorrow's external meetings. ## Integrations - Google Calendar - CRM (Accounts, Contacts, Inbox) - LinkedIn ## Steps 1. Pull tomorrow's calendar events 2. Match each external attendee to a CRM account 3. Research each attendee: last 3 LinkedIn posts, last 5 inbox threads, recent funding/hiring news 4. Draft a one-page brief: who they are, what's been discussed, opener, expected objections 5. Email me by 8 AM tomorrow ``` Tools and integrations auto-suggest. Visual preview as you write. ### 3. Import existing SOPs (Enterprise) Upload Notion / Confluence / Google Docs / Word files from **Settings → Playbooks → Import**. Komo extracts the steps and proposes a draft. ### 4. Record your process Record your playbook Click **Record** and walk through the motion on your screen, narrating the *why*. Komo watches and generates the playbook. Useful for nuanced motions that resist being typed out. ## Sales-specific examples ### Pre-call brief ``` Trigger: Any calendar event in next 24h with an external attendee. Steps: 1. Match attendee's company to a CRM account 2. Pull standard fields + last 5 inbox threads + campaign activity 3. Research attendee on LinkedIn (last 3 posts, role changes) 4. Draft one-page brief: who, what's been discussed, opener, objections 5. Email me 12h before the meeting ``` ### Account QBR ``` Trigger: Manual or scheduled (e.g. monthly per account). Steps: 1. Pull renewal date, contract value, product usage 2. Pull last 90 days of inbox + campaign activity 3. Identify wins, blockers, risk signals from inbox tone 4. Generate one-page QBR: exec summary, health, wins, risks, next steps 5. Email me Friday morning + post to account timeline ``` ### Weekly pipeline review ``` Trigger: Every Monday 8 AM. Steps: 1. Pull every open opportunity 2. Score each on fit, timing, connection 3. Surface top 10 (push) and bottom 10 (disqualify/re-engage) 4. Send digest ``` ### Signal-to-touch ``` Trigger: New lead from a Signal Agent. Steps: 1. Read signal context (which post, which engagement, why matched) 2. Pull buyer's last 3 LinkedIn posts 3. Draft 2-touch sequence (LinkedIn DM + email) referencing the signal 4. Queue in the matching campaign 5. Notify me only if fit score is unusually high ``` ### Renewal risk scan ``` Trigger: Every Monday for accounts renewing in next 90 days. Steps: 1. Pull last 60 days of inbox activity per account 2. Classify reply tone (positive, neutral, negative, silent) 3. Cross-reference with product usage trend 4. Flag declined tone or dropped usage 5. Email watchlist with renewal date, decline signal, suggested action ``` ### Competitive battlecard refresh ``` Trigger: Every 2 weeks. Steps: 1. Pull competitors from CRM 2. Scrape recent pricing, feature, positioning updates 3. Diff against last saved battlecard 4. Update with "What's changed" summary 5. Notify #enablement on Slack with the diff ``` ## Running a playbook Four invocation paths: * **One-click** from [New Task](/product/new-task) template showcase * **Schedule** — cron (see [Schedules & Triggers](/product/schedules-triggers)) * **Trigger** — external event * **Inbox routing rule** — see [Inbox routing](/product/inbox#routing-rules) ## Writing better playbooks **Be specific about inputs and outputs.** * ✅ "When email subject contains 'compliance check' followed by company name" * ❌ "When someone needs a compliance check" **Define clear success criteria.** * ✅ "Pass if no regulatory violations in 24 months AND financial ratios within ranges" * ❌ "Check if account is compliant" **Specify exception handling.** * ✅ "If renewal date is missing, flag for manual review and notify me" * ❌ "Handle missing data appropriately" **Map to specific tools.** * ✅ "Create a Linear issue, assign to @sales-ops, set priority based on deal size" * ❌ "Notify the relevant team" ## FAQ **Can playbooks call other playbooks?** Enterprise feature — contact sales. **What if a step fails?** Built-in retry + fallback. Failed runs preserved in History for inspection. **Can I version playbooks?** Yes. Every save creates a new version; roll back from the menu. **How do I update one?** Edit in the editor, or describe the change in natural language ("add a step: notify CFO if deal > \$50k"). Goes live on next run. **Can playbooks read sensitive CRM data?** Yes, scoped to your account's permissions. *** Turn your team's repeated motions into one-click playbooks. Start at the [Playbook Editor](https://komo.ai/agents/builder). # Schedules & Triggers Source: https://docs.komo.ai/product/schedules-triggers Run playbooks on a schedule or in response to events across your stack Schedules and triggers turn a [playbook](/product/playbooks) from a one-click action into an autonomous workflow. ## Schedule vs. trigger | | Schedule | Trigger | | ------------ | ---------------------------------------------- | ------------------------------------------------ | | Activated by | A clock (cron) | An event in a connected app | | Typical use | Monday pipeline review, daily Signal Agent run | Inbound reply, "Closed Won," GitHub issue opened | | Set up in | Playbook → **Schedules** tab | Playbook → **Triggers** tab | You can put both on the same playbook. ## Schedules **Quick** — one immediate run for testing. **Recurring** — built-in cadences: | Cadence | Typical sales use | | -------------- | ----------------------------------------- | | Every minute | Real-time inbox monitoring for hot leads | | Every 5–30 min | Signal Agent → Slack pings | | Hourly | Dashboard refresh, urgent reply scan | | Daily | Morning pipeline digest, end-of-day recap | | Weekly | Monday pipeline review, Friday summary | | Monthly | QBR generation, renewal scan | Defaults to your account timezone, DST automatic. **One-time** — single future run: ``` On Thursday 8 AM: Generate pre-call briefs for tomorrow's external meetings. ``` **Advanced (cron)**: ```bash theme={null} # Every Tue + Thu at 2 PM 0 14 * * 2,4 # 1st and 15th at 9 AM 0 9 1,15 * * # Every weekday at 8 AM and 5 PM 0 8,17 * * 1-5 # Last business day of every month at 11:59 PM 59 23 L * 1-5 ``` ## Triggers **Inbox-driven** (often easier via [Inbox routing rules](/product/inbox#routing-rules)): * New email from VIP → notify owning rep * Reply classified as "Hot Lead" → auto-draft fast follow-up * "Meeting Request" → propose calendar slots * "Unsubscribe" → propagate to all campaigns + suppression list **CRM-driven**: * New CRM contact → enrichment + ICP scoring + auto-add to list * Account stage → "negotiation" → generate stakeholder map, push to Slack * Signal Agent surfaces a new lead → auto-draft personalized first touch **External-app-driven**: | App | Trigger | Use | | -------------------- | ----------------------------- | --------------------------------- | | Gmail / Outlook | New email matching pattern | Inbound deal triage | | Calendar | Event created / starting soon | Pre-call brief | | Salesforce / HubSpot | Deal stage change | "Closed Won" → onboarding | | Slack | `@komo` mention or keyword | Conversational invocation | | Notion | Page edited / row added | New ICP → kick off list build | | GitHub / Linear | Issue/PR opened | Engineering update for an account | | Stripe | Payment, subscription change | Customer success follow-up | | Fireflies / Granola | Transcript ready | Auto-summarize → account timeline | …plus 100+ more apps. ## High-leverage patterns **Morning pipeline digest** ``` Playbook: Weekly pipeline review Schedule: Every Monday 7 AM Output: Digest emailed to rep + posted to #sales-pipeline ``` **Signal-to-touch** ``` Playbook: Signal-to-touch (draft 2-step outreach) Trigger: Signal Agent surfaces a new ICP-matched lead Output: Drafts queued in the campaign; Slack DM if high-fit ``` **Pre-call brief** ``` Playbook: Pre-call brief Trigger: Calendar event with external attendee, 12h before Output: Brief in inbox at meeting start - 12h ``` **Closed-won onboarding** ``` Playbook: Customer onboarding kickoff Trigger: Deal stage → "Closed Won" Output: Linear tasks, kickoff email, welcome Slack channel, Stripe record ``` **Renewal risk watch** ``` Playbook: Renewal risk scan Schedule: Monday 7 AM, scoped to accounts renewing in 90 days Output: Watchlist emailed to CS team ``` ## Setting up a schedule Edit the playbook to automate. Right-side panel. Quick, Recurring, One-time, or Advanced (cron). Frequency, timezone, name. Run manually before enabling. Toggle on. ## Setting up a trigger Inside the playbook. Connected apps show a green badge; others prompt for auth. e.g. Gmail "new email received," Slack "keyword mentioned." Narrow with `from:`, `subject:`, channel, etc. Without filters the trigger fires on every event — too noisy. e.g. max once per 30 min, to prevent runaway loops. Use **Test trigger** to simulate, then save. ## Managing Every schedule/trigger appears in the playbook's right panel. **Pause/resume**, **Edit**, **View runs**, **Delete**. ## Tips Always test manually before scheduling. A broken daily schedule is harder to catch than a broken one-off. Use filters aggressively. "New Gmail email" without filters fires on every email. Combine schedules with triggers — one playbook can be daily + on-demand from Slack. Time triggers in your audience's timezone. A 7 AM digest in their inbox, not yours. ## FAQ **What happens if a scheduled task fails?** Komo retries with exponential backoff. Failed runs logged in History. Configure a Slack DM for critical playbooks. **Multiple schedules + triggers on one playbook?** Yes — common pattern: daily schedule + on-demand Slack trigger. **Timezone?** Defaults to your account timezone, overridable per-schedule. DST automatic. **How many schedules/triggers can I have?** Depends on plan. Contact sales for higher limits. *** Turn any [playbook](/product/playbooks) into an autonomous workflow. Pick the motion you run every Monday and ask: *what would make this trigger itself?* # Signals & Signal Agents Source: https://docs.komo.ai/product/signals 24/7 LinkedIn engagement monitoring — auto-add in-market buyers to your pipeline A **Signal Agent** runs 24/7, watches LinkedIn posts that match your sources (keywords, influencers, competitors, your own content), and surfaces the people who comment or react. Every engager is scored against your ICP — only matches land in your list. The closest Komo gets to inbound: you don't pay for the prospect, and you don't have to find them. ## Two tabs at `/signals` * **Agents** — your Signal Agents with status, leads found, next-run time * **Feed** — every match: triggering post, engager profile, ICP score. Filter by agent, source, label. Pause, resume, or run any agent on demand. ## How an agent works 1. **Discover posts** from each signal source 2. **Collect engagers** (comments + optional reactions) 3. **Score against ICP** (titles, locations, industries + free-text criteria) 4. **Add to list** — matched engagers become contacts, with the triggering post attached Runs **twice a day** by default. Posts dedupe within 24h. ## Creating an agent **Lists → New list → Signal Monitoring** (or **Signals → New agent**). Four parts: ### 1. Signal sources (pick any combination) | Source | Provide | When to use | | ------------------------- | ------------------------------- | ------------------------------------- | | **Engagement keywords** | Tags (`cold email`, `ISO27001`) | Widest net | | **Influencer profiles** | Profile URLs | Audience of voices your buyers follow | | **Competitor companies** | Company page URLs | Anyone engaging is warm for you | | **Your LinkedIn profile** | Your profile URL | Re-engage your own audience | | **Your company page** | Your company page URL | Engagement with company posts | ### 2. ICP filters * **Job titles** (e.g. `VP Sales`, `RevOps Lead`) * **Locations** (e.g. `United States`, `EMEA`) * **Industries** (e.g. `SaaS`, `Fintech`) * **Matching mode**: * **High precision** — fewer, better leads (default) * **Discovery** — broader net ### 3. Caps & cost controls | Cap | Default | Limits | | -------------------- | ------- | --------------------------------------- | | Posts per source | 10 | Recent posts scanned per source | | Raw engager cap | 400 | Unique engagers scraped per run | | Apify enrichment cap | 200 | Profiles enriched per run | | Daily lead cap | 100 | Max engagers added per day | | Fetch reactions | on | Reactions + comments (\~2× scrape cost) | ### 4. Advanced (optional) * **Additional AI criteria** — free-text rules for the scorer (`"Prefer founders. Skip students. Prioritize anyone hiring SDRs."`) * **Exclude service providers** — drops consultants, agencies * **Exclude Open-to-Work** — drops profiles flagged on LinkedIn A **Run immediately** checkbox kicks off the first run as soon as you save. ## Feed view Each match card shows: triggering post, engager profile, engagement type, signal source, ICP score and reasoning. Click an engager to add to a different list, push to inbox routing, or mark as read. ## Example: high-quality outbound for a SaaS company ``` Name: "VP Sales engaging with cold-email content" Sources: Engagement keywords: "cold email", "outbound sequence", "SDR playbook" Influencer profiles: <2 sales thought leaders> Competitor companies: <2 competitors> ICP filters: Titles: VP Sales, Head of Sales, CRO Locations: US, Canada Industries: SaaS, IT Mode: High precision Caps: Daily lead cap: 100 Advanced: Additional: "Prioritize anyone mentioning hiring, building, or measuring an outbound motion." Exclude service providers: ON ``` Expected output: \~20–60 leads/day, every one publicly in-market. ## Pause, run, delete From the **Agents** tab menu: **Run now**, **Pause / resume**, **Delete**. ## Connected to [Contacts](/product/contacts) (matched engagers) · [Accounts](/product/accounts) (auto-created parent) · [Lists](/product/lists) (the bound list) · [Campaigns](/product/campaigns) (attach list → auto-enroll new matches) · [Inbox](/product/inbox) (replies) ## Tips **Start with high precision.** Discovery mode is noisier — only loosen if daily lead count is too low. **Engagement keywords cast the widest net.** Influencer/competitor sources are narrower but higher-quality. **Use Additional criteria aggressively.** Structured filters can't capture nuance like "anyone complaining about Outreach." **Leave Fetch reactions on.** A typical post has 5–10× more reactions than comments — worth the 2× scrape cost. # Quickstart Source: https://docs.komo.ai/quickstart Get from signup to your first booked meeting in under 30 minutes
Decorative background image. Decorative background image.

Welcome to Komo AI

The AI Revenue Engine. From buyer signal to close — automated. Build your first list, launch your first campaign, and book your first meeting in under 30 minutes.
Start your 7-day free trial at komo.ai
## Your first 30 minutes The left sidebar has **History**, **New Task**, and **Sales CRM** (Dashboard, Accounts, Contacts, Lists, Campaigns, Signals, Inbox). Fastest path from cold workspace to working pipeline: **Inbox → Settings** → connect Gmail or Outlook. Required for sending campaigns and triaging replies. [→](/product/inbox) **Lists → New list** → pick a source (Sales Nav URL, People Search, CSV, manual, Find with AI, or Signal Monitoring). [→](/product/lists) **Signals → New agent** → add keywords, competitor pages, or influencer profiles. Komo auto-adds matched LinkedIn engagers to a list. [→](/product/signals) **Campaigns → New campaign → Create with AI** → describe target, offer, goal in one sentence. Review the drafted sequence and save. [→](/product/campaigns) **New Task** → pick **Assistant** for quick CRM-grounded answers, **Task** for multi-step work in a cloud sandbox. [→](/product/new-task)
# Cancel Subscription Source: https://docs.komo.ai/support/cancel-subscription How to cancel and what happens after Cancel anytime through the Stripe Customer Portal. Access continues until the end of your current billing period. ## How to cancel Bottom-left corner of Komo. From the menu. Shows current plan + renewal date. Opens the popup. Redirects to the Stripe Customer Portal. Click **Cancel subscription** → optional feedback → Confirm. Stripe emails you a confirmation. Paid access continues until end of current period. ## What happens after **Immediately:** * Subscription marked "Canceled" * No future charges **Until end of billing period:** * Full paid access * All data preserved **After billing period ends:** * Account drops to a limited free tier * All data preserved — accounts, contacts, lists, playbooks, inbox * Signal Agents, scheduled playbooks, and active campaigns pause until you re-subscribe ## Reactivate Anytime: Profile → **Billing** → **Upgrade** → pick a plan → checkout. Reactivating in the same billing period restores immediate access. ## Your data is safe * **Accounts + Contacts** — CRM preserved * **Lists** — including Signal Agent–bound lists * **Playbooks** — all your authored motions * **Inbox** — threads, categories, routing rules * **Integrations** — connections kept; some functionality limited until re-subscribe ## Troubleshooting **Can't find Cancel?** You must be in the Stripe Customer Portal, not the Komo Billing page. Refresh, clear cache, check the right Stripe account. **Cancellation not processing?** Try a different browser, disable extensions, or contact Stripe support. **Cancelled but still charged?** Check your Stripe confirmation email and the portal for the cancellation date. Forward your receipt to [admin@komo.ai](mailto:admin@komo.ai) — we'll investigate. **Want to pause instead?** No pause option currently. Cancel + reactivate when ready — your data is preserved. ## FAQ **Refund mid-cycle?** No prorated refunds. Access continues to end of billing period. See [Refund Policy](/support/refund-policy). **Team members?** On team plans, all members lose paid access when the subscription ends. Notify before canceling. **Cancel during free trial?** Yes — no charges. See [Free Trial](/support/free-trial). **Use Komo after cancel?** Yes — limited free tier. Re-subscribe anytime to restore Signal Agents, scheduled playbooks, active campaigns. *** Need help? [admin@komo.ai](mailto:admin@komo.ai). Your account is always there at [komo.ai](https://komo.ai). # Dark Mode Source: https://docs.komo.ai/support/dark-mode Learn how to enable and customize dark mode in Komo AI Dark Mode reduces eye strain and can make reading easier in low-light settings. Komo AI offers flexible theme options to match your preferences and working environment. ## Available Theme Options Komo AI supports three theme modes: * **Light Mode** - Bright, traditional interface with light backgrounds * **Dark Mode** - Dark interface optimized for low-light environments * **System Mode** - Automatically matches your device's system theme settings System Mode is perfect if you want Komo AI to automatically switch between light and dark modes based on your device's settings or time of day. ## How to Enable Dark Mode ### Step 1: Access Your Profile Menu Click on your **profile icon** in the **bottom left corner** of the Komo AI interface. ### Step 2: Select Theme From the menu that appears, click on **Theme**. ### Step 3: Choose Your Preferred Mode Click the **Theme** option repeatedly to toggle through the available modes: 1. **Light** - Bright interface with light backgrounds 2. **Dark** - Dark interface with reduced brightness 3. **System** - Matches your device's current theme The interface will update immediately to reflect your selection. *** Customize your workspace and start automating in your preferred theme at [komo.ai](https://komo.ai). # Free Trial Source: https://docs.komo.ai/support/free-trial Every Komo account starts with a 7-day free trial — full access, no card required Every new Komo account starts with a **7-day free trial**. Full access to every paid feature. No credit card. ## What's included * ✅ Every paid-tier feature * ✅ All six [prospecting paths](/product/lists) (Sales Nav, People Search, CSV, Manual, Signal Monitoring, Find with AI) * ✅ Unlimited [Signal Agents](/product/signals) * ✅ Unlimited [campaigns](/product/campaigns) and senders * ✅ Full [Inbox](/product/inbox) triage with routing rules * ✅ [Playbook](/product/playbooks) authoring + scheduling * ✅ All [integrations](/integrations) — Gmail, Outlook, LinkedIn, Apollo, Salesforce, HubSpot, Slack, Notion, and more ## How it works Email or SSO. No card required. Every paid feature enabled on day 1. Follow the Dashboard's getting-started checklist. Adding a card during the trial sets up the paid plan for day 8. No charges until then. Day 8: if you've added payment, the subscription starts. If not, the account drops to a limited free tier — all data preserved. ## Recommended week 1 | Day | Goal | | ------- | --------------------------------------------------------------- | | **1** | Connect Gmail/Outlook, LinkedIn, and your CRM | | **2** | Build your first prospect list ([6 paths](/product/lists)) | | **3** | Set up a [Signal Agent](/product/signals) — leads start flowing | | **4** | Launch a [campaign](/product/campaigns) targeting your list | | **5–6** | Triage replies in [Inbox](/product/inbox), add routing rules | | **7** | Save your repeated motions as [playbooks](/product/playbooks) | By day 7 you have a working sales motion that runs on its own. ## FAQ **Need a credit card to start?** No. **What happens at day 8 without payment?** Limited free tier. All data preserved — lists, contacts, accounts, playbooks, integrations. **Can I extend?** Email [admin@komo.ai](mailto:admin@komo.ai) with your use case. **Enterprise trial?** Yes — dedicated SE, custom integrations, procurement-ready terms. Email [admin@komo.ai](mailto:admin@komo.ai). **Multiple users?** Yes — invite teammates from Settings → Team. Seat limits apply on paid plans. **Cancelled before day 8 — charged?** No. Zero charges if cancelled before the trial ends. ## Pricing We're still finalizing plan structure. Email [admin@komo.ai](mailto:admin@komo.ai) for a quote tailored to your team size and volume. Enterprise pricing includes custom SLAs and procurement-ready terms. *** Start at [komo.ai](https://komo.ai) — no card required. # Refund Policy Source: https://docs.komo.ai/support/refund-policy Komo AI's refund policy and subscription terms ## Free trial Every new account starts with a **7-day free trial** with full feature access. * ✅ Every feature unlocked * ✅ No charges during the trial * ✅ Cancel anytime before day 8 * ✅ No commitment Use the trial to connect your inbox, build one prospect list, and launch one campaign. A full week to evaluate Komo against your real motion. ## After subscription starts Once paid (after day 7): * **No refunds** for active subscriptions * Cancel anytime — access continues to end of billing period * No prorated refunds for partial periods ### Why no refunds The 7-day trial exists specifically so you can evaluate before committing. Use it to test every feature, fit it to your workflow, and make an informed decision. ## How to cancel 1. Profile icon → **Billing** 2. **Change Plans or Manage Subscription** 3. Click **Manage Subscription** in the popup 4. Cancel from the Stripe Customer Portal Step-by-step: [Cancel Subscription](/support/cancel-subscription). **After cancellation:** * Full access until end of current billing period * Account drops to limited free tier * All your data preserved * No further charges ## Special circumstances For exceptional situations, email [admin@komo.ai](mailto:admin@komo.ai) with: * Full name * Account email * Detailed explanation * Any relevant screenshots Special-circumstance requests are reviewed case-by-case. Approval not guaranteed. ## Billing details * **During trial**: no charges * **First charge**: automatic on day 8 unless cancelled * **Recurring**: monthly or annual depending on plan * **Payments**: processed via Stripe * **Approved refunds**: returned to original payment method in 5–10 business days ## To avoid charges 1. Set a reminder before day 8 2. Cancel before then if you're not ready 3. Sign up again whenever you change your mind ## More * [Update Payment](/support/update-payment) * [Cancel Subscription](/support/cancel-subscription) * [Free Trial](/support/free-trial) * Email: [admin@komo.ai](mailto:admin@komo.ai) *** Try Komo risk-free with the 7-day trial at [komo.ai](https://komo.ai). # Update Payment Information Source: https://docs.komo.ai/support/update-payment Change your payment method or billing address Manage payment details through the Stripe Customer Portal. ## How to update Bottom-left of the Komo interface. From the menu. Opens the subscription popup. Redirects to the Stripe Customer Portal. **Payment method:** Click **Update payment method** or **Add payment method** → enter card → Save. **Billing address:** Click your current method → **Edit** → update → Save. Changes apply to all future billing cycles. ## In the Stripe portal you can * Add or remove payment methods * Update billing address * View billing history and download invoices * Update card expiration / CVV ## Accepted methods * **Credit / debit cards** — Visa, Mastercard, Amex, Discover * **Digital wallets** — Apple Pay, Google Pay (where available) Enterprise customers can arrange invoice billing. Contact [admin@komo.ai](mailto:admin@komo.ai). ## Troubleshooting **Can't update?** Verify you're in the correct account, allow pop-ups, clear cache, try a different browser. Still stuck → [admin@komo.ai](mailto:admin@komo.ai). **Card declined?** Check card details, activation status, available credit. Bank may need to authorize international payments. Try a different method. **Billing address mismatch?** Match the address on file with your card issuer. **Changes not reflecting?** Refresh the Billing page or wait 5–10 minutes. Still missing after 15 minutes → [admin@komo.ai](mailto:admin@komo.ai). ## FAQ **When is the new payment method charged?** On the next billing date. **Can I use different methods for different subscriptions?** One active method per account. Need separate billing? Use separate accounts. **Charged when updating?** No — only on the regular billing cycle. **Multiple methods?** Yes, set a default. Stripe falls back to others if the default fails. **Remove old methods?** Click the method → Remove. At least one valid method required for active subscriptions. **Is my payment info secure?** Yes. Processed and stored by Stripe (PCI-compliant). Komo doesn't store full card details. *** Questions? [admin@komo.ai](mailto:admin@komo.ai). # Overview Source: https://docs.komo.ai/welcome The AI Revenue Engine ## Welcome to Komo AI Komo is the **AI Revenue Engine** — revenue work on autopilot, from buyer signal to close. **You sell. Komo does the rest.** ## What Komo does * **[Accounts](/product/accounts) & [Contacts](/product/contacts) that enrich themselves.** Every record auto-researches the fields you care about, with cited sources — fresh, verified, never stale. * **Six ways to prospect.** [Sales Nav, People Search, CSV, manual, Find with AI, and Signal Agents](/product/lists) — all into one enriched list. * **24/7 [Signal Agents](/product/signals).** Watch LinkedIn engagement, competitor posts, and influencer content. Surface in-market buyers your competitors aren't already blasting. * **Multi-step [campaigns](/product/campaigns).** AI drafts email + LinkedIn sequences from real account evidence. You review every line; your senders ship — never an autonomous AI SDR blast. * **Smart [inbox](/product/inbox).** Replies auto-categorized (Hot Lead, Interested, Meeting Request, Objection, Unsubscribe…) and routed to an agent or teammate. * **An [agent that knows your CRM](/product/new-task).** Ask anything at `/new` — drafted, cited, grounded in your real data. No more "research the account" tax before every call. * **[Playbooks](/product/playbooks).** Reusable templates for the motions you run every week. ## Who it's for | | | | ----------------- | ------------------------------------------------------ | | **RevOps** | One operating layer for signal, sequence, and CRM work | | **Sales leaders** | Pipeline quality before activity volume | | **AEs / SDRs** | Every rep gets a researcher and an operator | | **Founders** | Weekly pipeline without hiring an SDR team | ## Four pillars Warm leads, not cold lists. Buyers already in-market. Every account scored by fit, timing, and connection — with citations. Cited briefs in one page, ready for the call. QBRs, renewals, and inbox triage — automated. *** Start your **7-day free trial** at [komo.ai](https://komo.ai) — no credit card required.