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 (at /prospecting), with a Feed inbox of every lead it's working and a Leads tab — your call list of every lead it delivered, with what came of them. Accounts on the alternative lead source also get a Hunts tab.

Agent K is available on every account. You switch it on and off yourself with the status toggle in Agent K settings; it needs somewhere to deliver leads — a connected CRM (LeadConnector or HubSpot), or your own mailbox to email them from — and a funded Wallet to run. With both CRMs connected you pick which one Agent K delivers into. What it does beyond finding leads — calls, texts, emails and LinkedIn invites when something happens — is set up in Automations.

Agencies: rename Agent K

Agencies can give Agent K their own name for every client company under Agency settings → Prospecting Agent Name (leave it blank to keep "Agent K"). The new name shows everywhere your clients see Agent K — the app, notifications, emails, notes written into LeadConnector, and Nox in chat and voice. The LeadConnector tags (nextlevel agent-k-lead and the rest) never change, so existing workflows keep firing.

Where leads come from

Agent K works three sources:

1. Inbound — visitors on your site that it can identify through the Identity Graph: a past visitor coming back, someone who went quiet, or — if you switch it on — someone highly engaged on your site right now.
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. (Accounts on the alternative lead source work differently.)
3. Reactivation — dormant contacts already in your CRM that are showing signs of life again.

A few guard rails apply to every lead:

• Country — Agent K reads the country out of your ideal customer description and shows it as a Country chip. Leads outside that country are skipped. New-business registrations are only available in the US, so an ideal customer outside the US gets outbound leads from the other signals only — the Feed says so rather than looking stuck.
• People you already have — an outbound prospect who turns out to be an existing LeadConnector contact is skipped; existing contacts are reactivation's job, with its own dormancy and consent rules.
• Turning a source off stops it — switching off Revive forgotten CRM leads also stops the re-engaged leads already in flight: queued ones aren't released and no further follow-ups are written.

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 guided five-step walkthrough — Who to go after (your ideal customer), What Agent K watches for (the signals — nothing to pick, it watches them all), Your own traffic (re-engagement and the daily limit), How it hands off leads, and a final review — ending with Activate Agent K. Anything you skip can be finished later in Agent K settings.

New accounts meet the same walkthrough as a step in client setup. It asks you to Connect LeadConnector first (the sign-in leaves the app and comes straight back to the step), or Skip — connect it later; you can also Skip for now and set up Agent K later in Settings. No CRM? Skip the sign-in and connect your own mailbox under Settings → Integrations — Agent K will email leads from it.

Before Agent K can be switched on:

• A "Before you turn Agent K on" window shows exactly what it costs — the per-action price of each lookup it makes on your behalf. Nothing is charged until you've seen the prices and clicked I understand — turn it on. See Billing.
• Your Wallet must have a balance. At $0 the settings show "Your wallet is $0.00 — fund it to activate Agent K" with a Top up wallet button.
• With neither a CRM nor a mailbox connected, a Nothing to deliver leads to banner asks you to connect LeadConnector or HubSpot, or your own mailbox so Agent K can email leads itself.

Two ways Agent K hands off leads

Under Outreach → How Agent K hands off leads, you choose who writes the emails. Either way, every lead lands in your CRM with its token, why-now note, and trigger tags — the mode only decides who does the writing. A live summary under the choices reads back the result, for example "Leads land in LeadConnector · Agent K emails them from you@yourcompany.com."

Choosing the CRM and the sender

• Deliver leads to: — shown when there's a choice: each connected CRM (LeadConnector, HubSpot) and, with your mailbox connected, No CRM — just email them from your address. If the CRM you picked is later disconnected, Agent K stops delivering rather than switching to another CRM.
• Send the emails: — in compose-and-send mode on LeadConnector with a mailbox connected: Through LeadConnector conversations or From your mailbox. A lead's whole sequence goes out the way its first email did.
• No CRM at all — with only a mailbox connected, Agent K always composes and sends: there's nothing to push to, so leads stay in Agent K and every email goes out from your mailbox. Pushing, tags and custom fields don't apply.

Emails sent from your mailbox carry an unsubscribe link, follow-ups thread onto the earlier email, and replies land in your inbox — see Your Mailbox.

Agent K on HubSpot

If HubSpot is your CRM, Agent K delivers (HubSpot has no compose-and-send of its own) — unless your mailbox is connected, in which case Agent K composes & sends sends from your mailbox while every lead still lands in HubSpot. Under How your team picks up each lead in HubSpot, choose A HubSpot workflow — trigger it on the "kk_tags" contact property (Professional tiers) or A task for your team on each lead, with the why-now and their link. The Agent K settings show the HubSpot setup steps in place of the LeadConnector ones — see HubSpot.

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. In this mode Agent K never sends an email on its own — not even from a rule or bulk run — so it can't double up on your workflow's sequence.

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 or from your mailbox. In this mode:

• 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), counted from your own midnight, to keep inbox delivery healthy. Messages you approve by hand aren't capped.
• The follow-up messages — 3 max — override any step of the sequence: First message (optional), Second message, a few days later (optional), and Last message (optional). 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. Preview the sequence drafts all three for a sample lead.
• What you write below is — A guide — Agent K keeps your offer and points, but writes each lead their own version is the default: your copy is the brief. 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.
• 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.

Whether these emails go out on their own or wait for you is set in one place — the Sending tab. The Outreach tab repeats the current answer with a Change what sends without asking → link.

What goes out without asking

Pushes. In the default mode, 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 LeadConnector — 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 leads flow through at your daily limit without the click.

Messages. Agent K's own emails and LinkedIn invites follow the grid on the Sending tab — per channel, Ask me first, After they visit, or Automatically. Anything set to ask waits in your review list; nothing is dropped. Your rules and bulk runs send the way you set each one up.

Confirmations. Every manual 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.

Held drafts. An email that's allowed to go out automatically but is waiting shows when it will go instead of "Drafted": Sends 4:00 PM (the recipient's quiet hours), Sends tomorrow (today's send cap is used up), or Sends after a visit (a prospect set to "After they visit" who hasn't been on your site yet), with a note on the lead.

The queue. When rules or bulk runs have lined something up, a chip in the Agent K page bar reads N queued · M need your approval. Click it to open Agent K's queue — Needs your approval (calls, texts and messages waiting on you, with Approve and Cancel) and Going out on their own (what's scheduled and when). A step marked "Waiting for approval" in the automations activity log opens the same list.

New-lead alerts

When Agent K releases a batch of new leads you get:

• An in-app pop-up with its own sound (and a desktop notification) that stays until you dismiss it. Open lead jumps straight to the lead the notification names; View leads opens the Feed. Muted notifications stay silent.
• A phone push for each batch, if the Agent K push toggle is on in Notification settings. Your daily push cap and quiet hours apply.

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.

If something is stopping Agent K — LeadConnector not connected, an empty wallet, an ideal customer it hasn't read yet — a banner across the top says what, with a button to fix it, on every tab.

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 or one signal. Counts show in parentheses.
• Search leads and messages — by name, email or company.
• Filters — Engagement (a min/max on the best engagement score across their visits), Visited (Has visited your site, On your site now, Never visited), Has (Phone, LinkedIn, Email), and CRM (In CRM, Found details not in CRM, Not in CRM).
• A date range that defaults to All dates, 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.

Each row shows the latest step the lead reached ("Sent 5m ago", "Pushed 1h ago"), icons for the phone, email and LinkedIn Agent K has, a CRM badge, and a visited badge with their best score (live while they're on your site). Tick rows — or select every lead matching the filters — to act on them in bulk; see Bulk actions.

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

• Everything Agent K found — the enrichment and the why-now evidence.
• 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, and Edit the sequence copy → jumps to the setting. In push mode there's no ladder — your own LeadConnector workflow sends the sequence.
• Conversation — the live LeadConnector thread, every channel in both directions, plus Agent K's own AI calls and texts (sent, scheduled or failed) — including for leads not yet in your CRM. A designed email from one of your LeadConnector templates shows as the email itself, subject on top, rather than a chat bubble. Each text has an Open in Chats → link and each call opens on the Calls page.
• Website visits — every visit with its scores, and Watch live → or Open recording →. See Visits and scores.
• 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, sent by a standing rule, or sent by one of your Agent K rules or bulk runs — with the channel, recipient, step, why this lead, how it was found, the signal, and a deep link to the setting behind the decision. 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 fields, tags, and note that were written (and, before a push, what pushing will write), with Change how Agent K hands off leads →.

The contact pane holds the person, their company, Found via, and the lead's timeline (Found / Pushed / Sent). From here you can:

• Find phone number / Find LinkedIn — an on-demand lookup when Agent K doesn't have them. It confirms the cost first, shows how long the lookup has been running, and writes what it finds onto the LeadConnector contact. See Billing.
• See the CRM state of what was found, with Sync now to retry a write that didn't land.
• AI call — your outbound AI agent phones the lead, now or at a time you pick; tell it what the call is about and the recording and outcome land on the contact.
• Text — your SMS agent texts the lead, now or later. Let the AI write it from your context and preview the exact message first, or type it yourself.

Calls and texts Agent K places are named after the lead and linked both ways: the Calls page shows an Agent K lead chip and lists calls awaiting approval under Scheduled, and a texted conversation in Chats carries a Texted by Agent K · Open the lead strip.

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.

If the Feed is empty, it says why — the last hunt's result, a full queue, or something that needs your attention.

Visits and scores

Each visit carries two scores, and the lead pane shows both:

• Engagement — how involved they were: time spent, pages read, and whether they moved closer to buying. It's the same number the session details panel shows, and it's what the Feed's filters and visited badges use. A visit that hasn't been analysed yet shows "Engagement —".
• Lead score — pages viewed, high-intent pages, chats, calls and forms. It updates while they're on the site, and it's the score your automations trigger on.

Hunts

Some accounts find outbound leads through an alternative lead source instead of the standard one — it's switched on per account by the Knock Knock team; contact support. On it:

• Agent K runs one hunt a day, two hours before your working hours open (7am if you have no hours set, or are closed that day), so the day's leads are waiting when you start. A search takes a few minutes and its leads land in your queue within minutes of it finishing.
• The hunt is built from your ideal customer description — or, once you've calibrated, the written description you saved. Each new search leaves out everyone your earlier hunts already found, so nobody is found or charged twice — and that still holds after you clear your queue.
• Someone the search itself rejected is never added or charged, and someone you marked Not a fit while calibrating is never found again. A person turned away by an earlier hunt is judged again on today's rules if a later hunt finds them.
• A why-now signal is not required. Every lead that fits your ideal customer and country is delivered. A lead with a recent signal carries it as usual; one without a recent signal carries none — no kk_why_now, why-now note or signal: tag is written, so your workflows never claim a reason that isn't there.
• Every lead found is charged, with or without a signal (see Billing).
• If the alternative lead source can't take a search (it's out of capacity), that hunt — and new-business owner lookups — run on the standard lead source instead, under its rules: only leads with a why-now signal, charged per search.

These accounts get a Hunts tab on the Agent K page listing every hunt (Daily hunt, Manual hunt, or Calibration round for the sample searches you ran while calibrating; Searching, Done, or Stopped). Open one to see:

• Findings in plain English about your ideal customer description — which check turns most people away and which setting to change, overlap with earlier hunts, or a pool that's drying up — plus the funnel: People checked → Passed every check → New to you → Sent to your feed.
• What Agent K looked for — your ideal-customer chips, the Exact search instructions, and how many matching people remain, with Edit ideal customer →.
• Why people were rejected — rejections grouped by the check they failed; click one to filter the list.
• Every lead this hunt found, filterable All, Kept, Rejected, Found before — each with a one-line verdict and the full reasoning, confidence and evidence.

A lead that passed every check but didn't reach your feed says why in plain words, never as a rejection:

• Cleared from your queue — queued, then cleared (from the Danger zone) before it was released.
• Not in the queue — there's no record of it in Agent K's queue; it either couldn't be saved or was removed since.
• Re-queued later — this hunt turned them away under an older rule; a later hunt judged them again and queued them.
• Turned away before — an earlier hunt already checked and turned them away.
• A turned-away lead shows the reason from the hand-off step — Already in your CRM, Do not contact, Contacted recently, No email or phone, Couldn't tag contact, and so on — and leads turned away for having no buying signal say No buying signal (old rule), since that rule no longer applies on this lead source.

These sit under All only.

Leads

The Leads tab is your call list: every lead Agent K delivered, one row per person, ranked by who is best to phone right now — with the period report on top. (Old links to the Reports or Hot leads tabs land here.)

Period and stage tiles. Pick Today, Yesterday, Last 7 days, Last 30 days (the default), or All time. The tiles count what happened in that period:

• Found, Delivered, Emailed (send mode only), Visited site, Replied, and Booked — the last three also show a percentage of Delivered.
• Visited site means recognized on your site in the period — from their email link or KnockID. Booked includes calls you logged as a booked meeting.
• On All time, Delivered equals the All leads count below; Found always covers Delivered.
• Click a tile to narrow the list to exactly the people it counted (click again, or the × on the filter chip, to clear). If some of them can't be listed because they aren't linked to a contact record, the chip says how many.

An empty period says so plainly — "Nothing happened in last 7 days" — with Look at all time →.

The list. A line above it says how many hot leads are waiting for a call, and how many haven't had an SMS or AI call yet.

• To call — hot (an engagement score of 70 or more), not yet closed out by a logged call, and on your site in the last 30 days. Older hot leads stay under All leads.
• Called — leads with a logged call. All leads — everyone delivered, including people who never visited.
• Chips: Has phone, No SMS / AI call yet, Visited in last 24h. Search name, email, phone, company.
• Sort: Best to call (the default) ranks someone on your site now first, then by score, with older visits counting for less. Also Engagement, Most visits, Time on site, Most recent visit, and Newest delivered.
• Export CSV downloads the rows on screen, as filtered and sorted.

Each row shows the lead (with On site now, their call outcome or attempts, the why-now signal and the pages they read), their phone, email and LinkedIn with a copy button — or Find phone when there's no number — then Engagement, Visits (with time on site), Last visit, and the SMS / AI call already placed (Not contacted if none). A lead who hasn't been to your site says "Hasn't visited your site yet" with when it was delivered. Someone Agent K delivered more than once (a returning visitor is re-delivered after the contact cooldown) is still one row, with every call merged.

The lead. Click a row to open it beside the list (over it on narrow screens; j / k move through the list, Esc closes). It's the Feed's contact pane with three cards on top:

• Why call now — on your site now or when they last visited, visits and time on site, the pages they read, and the why-now reason.
• Journey — when they were Delivered, Emailed (send mode), made their First visit, Replied, and Booked, with Open contact in your CRM →.
• Log the call — pick No answer, Left voicemail, Spoke, interested, Booked meeting, Not interested, or Wrong person / bad number, add optional notes, and Save outcome. No answer and voicemail keep the lead on your list; anything else closes it out. Not interested and Wrong person also stop Agent K contacting them (they go on the Do-not-contact list) and tag the CRM contact nextlevel call:not-interested or nextlevel call:wrong-person, so your workflow can drop them from its sequence. Every logged call is written as a note on the CRM contact.

Report details. Collapsed under the list: where leads came from (by signal), what you'd have missed — Worked after hours, Forgotten leads revived, and Recognized the second they clicked — and leads found per day.

Replied counts replies to every touch, including emails your own LeadConnector workflow sent after a push. Delivered leads are also added to the Identity Graph the moment they're pushed.

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

Click Configure on the Agent K page, or go to Settings → AI Agents → Agent K. Settings are organized into ten tabs:

Overview

• The status toggle — Agent K is on the lookout when on; Agent K is paused when off (no new searches, lookups or outreach).
• What Agent K costs — the pricing table and your wallet balance.
• Weekly digest — Send the weekly digest plus Send it every (default Monday). Quiet weeks send nothing.
• Danger zone — empty the inbox's To review queue for a clean slate. Pick which leads to clear — Every waiting lead, Re-engaged CRM leads, Outbound prospects, or Website visitors — and the count shows how many are waiting and how many more are queued behind them. Delete them asks for confirmation, then deletes those leads and the prospects queued behind them for good. What Agent K already sent is untouched, and a hunted prospect is never offered again.

Signals

What Agent K watches for — nothing to switch on or off. The combinations it ranks highest (a forgotten lead back on your site, an email click followed by time on your key pages, an ideal-customer fit with a fresh reason, a brand-new business of your kind, a prospect Agent K found visiting your site), and the full list it's Always watching: website moments (these follow what's on under Your traffic), hiring and expansion, brand-new businesses, funding and new tools, and second chances from your CRM.

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 (Answer them), and shows Agent K understood this as removable chips — Industry, Geo, Country, Title, Seniority, Keyword, Exclude, and Size. Remove any chip it got wrong. Until Agent K has read the description, outbound hunting is paused; saving reads it too.

Reach meter — under the chips, Agent K estimates how many people your description reaches, live as you edit: ~N people match — healthy reach, narrow, leads will be slow, or too narrow, expect few or no leads, with a few example people. When reach is low it offers one-click ways to widen it — Search all of a wider region, Match any industry wording, or Any company size — each showing the reach it would give. The estimate is free. (On the alternative lead source it's an estimate from a general people database; your hunts search separately.)

If a hunt matched nobody new, the Feed says so with a Calibrate with real leads button.

Calibrate with real leads

Calibrate with real leads (under the reach meter — highlighted when reach is low) checks your description against real people before Agent K hunts with it. It opens a full-screen workspace with four steps — Find, Rate, Adjust, Save — and three panes:

• Your ideal customer (left) — what's being tuned, with Undo. On the alternative lead source this is a written search description you can Edit directly; Agent K writes it from your chips the first time.
• The middle pane — each round's people to rate, latest round first, with Earlier rounds collapsed below.
• The right pane — your chat with Agent K about what to change.

How a round works:

1. Pick the country first. Agent K searches one country at a time, so Country you sell in must be set before Find works — the workspace offers the countries from your locations as one-click choices, or any other. Locations outside that country find nobody, and the workspace offers to Remove them.
2. Find 5 people — the button shows the round's expected price (see Billing). The search runs in the background with live progress — what it's doing, people checked so far, Found so far with a fit score on the alternative lead source, and how long searches like this usually take. You can close the window and come back; a search stops after 30 minutes.
3. Rate each person — Good fit or Not a fit (keys Y / N), with optional reasons, and Why it matched to see the evidence. Open their LinkedIn to check. Good fits per round tracks how each round did.
4. Adjust — click Adjust from my ratings, or just tell Agent K what you want ("bigger teams, no franchises"). It replies with the changes it suggests — Apply these changes (or Use it for a rewritten description) or Ignore. Then Use the suggestion & find 5 more, or Find 5 more without it. Agent K never changes your country — that's always the picker.

Each finished round posts a short summary in the chat — how many people were checked and why the others were dropped. The header shows Spent this session; Start over wipes the session (not while a search is running). Progress is saved, so you can close and pick up later.

When most of a round is a good fit it says this looks right. Review & save shows what changed and how many people you approved; Save ideal customer makes it the description Agent K hunts with from then on. The people you marked Good fit are added to your leads — on the standard lead source, still only once a why-now signal turns up for them — and anyone marked Not a fit is never found or charged again.

After calibrating on the alternative lead source, the Ideal customer tab shows Searching with your calibrated description. Editing the chips switches back to searching from the chips.

Your traffic

• Re-engage your own traffic — A past visitor comes back, Someone is highly engaged on your site, Someone went quiet, Revive forgotten CRM leads (with Consider a lead dormant after, 30–365 days, default 90), and Stay out of the way when they reach out first (on by default — no drafts for visitors who submit a form, book, chat, or call).
• Someone is highly engaged on your site (off by default) — set Engagement score of at least (10–100, default 70). When a known visitor's visit reaches that engagement score, they become an Agent K lead — why-now "Spending real time exploring your site", tagged nextlevel signal:deep-engagement — within your daily limit, and go to your CRM like any other lead (straight away if Push leads automatically is on). Only verified visitors count, never a guess or a bot. For a text, call or anything else, add an automation that starts when a visitor is highly engaged.
• Daily limit — a slider from 1 to 50 (default 10). It's a cap, never a target: Agent K paces releases through the day and holds them during the recipient's night.

Outreach

• How Agent K hands off leads — the hand-off mode and its send-mode controls.
• Push leads automatically (push mode) — see What goes out without asking.
• How Agent K writes for you — Voice & tone, shaping every message it writes (in push mode: LinkedIn messages and suggested replies). The email signature is set in your Assistant settings and shared with Agent K.

Channels

• Email — delivered to your CRM (or sent by Agent K in send mode — through LeadConnector or your mailbox).
• Calls and texts — placed by your rules, on the numbers your agents already use (See your rules →).
• LinkedIn — see LinkedIn outreach.

Delivery

How leads land in LeadConnector — the workflow checklist, Set tracking token on existing contacts, and the tags Agent K adds. See How leads land in LeadConnector.

Automations

Your rules and their activity log now live on the Automations page (Automations | Logs tabs).

Sending

The one place that answers "does this go out without asking me?".

What Agent K sends without asking you — a grid with a row per channel and a column per kind of lead:

	Prospects (people matching your ideal customer, plus forgotten CRM leads if revival is on)	Website visitors (people who've been on your site)
Emails — the first one as soon as it's drafted, and its follow-ups	Ask me first / After they visit / Automatically	Ask me first / Automatically
LinkedIn invites — within your daily LinkedIn limit	Ask me first / After they visit / Automatically	Ask me first / Automatically

• Automatically sends inside your send window in each person's own time zone, and keeps to the daily send cap, the do-not-contact list and the frequency cap.
• After they visit waits until a prospect has been on your website themselves.
• The Emails row only applies when Agent K composes and sends; in push mode your LeadConnector workflows send the emails and the row is greyed out. The LinkedIn invites row needs a connected LinkedIn account.
• Switching emails to Automatically also sends drafts waiting from the last 3 days, up to your daily cap; switching LinkedIn invites also sends invites waiting from the last 14 days, within your daily LinkedIn limit.
• Sending automatically to prospects asks once for I confirm we have consent to contact these people; after that the tab shows the date consent was confirmed.

Below the grid:

• How LinkedIn invites go out — Warm up first — like a recent post, then invite 12–48 hours later (recommended) or Invite right away. Quiet hours, how often one contact is messaged, and the spacing between messages apply to everything that sends on its own, Agent K included — change them on the Automations page under When messages may go out.

Do-not-contact

Do-not-contact list — replies like "stop" or "please don't reach out again" land here automatically, and you can add anyone yourself: type an email or phone under Add an email or phone and click Never contact. Nobody on the list is contacted again — by any agent, on any signal. Remove an entry if it was a mistake.

LinkedIn outreach

Turn on LinkedIn 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:

• Warm up first — like or comment on their post before connecting, for higher acceptance.
• Personalize every request — each request references why Agent K is reaching out, never a template blast.
• Add a note to invites — off sends plain connection requests. LinkedIn allows far fewer invites with a note (about 5 a month on a free account), so turning notes off keeps invites flowing.
• Invite usage — once connected, a panel shows your invites in the last 7 days and notes in the last 30 days against your LinkedIn account type's published limits, plus Agent K's own daily cap and how many of this week's invites came from Agent K.
• A reply stops the sequence for that lead immediately, same as email.

LinkedIn invites wait in your review list unless you set LinkedIn invites to Automatically on the Sending tab. On a waiting invite, Send without note sits next to Send (it asks Send the invite without a note? first) — useful once LinkedIn has stopped accepting notes from your account. If invites already go without a note, the lead says so and the extra button is hidden. Invites are capped per day and pause automatically if too few are being accepted.

LinkedIn billing

The connected LinkedIn seat is charged when you connect and then monthly from your Wallet. If the Wallet can't pay at renewal, the LinkedIn account is disconnected immediately, with an email telling you why — keep the Wallet funded ahead of the renewal date. Top up and reconnect to resume. Switching the channel off only pauses outreach — the seat stays connected and billed until you Disconnect. LinkedIn activity (likes, invites, messages) is totalled daily and taken from your AI credits.

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 lead without a recent signal gets no kk_why_now.
• 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. Agent K writes kk_token onto the contact before it adds the nextlevel agent-k-lead tag, so a workflow triggered by the tag never sends with a blank token. (In send mode Agent K's own links carry the token automatically, and so do the emails your rules and bulk runs send.)

Also on the Delivery tab: 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 shows live progress, survives a page refresh, and is safe to re-run.

A visit from a tracked link is credited to whoever created the link: a click on an Agent K email counts as Agent K outreach, a ManyReach campaign click as that campaign, and a click from one of your own CRM emails (a backfilled token) is not labelled Agent K.

Company and website fill native LeadConnector fields automatically. The custom fields for LinkedIn URL and job title are named under Integrations → LeadConnector — see LeadConnector.

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. For emails sent from your mailbox, replies are picked up by its reply tracking, and an unsubscribe click or a bounce stops all email to that person. 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.

Campaign links beyond LeadConnector

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 is pay-as-it-works from your Wallet — no subscription. The pricing table on the Overview tab (and in the window before you switch it on) lists what each action costs your account:

Action	Charged
Finding leads	Per search Agent K runs — or, on the alternative lead source, per lead found, with or without a why-now signal
Revealing a contact	Per decision-maker whose details are pulled
Phone lookup	Per Find phone number, whether or not a number comes back
LinkedIn lookup	Per Find LinkedIn, whether or not a profile comes back
Why-now signal	Per lead that comes back with a real reason to reach out — no signal, no charge (not on the alternative lead source)
New-business filing	Per newly registered business Agent K brings you
LinkedIn account	Per connected account, then monthly while it stays connected
LinkedIn activity	Per like, invite or message — totalled daily and taken from your AI credits, not the wallet

Calibration rounds come out of the same wallet: each person whose details are revealed (a round can reveal a few more than five when some have no contact details), or on the alternative lead source one charge per round for the leads it found. The button shows the expected price before each round; on the alternative lead source the people you approve aren't charged a second time when they're added to your leads. Searches and lookups are charged per attempt, the way the data providers charge. Agent K checks your balance before it spends and pauses itself when the wallet runs out — it never spends past your balance. Every charge appears on your wallet statement under Packages → Wallet. AI calls and texts placed from a lead or a rule are billed like any other call or text.

Next steps

• Automations — rules, workflows and bulk actions that act on Agent K's leads.
• LeadConnector integration — connect the CRM Agent K delivers into.
• Your Mailbox — send Agent K's emails from your own address, or run Agent K with no CRM.
• Wallet — where Agent K's 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.