Find your fit
Who it is for
It suits teams whose procedures and answers live across chat, documents and colleagues’ memory. Support teams can collect repeat answers; operations and onboarding teams can give new staff searchable policies, SOPs and assigned reading.
The wiki is the central offer for teams willing to create and maintain their own pages. The Agent is aimed at Slack-heavy teams that want answers and small requested actions in threads, and it does not require buying a wiki plan.
The work it supports
Core capabilities
Build a Kipwise Page with collaborators, formatting and embedded material from other tools. Templates help editors start recurring page types, while version history gives a way to revisit earlier wording after a process changes.
Search the wiki from Slack during a conversation or from a browser extension while working elsewhere. A connected Google Drive source can appear in the same search, and a live Drive file can be embedded on a Page instead of pasted as a static copy.
When a search misses an answer, assign the question to a teammate. Kipwise saves the resulting Q&A so the next person can find it; review recurring questions before adding another long document.
Assign reviewers and intervals to critical content. Reviewers receive reminders, while teammates can request a check or comment on a suspect passage. Start with pages that affect real decisions so maintenance remains practical.
For onboarding or policy changes, use Mandatory Read to assign specific pages and see who has read them. This is a reading record, so test it with a realistic handoff rather than assuming it proves understanding.
Check analytics for searches with no results and highly viewed pages. Those patterns can show where an answer is missing or where a frequently used process deserves a closer review.
Selected Pages can become a customer-facing help center. Separate public material from private operations notes, and check the needed custom domain and branding scope against the chosen wiki tier.
Kipwise Agent is a separate Slack option: a user can request an answer or a task in a thread and the Agent acts within that person’s permissions. Demonstrate its source links, approval behavior and connected-tool access on a harmless example before trusting it with a live record.
Understand the offer
Pricing and getting started
The current knowledge-base page shows Premium at $7 per user per month and Branded at $14 per user per month, each with a 20-user minimum. Premium includes the core editor, templates, version history, Slack and Chrome access; Branded adds SSO, Ask AI, AI suggestions, limited Slack auto-answering and branding options. The page also offers a yearly selection with 10% off, so confirm the billed term and final total.
Enterprise requires a quote and adds custom integrations, identity/access options, regional storage choice and API access. A separate AI Knowledge Suggestions add-on is displayed at $7 per enabled user monthly; clarify how that differs from Branded’s listed AI Auto-suggestions before budgeting for both.
Kipwise Agent is priced separately at $10 USD per user monthly before tax with a three-user minimum and no wiki-plan prerequisite. It includes $5 of monthly AI credit per person plus $2 per user in a shared pool; unused monthly credit does not roll over. When both an individual and shared credit are exhausted, that user pauses until credits are topped up, starting at 20 credits.
Trial terms also differ. The wiki advertises 14 days without a credit card. Agent starts with $2 of credit for seven days on the fast model, or $10 for 14 days with all models for an existing Kipwise customer or paid Slack-plan user. Check which path your workspace qualifies for before planning an evaluation.
Look a little closer
Before you choose
Pilot a small set of real knowledge types: one repeat support answer, one changing SOP and one onboarding page. Ask a teammate who did not write them to find the right answer in Slack and in the browser, then note what was hard to locate.
Assign a reviewer to the changing SOP and test the reminder cycle. Check whether an unanswered question becomes a useful saved Q&A and whether searches with no results reveal a gap worth filling.
If external documentation is needed, publish only a selected non-sensitive Page to a test help center and inspect its public access. Verify any custom domain, branding and permission requirements in the paid plan before putting customers there.
Compare the 20-seat wiki minimum with the three-seat Agent minimum for your team. Request a current quote covering yearly billing, AI suggestions, Agent credits and top-ups; keep a short Agent pilot within its own trial and permissions.
9 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →
