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 delivers them into your LeadConnector (formerly shown as GoHighLevel) as tagged contacts. Your own LeadConnector workflows send the sequences; Knock Knock does not send Agent K email itself.

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.

Agent K settings​

Go to Settings → AI Agents → Agent K.

  • Agent K is active — the master toggle. When on, Agent K finds leads and drafts outreach for you; turn it off to pause.
  • 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.
  • 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.
  • 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.
  • 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, used in the drafts and fields it produces.
  • Weekly digest — Send the weekly digest plus a day picker (default Monday). Quiet weeks send nothing — an empty digest is noise.

How sequences send (LeadConnector delivery)​

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.

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.

Two optional extras on the same screen:

  • 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.

The review queue​

On your Dashboard, Agent K — who to reach out to next lists the leads it found, each with the why-now evidence. For every card you can Approve & send, Edit, or Skip — or clear the queue with Approve all. Delivered leads show a Delivered badge and an Open contact in LeadConnector → link.

Why-now badges tell you at a glance why each lead surfaced: From email, Returning, High intent, Engaged, Re-engaged, New business, Hiring, Expanding, Modernizing, Raised money, Went quiet, and ICP match.

Alongside the queue:

  • Today's pipeline — a rail showing Leads found, Delivered, Replied, and Booked.
  • What would you have missed without Agent K? — the leads you'd never have seen otherwise.

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.

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 Campaigns tab of your Dashboard.

Billing​

Agent K's AI usage and the per-lookup data-provider fees are billed as AI credits, in the same usage totals as chat and voice AI. See AI Credits & Usage.

Next steps​