A CRM with a knowledge base puts your team's written answers (procedures, fixes, policies) in the same app as your customers, tickets and tasks. For a small business the useful version is an internal knowledge base: short articles your staff search while they're on a call or working a ticket. Start with ten articles drawn from questions you answer every week, give each a named owner, and review them for 15 minutes a month.
The reason to want a CRM with a knowledge base, rather than a separate wiki, is boring and practical: people look things up where they already are. If a technician is inside a ticket and the fix lives in a different app with a different login, they'll message the one person who knows instead. That works until that person is on vacation.
Internal knowledge base or customer help center? Decide this first
"Knowledge base" gets used for two different things, and buying the wrong one is the most common mistake we see in this category.
| Internal knowledge base | Customer help center | |
|---|---|---|
| Who reads it | Your staff | Your customers, publicly or after login |
| Typical articles | How we onboard a client, warranty rules, the fix for a recurring error, who approves refunds | How to reset your password, shipping times, product setup guides |
| Tone | Blunt shorthand is fine | Polished, branded, reviewed |
| Main payoff | Fewer "quick questions" and faster, consistent answers | Fewer tickets in the first place |
| What it needs from the tool | Search, categories, sitting next to customer records | Public pages, theming, search engine visibility, article analytics |
If you sell a product to hundreds of customers who'd happily help themselves, you want a help center, and a help desk platform will usually do it better than any CRM. If you're a service business with dozens or a few hundred clients who call, email or text, the internal version is the one that pays off. Your customers want a person; the knowledge base just makes sure that person gives the same right answer every time.
To be clear about our own product: Argento's Knowledge Base is internal. Only members of the workspace can read it. There's no public help center or customer portal.
Why a CRM with a knowledge base beats a separate wiki (and when it doesn't)
A team wiki in a separate tool is fine when the knowledge is mostly about your company: HR policies, the brand guide, how to book time off. It's weaker when the knowledge is about serving customers, because the article and the situation it's for are in different places.
Keeping an internal knowledge base inside the CRM helps in three specific moments:
- While working a ticket. The customer, their history and the fix are a sidebar click apart. Our guide to a CRM with a ticketing system describes the "write it up the second time" habit that feeds the knowledge base from real tickets.
- During onboarding. A new hire learns the customers and the procedures in the same tool, instead of being sent links to three apps on day one.
- When someone's out. The process for a client's annual renewal, written down once, means the renewal happens even when its usual owner is on leave.
It doesn't help much if your knowledge is mostly long technical documentation with diagrams and version history, or if a large share of your company never touches customers. In those cases a dedicated wiki earns its separate login.
The first ten articles to write
Don't start with a blank page and a brainstorm. Start with the last two weeks of tickets, tasks and "hey, quick question" messages in chat. Anything asked twice is a candidate. For most service businesses, these ten cover a surprising share of daily questions:
- New client onboarding steps. What happens between "signed" and "first job done," in order, with who does each step.
- How we price the common jobs. The rules, not a price list that changes monthly. "Minimum call-out is one hour; anything after 5 p.m. is overtime rate."
- Refunds, credits and warranty. Who can approve what, and up to what amount.
- The three most common problems and their fixes. One article each. These are your highest-traffic articles by far.
- Escalation: when to stop and get someone senior. Specific triggers, not "use your judgment."
- How we set lifecycle stage and lead status. Definitions for each value so the CRM means the same thing to everyone.
- How to log a call or visit. What goes in notes, what becomes a task, what becomes a ticket.
- Where files live. The folder structure in Documents and the naming rule. (Our guide to CRM with document management has a client folder template you can copy.)
- Vendor and supplier contacts. Who to call for parts, licenses or outages, and account numbers that aren't sensitive.
- End-of-month checklist. The recurring admin that gets forgotten when the person who usually does it is busy.
Notice that none of these are long. If an article takes more than 20 minutes to write, it's probably two articles.
An article template that fits on one screen
People read knowledge base articles mid-task, often with a customer waiting. The format should let them find the answer in about ten seconds. This template works for almost any internal article:
Title: [The question, as someone would ask it]
e.g. "Customer says the invoice total is wrong"
When to use: One sentence on the situation.
Answer: The short version in 1–3 lines.
Steps: 1. ...
2. ...
3. ...
Watch out: The mistake people make here.
Owner: [Name] Last checked: [Month Year]Two details matter more than they look. Titling articles as questions ("Customer wants to cancel mid-contract") matches what people type into search. And the Owner / Last checked line at the bottom is what makes the monthly review below possible: anyone reading the article can see whether it's been confirmed recently and who to ask if it looks wrong.
Categories: five or six is plenty
Small teams over-categorize early and end up with eleven categories holding two articles each. Search does most of the finding; categories are just for browsing. A set like this covers most service businesses:
- Clients: onboarding, renewals, offboarding
- Support: common problems and their fixes
- Sales: pricing rules, how stages and statuses are used
- Operations: vendors, month-end, equipment
- Policies: refunds, warranty, escalation
- General: everything else, until a pattern appears
When "General" grows past ten articles, look at what's in it. That's usually where your next real category is hiding.
Example: a six-person bookkeeping firm's first month
Say you run a six-person bookkeeping firm with about 80 small-business clients. The two senior bookkeepers answer the same questions every week: how a new client's bank feeds get set up, what to do when a client sends receipts by text, which clients are on quarterly versus monthly close. Here's how a month of building a knowledge base might go. The firm is an example, not a customer.
Week 1. The owner scrolls back through two weeks of tickets and team chat and finds 14 questions asked more than once. She assigns the top eight to whoever answers each one best.
Week 2. Each article takes about 15 minutes with the template. Four categories: Clients, Monthly close, Tax season, Policies. Software settings that change every quarter stay as links to the vendor's help pages.
Week 3. New rule: answer a question in chat that isn't in the knowledge base, then write it up before end of day. Three articles appear that week from real questions.
Week 4. A junior bookkeeper handles a year-end document request alone using the "Year-end checklist" article while its author is out. That's the payoff.
What they deliberately left out: client portal logins and bank credentials. Those live in the firm's password manager, and the relevant articles say "login is in the password manager under the client's name; ask the owner for access." CISA's guidance on using strong passwords recommends a password manager for exactly this reason: credentials need tight access, and a knowledge base is built to be read by everyone.
Setting up the knowledge base in Argento CRM
The steps are short. Full detail is in the Knowledge base section of the Help Center.
- Open Sidebar → Knowledge Base.
- Select Manage Categories and create your five or six categories before writing anything. It's easier than sorting later.
- Start a new article. Put the question in Article title…, paste the template into the body and fill it in.
- Assign a category and select Save Article.
- To find something, use Search articles… or the category filter. Articles without a category can be moved with Move to General.
One habit makes it stick: give the knowledge base its own channel in Sidebar → Chat, where people post "new article: …" or "this one's out of date." Upkeep stays visible without another meeting. And keep the line between modules clear: contracts, proposals and client files go in Documents. The knowledge base is for how you do things; Documents holds the things.
Using the knowledge base with an AI assistant
This is where having answers inside the CRM starts to pay twice. Argento's MCP server lets Claude (or another MCP-capable assistant such as ChatGPT or Grok) search and list knowledge base articles along with companies, contacts, tickets, tasks, projects and deals. It runs under your own login and permissions, can't delete anything, and logs its actions in a Recent activity panel.
In practice that means you can ask questions that cross both:
- "Pull the full profile for Harbor Street Dental, then check the knowledge base for our year-end checklist and tell me which steps are still open for them."
- "Search the knowledge base for anything about refunds and summarize who can approve what."
- "List this month's open tickets about billing. Which of those questions aren't covered by a knowledge base article?"
That last prompt is the useful one for upkeep: it turns your ticket queue into a to-do list of missing articles. Connecting takes about five minutes; see our Claude CRM integration guide or the Claude section of the Help Center. An assistant is also handy for drafting: paste in a resolved ticket and ask for a first draft in your template, then edit it and save it yourself.
Keeping it current: a 15-minute monthly review
Knowledge bases rarely fail because nobody writes articles. They fail because one wrong article teaches people not to trust any of them. The Consortium for Service Innovation's KCS v6 Practices Guide makes a point worth borrowing even for a tiny team: articles should be fixed by the people using them, at the moment they find the problem, instead of waiting for a scheduled cleanup. Do that, and the monthly review gets short.
Once a month, each category owner spends 15 minutes on this checklist:
| Check | What to do |
|---|---|
| "Last checked" is older than six months | Read it. Still true? Update the date. Not true? Fix or delete it. |
| Someone flagged it in chat as wrong | Fix it today, then reply in the channel. |
| Two articles answer the same question | Merge into one and keep the clearer title. |
| An article mentions a person who's left | Change it to a role ("the office manager"), not a new name. |
| A question came up twice this month with no article | Write it, or assign it. |
If nobody owns a category, nobody reviews it. That one rule matters more than any feature.
When a dedicated knowledge base tool is the better buy
A knowledge base inside a CRM is deliberately simple. You'll outgrow it, or never fit it, if you need:
- A public help center that customers search and Google indexes.
- Approval workflows, where a draft must be reviewed before anyone can see it (common in regulated industries).
- Version history and rollback on every edit.
- Article analytics, such as views, failed searches and "was this helpful" votes.
- Multiple languages for the same article.
If two or more of those are must-haves, buy a dedicated tool and link to it from the CRM. If they're nice-to-haves, the time saved by having answers next to customers usually outweighs them for a team under 20 people.
What it costs
Standalone wiki tools are commonly priced per user, so each new hire costs a little more. In Argento, the Knowledge Base comes with every plan alongside Documents, Team Chat, tickets, tasks and projects. Starter is $25 a month for up to 10 users, Growth is $50 for up to 50, and Scale is $100 for up to 100. There's a 14-day free trial. See full pricing.
If you're weighing how many separate tools a small team really needs, our guide to all-in-one CRM and project management walks through the trade-offs of putting sales, delivery, support and files in one place.
Frequently asked questions
What is a CRM with a knowledge base?
It's a CRM that includes a place to write and search articles, such as how-tos, policies and fixes, in the same app as your customer records. Your team can look up the answer to a customer question without leaving the tool where the customer, their tickets and their history already live.
What's the difference between an internal knowledge base and a help center?
An internal knowledge base is for your own team: procedures, troubleshooting notes and policies that staff use to answer customers. A help center is published for customers to read themselves. Some tools do both; Argento CRM's Knowledge Base is internal only.
How many articles does a small business knowledge base need?
Fewer than you think. Ten good articles covering the questions your team answers every week are worth more than a hundred nobody reads. Start with the questions that come up repeatedly in tickets and calls, and add an article the second time a question is answered.
Should I store passwords or client logins in a knowledge base?
No. A knowledge base is built to be searched and read by the whole team, which is the opposite of what credentials need. Keep passwords in a password manager and have the article say where the login lives and who can grant access.
Can an AI assistant read my CRM knowledge base?
With Argento CRM, yes. Once Claude or another MCP-capable assistant is connected through Argento's MCP server, it can search and list knowledge base articles alongside companies, contacts, tickets, tasks, projects and deals, under your own permissions.
Does Argento CRM charge extra for the knowledge base?
No. The Knowledge Base is included on every plan, along with Documents and Team Chat. Starter is $25 per month for up to 10 users, Growth is $50 per month for up to 50 users, and Scale is $100 per month for up to 100 users.
Keep your answers next to your customers
Companies, contacts, tickets, tasks, projects, documents, an internal knowledge base and team chat in one workspace, with flat pricing from $25/month for up to 10 users. 14-day free trial.
Start your free trial