Knowledge base
Save customer language, product facts, campaign context, Slack canvases, and reusable notes so creators and AI assist work from approved source material.
Knowledge
The bot can capture a Slack thread, note, or source and file it under the brand.
Slash SocialCity route checklist and packing notes are reusable for future posts.
Recommended next step: Add to knowledge base✅ Command executed
Founder POV thread needs final context before publishing.
Slash SocialSlash SocialUsing knowledge: City route checklist
No media selected yet
Why it matters
In Slack
The preview below shows how knowledge base appears in Slack — the context, entry points, and next actions your team uses every day.
It makes approved facts, sources, owner, and freshness visible before creators or AI assist use them in public content.
The artifact shows approved source material, owner, freshness, and brand scope so creators and AI assist do not guess.
Owner: product marketing. Source: Slack Canvas launch notes.
Teams can see when source material needs another look.
Approved context can ground drafts, summaries, and reply suggestions.
A product note in a Slack thread, a customer phrase from a call recap, or a campaign canvas can become reusable brand knowledge instead of another message someone has to find later.
Knowledge entries help drafts, briefs, and suggested replies start from the facts, language, and claims the brand has already approved.
Each brand keeps its own source material, so an agency can store one client's proof points without leaking them into another client's draft workflow.
Outcomes
Brand facts, product details, and approved claims live in one source the whole team cites from draft modals.
Creators attach knowledge-base sources to captions so reviewers check claims against governed text.
Updates to a knowledge article log who changed what, so outdated copy is easier to spot before publish.
FAQ
Teams can save Slack messages, canvases, links, notes, files, and campaign context when those sources should inform future drafts or briefs.
No. Knowledge follows brand scope so facts, claims, and customer language stay with the brand that owns them.
Ready when your team is
Start with the workflow that hurts most, then connect the rest of your social operation around it.