Glossary
Canonical terminology for all public documentation. Every doc uses these exact terms — never synonyms, never internal names.
Product & surfaces
| Term | Definition |
|---|---|
| The Sales Ninja | The product: an AI prospecting agent that works on your LinkedIn account — it finds people matching your targeting, sends connection requests and messages, and hands you warm leads to close. |
| Your agent | The AI worker attached to your LinkedIn account. One agent per LinkedIn account. It works in the background — you don't need to keep any tab or app open. |
| Your Ninja | The in-app chat assistant — how you talk to your agent. Ask it anything about your account, your leads, or your results; use it to change targeting, adjust rules, set your sending volume, and add a lead by hand. |
| Dashboard | The home tab: your four funnel graphs, your agent's status, and daily activity. |
| Leads | The tab listing every person your agent has contacted or ruled out, with their current pipeline stage. |
| Flow | An outreach campaign: its targeting (ICP), its sourcing country, its message cadence and its reply settings. Lives in the Flows tab. Starter runs one flow; Pro up to five active. |
| AI assistants (MCP) | An optional connection that lets your own Claude, Codex, or other MCP-compatible assistant use the same tools as your Ninja. Set up in Settings → Connections by signing in; disconnect it there any time. |
| CRM sync | A Pro connection that writes your leads and their milestones through to folk, Twenty, HubSpot, Salesforce or HighLevel. One-way — we write to your CRM, never read from it. Set up in Settings → Connections. |
| Chrome extension | The Sales Ninja browser extension. Used once during setup to securely connect your LinkedIn account, and again if you ever need to reconnect. After setup, the agent works server-side — the extension does not need to stay open. |
Pipeline stages (the five filters in the Leads tab)
| Stage | Meaning |
|---|---|
| Not qualified | Evaluated and excluded — doesn't match your targeting. They stay visible so you can sense-check decisions. |
| Connection sent | A LinkedIn connection request has been sent to this person. |
| Message prepared | They accepted, and the agent has drafted the first message. In review mode it waits for your approval; in auto mode it's queued to send. |
| Message sent | At least one message has gone out to them. |
| Message received | They answered. The follow-up cadence for this person stops immediately. Answering them is yours by default, or your agent's if the flow's Replies block is on auto. |
Sourcing and qualification happen before the Leads tab — a person appears there once they've been invited (or ruled out). The Dashboard's funnel starts at Connection sent; for sourced-versus-contacted numbers, ask your Ninja how your flow is performing.
Concepts
| Term | Definition |
|---|---|
| ICP (Ideal Customer Profile) | The description of who you want to reach: job titles, industries, company sizes, geography, and any custom criteria. Your agent sources and qualifies against it. |
| Lead | A person your agent sourced for you. Every lead sits at exactly one pipeline stage. |
| Sourcing geography | The country a flow searches, picked from a fixed list in the flow's ICP block (Sourcing in). One per flow. Separate from the geography you describe in the ICP text, which is free-form and drives qualification. |
| Replies & meeting booking | The last block of a flow: what happens once a prospect answers. Carries its own review/auto switch and your meeting link. |
| Meeting link | Your booking URL, stored on the Replies & meeting booking block. Your agent shares it when a prospect is ready to pick a slot; with no link it asks for their availability instead. It never confirms a meeting for you. |
| Qualification | The agent's evaluation of a sourced person against your ICP, done before any outreach. Each lead carries the result as a Qualified / Not qualified status you can flip yourself from the lead view. |
| Connection note | The short text that can accompany a LinkedIn connection request. Your Ninja sends requests without a note — blank invites get accepted more often. |
| Cadence | The timed sequence of messages after a connection is accepted. Three LinkedIn messages by default; on Pro it can interleave email steps. A reply from the lead stops the cadence for that person. |
| Review mode | The agent drafts and waits for your approval before sending — at Message prepared for cadence messages, as a Reply to send card for answers to a reply. Set per block, and where every new account starts. |
| Auto mode (auto-send) | The agent sends what it drafted itself, following your rules and limits. Set per block — including the Replies block, which on auto lets the agent answer a conversation until you stop it on that lead. |
| Learned rules | Standing preferences you've taught your agent via your Ninja ("never contact competitors", "always mention our booking link"). They persist across all future outreach and are visible in the Flows tab. |
| Daily allowance | The number of connection requests your agent sends per day. At most 20 — a fixed ceiling, not a default. You can lower it. |
| Invites paused | The Dashboard status meaning LinkedIn has capped invitations on your account. Connection requests stop; messages, follow-ups and sourcing keep running. It clears on its own, usually within a day. |
| Weekly invite limit | LinkedIn's own cap on connection requests per week (roughly 100–200 for most accounts). The window is rolling and per-account — it does not reset on a fixed day. |
| Starter / Pro | The two plans. Starter: one flow, new connections, LinkedIn. Pro: up to five flows, your existing network as a source, email follow-ups, and CRM sync. |