Sessions
A session is a conversation thread between you and Knoq. Every time you type a question and hit Enter, you’re either starting a new session or continuing an existing one. Sessions are persistent — Knoq saves the full transcript to your account, so you can close the browser, come back later, and pick up exactly where you left off. Your session history is listed in the left sidebar of the chat interface. You can scroll back through past conversations, share a session link with a teammate (on Team and Business plans), and ask follow-up questions that build on previous context — Knoq carries the thread forward automatically. Each session has a title that Knoq generates from your first message, so your history stays scannable even after dozens of conversations.Connectors
A connector is an integration you’ve authorized Knoq to query on your behalf. Knoq supports 20+ connectors — including Slack, Notion, GitHub, Linear, Confluence, Google Drive, Jira, and more. Connectors are authorized via OAuth: when you connect an integration in Settings → Integrations, you’re taken through that tool’s standard authorization flow and Knoq receives a scoped access token. Your credentials are stored encrypted (AES-256-GCM) and never exposed to other users or returned in API responses. You can disconnect a connector at any time from the same settings page, which revokes Knoq’s access immediately. Each connector counts against your plan’s connector limit. Free plans support 2 connectors, Solo plans support 5, Team plans support 15, and Business plans support unlimited connectors.Knoq only queries connectors that belong to your account (or your organization, for shared team connectors). Your data is never mixed with another organization’s.
The Orchestrator
The orchestrator is the engine that runs every time you ask a question. It’s what makes Knoq different from a simple search tool. When you submit a message, Knoq automatically figures out which of your connected integrations are relevant to the question — a question about a project’s status might search Slack, Notion, and Linear; a question about a code bug might focus on GitHub and Linear. Those integrations are then queried simultaneously, so the full search takes roughly as long as the slowest single tool rather than the sum of all of them. Once results come back from every relevant integration, Knoq reads them together and writes a single, coherent answer — citing the original sources so you can verify every claim. In the chat UI, each search or document fetch Knoq performed is shown as a collapsible step beneath the answer. You can expand any step to see exactly what was queried and what was found, giving you full transparency into the reasoning.Verified Answers
Verified answers are admin-curated Q&A pairs that Knoq injects into relevant responses. When your question closely matches a verified answer, Knoq surfaces it with a verified badge alongside (or in place of) the live orchestrated answer. Verified answers are useful for high-stakes or frequently-asked questions where you want to guarantee the response is accurate and approved — things like security policies, legal disclaimers, escalation procedures, or canonical “how we do things here” explanations. Admins create and manage verified answers from the admin dashboard. When a verified answer is shown, Knoq still runs the orchestrator in the background so you can see supporting evidence from your live integrations alongside the curated response.Verified answers are available on Team and Business plans.
Agent Memory
Agent memory lets Knoq remember facts about you across sessions. Rather than re-explaining your context every time — your team, your role, the project you’re focused on, your preferred terminology — you tell Knoq once and it carries that context forward automatically. For example, if you tell Knoq “I’m on the infrastructure team and I own the database reliability work,” it stores that as a memory entry and uses it to make future answers more relevant — surfacing infrastructure-related Notion pages before marketing ones, or pre-filtering GitHub issues to your area. You can view, edit, and delete all memory entries at any time from Settings → Memory. Knoq will never act on a memory entry you’ve deleted, and memory is scoped to your individual account — it is never shared with other members of your organization.Write-back
Write-back lets you save an AI-generated answer directly to a Notion or Confluence page without leaving Knoq. When you receive an answer you want to preserve as living documentation, click the write-back option in the chat toolbar, choose the destination page or parent section, and Knoq creates or updates the document on your behalf. Write-back is useful for turning ad-hoc Q&A into permanent runbooks, summarizing a long Slack discussion into a Notion decision record, or keeping Confluence pages up to date with information Knoq has synthesized from across your tools.Write-back requires the destination connector (Notion or Confluence) to be connected with write permissions. It is available on Team and Business plans.
Query Packs
Your plan includes a fixed number of queries per month — 10 on Free, 500 on Solo, 5,000 on Team, and 10,000 on Business. If you use up your monthly allocation before the reset date, Knoq will let you know and stop accepting new messages until the next billing cycle. Query packs are additional bundles of queries you can purchase to extend your quota within the current month without upgrading your plan. They’re designed for months when your usage spikes — during a big project, an all-hands research push, or an incident response — without requiring you to commit to a higher tier permanently. Query packs are available on Solo plans and above. You can purchase them from Settings → Billing at any time. Unused queries from a query pack roll over only until the end of the current billing period.For a full breakdown of what’s included on each plan — including connector limits, member seats, SSO options, and enterprise features — visit the pricing page at knoq.one/pricing.