Skip to main content

Agent K

Agent K is the prospecting agent. It finds people worth contacting — from your own site traffic, from net-new outbound discovery, and from your dormant CRM — and hands them to you as leads with the evidence attached. It has its own Agent K page in the sidebar, with two tabs: a Feed inbox of every lead it's working and Reports on what came of them.

Beta

Agent K is currently in beta and is enabled per account by the Knock Knock team — contact support to join. Once it's enabled for your account, you control it with the Agent K is active toggle in Agent K settings.

Where leads come from​

Agent K works three sources:

  1. Inbound — visitors on your site that it can identify through the Identity Graph.
  2. Outbound — net-new prospects matching your ideal customer profile, but only when there's a "why-now" signal: they're hiring, expanding, modernizing their tech, they raised money, or a brand-new business just registered. A good-fit company with no signal is skipped — fit alone is just a cold list.
  3. Reactivation — dormant contacts already in your CRM that are showing signs of life again.

You can steer how Agent K weighs these sources by just telling Nox in chat or voice — "focus on reactivation this week" is enough.

Getting set up​

Setup is a standalone flow: click Set up on the Agent K card and a guided walkthrough takes you through the essentials — ideal customer, signals, and delivery. Every step is skippable; anything you skip can be finished later in Agent K settings.

Before Agent K can be switched on, a "Before you turn Agent K on" window shows you exactly what it costs: a pricing table with the per-step price of each data lookup it makes on your behalf. Nothing is charged until you've seen the prices and turned it on. See Billing.

Two ways Agent K hands off leads​

Under Outreach → How Agent K hands off leads, you choose who writes and sends the messages. Either way, every lead lands in your LeadConnector with its token, why-now note, and trigger tags — the mode only decides who does the writing.

Deliver to LeadConnector (default)​

Push to LeadConnector only — your own sequences write and send. Agent K delivers each approved lead as a tagged contact and your own LeadConnector workflows send the sequences. This is the default, and the tags and custom fields are the contract your workflows trigger on.

Agent K sends​

Agent K composes & sends — Agent K writes each message plus a short follow-up sequence and sends it through your connected LeadConnector email. In this mode:

  • Write your own touches (optional) — override any step of the sequence: First message, Second message, a few days later, and Last message. Leave them blank and Agent K writes each one around the lead's own why-now; write your own version with [LINK] where the tracked link should go.
  • What you write below is — how Agent K treats those touches. A guide — Agent K keeps your offer and points, but writes each lead their own version is the default: your copy is the brief, and the preview shows the personalized rewrite. Exact wording — send it word for word to every lead sends your text verbatim; the setting warns you that identical mail to everyone reads as a blast and can hurt inbox delivery.
  • What are you offering? — describe your offer once and Agent K weaves it into every draft.
  • Where should the tracked link go? — the destination page for the tracked link in each message.
  • Daily send cap — an enforced ceiling on automatic sends per day (10 to 150), to keep inbox delivery healthy. Messages you approve by hand aren't capped.
  • Never a blind drip — the sequence stops the second a lead replies or clicks through, and when there's nothing new to say Agent K sends fewer messages, never a filler one.

You approve every push​

Push leads automatically is off by default. Leads Agent K finds wait in the Feed under To review, each with its why-now evidence, until you click Push to GHL — no LeadConnector contact is created before you approve a lead. Turn Push leads automatically on (the Auto-push toggle at the top of the feed does the same) and approved-quality leads flow through at your daily limit without the click.

Every push, send, and skip asks first. Push to LeadConnector? explains that the contact gets written with the trigger tags and your workflows start sending from there; Send this message? warns it can't be unsent; Skip this lead? warns there's no way to bring the lead back from this screen. The batch buttons — Push all (N) or Approve all (N) — confirm the same way.

The Feed​

The Feed tab on the Agent K page is a three-pane inbox — everything Agent K is doing, and everything waiting on you. A rail of leads on the left, the selected lead in the middle, and the contact on the right; drag the handles between panes to resize them. On narrower screens the contact column drops below the lead, and on small screens it's one pane at a time with a Back to all leads button.

The rail:

  • Status tabs — To review (waiting on you), Sent, Skipped, and All, each with a live count. The feed opens on the first tab that has something in it. One row is one message, so a lead with a three-touch sequence shows as three rows.
  • Channel and Why-now signal selects — narrow the open tab to one channel (Email, GHL push, LinkedIn) or to one signal (From email, Returning, High intent, Hiring, Raised money, Went quiet, and so on — only the signals present in that tab are offered). Counts show in parentheses.
  • Search leads and messages, plus a date range that defaults to All dates — no window at all — with presets, a custom from/to, and an X to clear it.
  • Today chips at the top of the page — Found today, Pushed, and Site visits show at a glance what Agent K did today; Site visits counts every visit from an Agent K link, each one a visitor recognized by name as they land.

The lead pane shows everything without hiding anything behind an expander:

  • Everything Agent K found — the enrichment, the why-now evidence, and (for site visitors) a Watch the session recording link.
  • Email sequence — the three-rung ladder, Touch 1, Touch 2, Touch 3, with X of 3 sent and a status per rung: Sent, Delivered, Waiting for approval, Scheduled, Due, Skipped, Send failed, or Not sent. The footer explains why the sequence stopped ("The lead replied, so the sequence stopped itself…"), and Edit the sequence copy → jumps to the setting. In push mode there's no ladder — your own LeadConnector workflow sends the sequence, and Agent K doesn't record what your workflow sent afterwards.
  • Conversation — for pushed or emailed leads, the live LeadConnector thread, every channel in both directions, with a channel label on each message.
  • The send receipt — for every message that went out, who decided and why: Sent automatically by Agent K, Approved by a person, Sent automatically by Nox, or Sent by a standing rule, with the channel, recipient, step (Follow-up N of 3), why this lead, how it was found, the signal, and a deep link to the setting behind the decision (for example Switch to 'Approve each message' → or Turn off autonomous sending →). If a send went past a safety gate — quiet hours, the frequency cap, a cooldown, or a teammate already in the conversation — a Sent past a safety gate card names who allowed it, when, and why.
  • Written into LeadConnector — for pushed leads, the exact fields, tags, and note that were written (and, before a push, what pushing will write), with Change how Agent K hands off leads →.

Rows explain themselves: a skipped lead shows the reason in plain language ("They replied — follow-ups stopped", "They unsubscribed", "On the do-not-contact list"), and a failed send shows the real failure reason with a retry. In send mode, emailed messages render the exact email HTML the lead received — what you see is what went out.

If the queue is quiet, the empty state says why — the last hunt's result, a full queue, or something that needs your attention (like an empty wallet).

Reports​

The Reports tab answers "what came of it?" over any date range.

  • Tiles — Delivered, Emailed (send mode only), and Visited site. Click a tile to narrow the journey list below to leads that reached that stage.
  • Who, and what happened — one row per lead, walking its journey in stage words: Found, Queued for review, Delivered, Emailed, Visited site, Replied, Booked, Unsubscribed, Skipped, and Greeted on site. Expand any row for the full detail — who the person is, the signal, and every step with its timestamp.
  • Daily trend — a chart of activity across the period.
  • Impact cards — Worked after hours (leads handled outside your working day), Forgotten leads revived (dormant CRM contacts brought back), and Recognized the second they clicked (visits stitched to a name the moment they landed).
  • Conversations — where a lead replied, open the read-only conversation view to read the exchange in place.

Replied counts replies to every touch, including emails your own LeadConnector workflow sent after a push — the lead's summary in the Feed says "This lead has written back." Delivered leads are also added to the Identity Graph the moment they're pushed, not only once they click back to your site.

note

There is no "Opened" stat. Open tracking is noise — bots and mail scanners inflate it. Agent K reports what actually matters: delivered, emailed, and who came back to your site.

Agent K settings​

Go to Settings → AI Agents → Agent K. Settings are organized into seven tabs:

Overview​

  • Agent K is active — the master toggle. When on, Agent K finds leads and drafts outreach for you; turn it off to pause.
  • Weekly digest — Send the weekly digest plus a day picker (default Monday). Quiet weeks send nothing — an empty digest is noise.

Ideal customer​

Describe your ideal customer — a free-text description. Click Let Agent K read this and it parses what you wrote, may ask a clarifying question or two, and shows its understanding as removable chips: Industry, Geo, Title, Seniority, Keyword, Exclude, and Size. Remove any chip it got wrong.

Your traffic​

  • Re-engage your own traffic — toggles for A past visitor comes back, Someone went quiet, and Revive forgotten CRM leads, plus Stay out of the way when they reach out first (on by default) — this skips anyone who already contacted you via a form, chat, booking, or call, so Agent K never talks over an active conversation.
  • Consider a lead dormant after — a slider (default 90 days) for how long a CRM contact must be quiet before reactivation considers them dormant.

Outreach​

  • How Agent K hands off leads — the sending mode, plus the send-mode controls (touch overrides and whether they're a guide or exact wording, offering, tracked-link destination, daily send cap).
  • What should Agent K watch for? — the why-now signals, as toggles: They're growing their team, They're expanding, They're modernizing, They raised money, A brand-new business opened.
  • Push leads automatically — off by default; see You approve every push.
  • Daily limit — a slider from 1 to 50 (default 10). It's a cap, never a target: Agent K paces releases naturally through the day and holds them during the recipient's night.
  • How Agent K writes for you — Voice & tone and Signature, shaping every message it writes: outreach emails, follow-ups, LinkedIn messages, and suggested replies.

Channels​

The LinkedIn channel — see LinkedIn outreach.

Delivery​

The LeadConnector delivery details — custom fields, enrichment fields, and the tracking-token backfill. See How leads land in LeadConnector.

Do-not-contact​

Every suppressed contact, listed where you can see it — people who unsubscribed, replied with a stop, or were suppressed by you. Remove from do-not-contact lets Agent K contact someone again if they were suppressed by mistake.

LinkedIn outreach​

Turn on the LinkedIn channel under Settings → AI Agents → Agent K → Channels and click Connect LinkedIn — a hosted flow signs you into your own LinkedIn account; Disconnect ends it at any time. Then:

  • Connect requests carry real context from the lead's why-now, and you see a preview of the DM on accept — the message that goes out the moment they accept.
  • Warm up first — start at low volume and ramp up gradually, the way a healthy account behaves.
  • Personalize every request — each request is written for that person, never a template blast.
  • A reply stops the sequence for that lead immediately, same as email.

LinkedIn messages always wait in your review queue for approval before sending.

LinkedIn billing​

The connected LinkedIn seat is charged monthly from your Wallet. The day before renewal you get a heads-up email if your balance won't cover it — and if the Wallet can't pay at renewal, the LinkedIn account is disconnected immediately, with a notice telling you why. Top up and reconnect to resume.

How leads land in LeadConnector​

Each approved lead becomes a contact in your LeadConnector, carrying:

  • Custom fields kk_token and kk_why_now — create both custom fields in LeadConnector first. kk_why_now holds a one-line reason you can merge straight into your email templates.
  • A why-now note on the contact.
  • Trigger tags: nextlevel agent-k-lead, nextlevel signal:*, nextlevel source:* — and nextlevel returned-to-site, written when a lead clicks back to your site.

In the default mode, build LeadConnector workflows triggered by these tags to send your sequences. To recognize returning clicks instantly, append ?kk={{contact.kk_token}} to every link in your templates. (In send mode Agent K's own links carry the token automatically.)

Two optional extras on the Delivery tab:

  • Enrichment fields — custom-field names for a LinkedIn URL field and Job title field, filled from enrichment. Leave either blank to skip it.
  • Set tracking token on existing contacts — click Run now to backfill kk_token onto all your existing LeadConnector contacts, so returning clicks from older contacts are recognized too. It checks that the custom field exists first, shows live progress, survives a page refresh, and is safe to re-run.
note

The tags and custom fields are the contract between Agent K and your workflows. If a sequence isn't firing, check that your workflow triggers on nextlevel agent-k-lead and that the kk_token / kk_why_now custom fields exist in LeadConnector.

When a lead replies​

A reply stops all follow-ups for that lead immediately, suppresses the contact, and notifies you. Nox can suggest a reply for you to send — it never auto-sends replies.

Agent K also understands conversational opt-outs: a reply like "please don't reach out again" suppresses the lead even without an unsubscribe keyword, and they appear on the Do-not-contact list where you can see — and reverse — it.

The tracked links Agent K relies on aren't limited to LeadConnector sequences. You can mint the same ?kk= tokens for recipient lists you send from an external email tool — either as a CSV download for any sender, or pushed directly into a ManyReach campaign — so every campaign click lands on your site already recognized. Set it up on the ManyReach card under Settings → Integrations — see Email Campaigns (ManyReach).

Billing​

Agent K's data lookups are charged from your Wallet as itemized line items, at the per-step prices shown in the pricing table before you enable it: lead search, contact reveal, buying signals, new businesses, and the LinkedIn seat. Only successful steps are charged — a lookup that finds nothing, or a failed call, costs nothing. Every charge appears on the Wallet transactions page under its own type.

Next steps​

  • LeadConnector integration — connect the CRM Agent K delivers into.
  • Wallet — where Agent K's provider charges and the LinkedIn seat are billed.
  • Nox Assistant — the in-app assistant that works alongside Agent K.
  • Identity Graph — how visitors on your site get identified in the first place.