AI answers are only useful when they are grounded in the right knowledge. A model can write a confident paragraph from almost any prompt, but a team usually needs something more specific: an answer that reflects the company's actual product details, support policies, setup instructions, pricing rules, known limitations, and preferred way of explaining things.
That is the role of Team Brain in Aamu.app. Team Brain gives Aamu AI a way to retrieve relevant company knowledge before it answers or drafts. Instead of treating AI as a generic chatbot beside the work, Aamu connects AI to the workspace where the team's knowledge already lives.
This article focuses on Team Brain as a company knowledge layer. For the more specific customer-support workflow with Helpdesk drafts, Livechat, and human review, see the related article: AI customer support with Aamu.app: Team Brain, drafts, and human review.
Why company knowledge matters for AI
Most business questions are not answered well from general knowledge alone. A customer might ask whether a feature supports a certain setup. A teammate might need the current wording for a policy. A support person might need the safest way to explain a limitation. A visitor in live chat might ask how the product works before they decide to try it.
The difficult part is not writing fluent English. The difficult part is knowing what the company actually wants to say.
Without a knowledge layer, teams often work around the problem manually. Someone copies a policy into a prompt. Someone pastes product documentation into a chat. Someone asks AI a broad question and then checks the answer against old docs, tickets, and memory. That can help once or twice, but it does not become a reliable workflow.
Team Brain is meant to reduce that manual context work. The team maintains source knowledge in Aamu, and AI can retrieve the relevant parts when it needs to answer or draft.
What Team Brain is
Team Brain is Aamu's shared knowledge layer for AI-assisted work. It is not just a long prompt and it is not a separate chatbot with its own private memory. It is a way for Aamu to use the team's maintained knowledge as context.
That knowledge can include material such as product explanations, support answers, policy notes, FAQ snippets, public pages, sitemap content, and Aamu Docs selected as knowledge sources. The useful pattern is simple: write down what the team knows, keep it current, and let AI retrieve it when a question needs grounded context.
In Aamu today, Team Brain knowledge sources can be added as Page URL sources, Sitemap sources, Manual FAQ snippets, and selected Aamu Doc sources. Helpdesk projects can also optionally use resolved Helpdesk tickets as knowledge sources when that setting is enabled. Resolved tickets are different from manually selected sources: they come from the support history, so they should be used only when old resolved answers are still useful and accurate.
The important distinction is that Team Brain does not replace judgment. It improves the starting point. AI can answer from better material, but the team still decides what knowledge is allowed, which workflows can use it, and where human review is required.
What can become company knowledge
Good Team Brain source material is explicit and reusable. It should describe the answer clearly enough that another person on the team could use it too.
Useful source material includes:
Product how-to material that explains how features work and where settings live.
Support policies for cancellations, refunds, billing, data retention, account ownership, or escalation.
Setup instructions for email domains, Helpdesk, Livechat, forms, databases, API use, or project configuration.
Known limitations that should be explained consistently instead of improvised every time.
Tone guidance for how the team wants answers to sound.
Reusable support answers that come up often enough to deserve a maintained source.
This is why Docs matter in Aamu. A Doc is not only a place to write. It can become operational knowledge: something the team can edit, search, link to, and use as AI context.
Example: answering a product how-to question
Imagine someone asks:
Can Aamu create reply drafts for support emails without sending them automatically?
A generic AI tool might answer with a guess about how support automation usually works. Team Brain gives Aamu a better route. It can retrieve the relevant Aamu knowledge: AI can generate drafts for Helpdesk tickets and email threads, and sending is a separate explicit action.
A grounded answer can then explain:
Yes. Aamu can prepare reply drafts for Helpdesk tickets and email workflows without sending them automatically. The draft appears in the normal reply editor, where a person can review, edit, and send it. Draft generation and sending are separate actions.
The value is not only that the answer is well written. The value is that it reflects how Aamu actually works.
Example: answering a support policy question
Policy questions are where grounded knowledge becomes especially important. A customer might ask:
If we cancel today, will we be charged again next month?
AI should not improvise a billing policy. The answer should come from the team's actual rules. If the cancellation policy is written as Team Brain source material, Aamu can retrieve that knowledge before drafting an answer.
The team can then decide the right level of automation. A simple informational answer might be safe to draft quickly. An account-specific billing issue may need human review, because someone must verify the customer's actual subscription state.
Team Brain helps with the knowledge. Human review still matters when the answer requires account-specific judgment.
Example: live chat and asking for a human
Live chat is different from a draft workflow because the visitor may see the answer immediately. When Allow AI to answer live chat messages is enabled for a project, Aamu Livechat can use Team Brain to answer common questions from company knowledge.
That works well for questions such as:
Does this feature exist?
Where do I find this setting?
How do I start using Helpdesk?
What does this product term mean?
Can Aamu help with this kind of workflow?
But not every live chat message is a knowledge question. A visitor may ask:
Can I talk to a real person?
That should be treated differently. The visitor is not asking Team Brain for product information. They are asking for a support action: human help. In that case, the right behavior is to route the conversation toward a human support flow instead of continuing to answer from knowledge.
A useful response could be:
Sure. I can ask a human support person to take over this chat. Please add any details that would help them understand the issue.
This is where Team Brain and intent routing have different jobs. Team Brain helps answer knowledge questions. Intent routing helps recognize that the visitor wants a different action, such as asking for a human.
Separately from Team Brain answers, the live chat widget may also have an email fallback when live support is not available. That is a widget or workflow behavior, not the same as an AI intent where the visitor asks the assistant to email them later.
How Team Brain differs from a generic chatbot
A generic chatbot can be useful for brainstorming, rewriting, or explaining public information. But company work usually needs a narrower answer: what does this team know, what has this team decided, and what should this team say?
Team Brain is different because it is connected to maintained workspace knowledge. The team can improve the source material when an answer is weak. A repeated question can become a Doc. A Doc can become Team Brain context. A support answer can become more consistent over time.
That feedback loop matters. If AI gives a poor answer from vague or missing knowledge, the fix is not only to edit the generated text. The better fix is often to improve the source knowledge so future answers start from better context.
How to prepare knowledge for better answers
Team Brain works best when source material is written in a way that can actually answer questions. A vague note is hard to retrieve and easy to misread. A clear answer, policy, or instruction is much more useful.
A practical preparation checklist:
Write policies as direct answers, including exceptions and escalation rules.
Keep product instructions current when settings, names, or workflows change.
Turn repeated support replies into maintained Docs or snippets.
Separate public-facing answers from internal-only notes when the distinction matters.
Include examples of the tone and level of detail the team wants.
Review weak AI answers as signs that the source knowledge may be incomplete.
The goal is not to write perfect documentation for its own sake. The goal is to create knowledge that the team and AI can both use.
Where human review still matters
Grounded knowledge does not make every answer safe to send automatically. Some questions involve account-specific facts, money, legal commitments, security, data deletion, customer emotion, or unclear context. Team Brain can help retrieve relevant material, but a person may still need to decide what to say.
This is why Aamu separates different levels of AI assistance. In Helpdesk and Emails, AI can prepare drafts for human review. In Livechat, AI answers can be enabled for real-time questions when the team has prepared the knowledge and accepts that level of automation. Asking for a human should be recognized as a different intent from asking a knowledge question.
Good AI support is not just fast. It is fast where speed is safe, careful where judgment matters, and honest about when a person should take over.
The bottom line
Team Brain makes Aamu AI more useful by connecting answers to company knowledge. Instead of asking AI to guess from a broad prompt, the team can maintain the knowledge it wants AI to use: Docs, policies, setup instructions, product notes, reusable support answers, and live chat guidance.
That turns AI from a separate writing tool into something closer to a workspace memory layer. It helps the team answer with better context, keep explanations consistent, notice missing knowledge, and decide which situations should stay human-reviewed.
The practical promise is simple: when your company knowledge is clear and maintained, Aamu.app can help answer from it.