1
List recurring questions
Start with repeated tickets, onboarding questions and errors that consume support time.
Business guide
How to create a knowledge base
Turn repeated questions into useful articles that speed up support and create self-service for customers.
Direct answer
To create a knowledge base, identify recurring questions, group by category, write direct articles, publish them in the portal and track unanswered searches to improve content.
8 minBeginner
Knowledge BaseArtigos filtrados
Base de conhecimento
CategoriasGerar com IANovo artigo
buscar: pagamento, prazo, pedido
Todos 42Publicado 28Rascunho 6Interno 8
42
Artigos
1.2k
Views
164
Util
ArtigoStatusUsoAções
Como rastrear pedido
entregapedido
320
94%
Troca e reembolso
pos-venda
74
novo
Nota fiscal e pagamento
financeiro
188
81%
Knowledge base step by step
The animated mockup shows how a frequent question becomes an article, category, portal search and fewer tickets.
AI Article DraftRascunho criado
Editor de artigorascunho IA
Titulo
Como rastrear pedido
Categoria
Entrega
Tags
pedido, prazo
Publico
Portal + time
H2BListaLink
Como rastrear pedido
1. Abra o link enviado no WhatsApp.
2. Confira o status da transportadora.
3. Se o prazo passou, abra um ticket.
Ações IA
Versões
v2 · IA estruturou passos
v1 · pergunta frequente
2
Create simple categories
Organize by themes customers recognize: account, billing, access, product usage or support.
3
Write short, actionable answers
Use a clear title, direct answer, numbered steps and links to next actions.
4
Measure content gaps
Track searches without results, top articles and topics that still become tickets.
Fundamentals, context, and decision
Operational goal
To create a knowledge base, identify recurring questions, group by category, write direct articles, publish them in the portal and track unanswered searches to improve content.
Decision rule
Before opening AbstractOS, gather lead list, sales stage, owner, SLA, conversation history, offer, and qualification rule. Better inputs reduce the chance that AI creates something polished but disconnected from real operations. Configure the flow around one simple hypothesis: prioritize the action that reduces context loss, improves response speed, and creates a verifiable next step. Avoid starting with visual details or automations before validating the core intent.
Quality criterion
Review process owner, next action, SLA, data quality, and pipeline effect. If any of these points are weak, treat the output as a draft and run another iteration before publishing or scaling. Finish by recording lead, company, deal, ticket, task, and support history. This turns the learning moment into operational memory and makes auditing, collaboration, and measurement easier later.
Practical application checklist
- List recurring questions
- Create simple categories
- Write short, actionable answers
- Measure content gaps
- Review result before scaling.
- Register owner and next action.
- Validate the input before asking for another AI generation.
- Compare the result with the original intent.
- Record the decision, owner, and next review.
Metrics and quality signals
- clear owner for each record
- next action created with a deadline
- data useful for reporting and forecasting
- Leads with next action
- Time in stage or SLA
- Conversion by source or owner
- Operational rework avoided
Module field guide
How to create a knowledge base
Use this module when the flow needs to become an operational routine, not just a one-off action. The goal is to leave with a usable artifact, a clear decision, and a recorded next step.
List recurring questions
Before opening AbstractOS, gather lead list, sales stage, owner, SLA, conversation history, offer, and qualification rule. Better inputs reduce the chance that AI creates something polished but disconnected from real operations.
Create simple categories
Configure the flow around one simple hypothesis: prioritize the action that reduces context loss, improves response speed, and creates a verifiable next step. Avoid starting with visual details or automations before validating the core intent.
Write short, actionable answers
Review process owner, next action, SLA, data quality, and pipeline effect. If any of these points are weak, treat the output as a draft and run another iteration before publishing or scaling.
Measure content gaps
Finish by recording lead, company, deal, ticket, task, and support history. This turns the learning moment into operational memory and makes auditing, collaboration, and measurement easier later.
Recommended operating model
- 1Define the main intent of the flow in one sentence: who is affected, which problem is solved, and what action should happen next.
- 2Run it on a small sample first. In AbstractOS, validate the flow, review AI suggestions, and adjust fields, tone, rules, or integrations before scaling.
- 3Compare the result with the expected signals: clear owner for each record; next action created with a deadline; data useful for reporting and forecasting. These signals show whether the module is ready for real use or still a draft.
- 4Document the decision, owner, and next review. This prevents rework when another team member continues the process.
- 5After validation, connect the result with automation, reporting, or a sales playbook so one-off use becomes a process.
Practical example
A SaaS can create articles for password reset, billing update and team invites. Each article reduces repeated tickets and keeps support focused on more important cases.
Common mistakes
- Creating articles that are too long for simple questions.
- Using internal categories customers do not understand.
- Not updating articles when the product changes.
How to do it in AbstractOS
In Business Studio, use the knowledge base to create articles, publish a help portal and connect support learning to self-service.
Create knowledge basePortal PublishNo portal
Publicação no portal
onlineComo rastrear pedido
Publicado no portal e liberado para sugestão em tickets.
on
Portal
-18%
Tickets
320
Views
Salvar
nova versao
Publicar
portal/widget
3
Medir
busca e votos
Portal de ajudapreview público
Buscar ajuda
rastrear pedido
Como rastrear pedido
Artigo · atualizado agora
Prazo de entrega
Artigo · atualizado agora
Alterar endereço
Artigo · atualizado agora
Ticket evitado · artigo marcado como útil
Keep learning
How to organize support in Help Desk
Centralize requests, customer context, SLA and replies to reduce noise and improve response time.
How to automate sales follow-up
Reduce forgotten tasks and repetitive work by creating rules to remind, nurture and reply at the right moment.
How to integrate Business Studio with API and webhooks
Connect operational data to forms, sites, internal tools and external systems without losing traceability.
How many articles should I create first?
Start with 5 to 10 recurring questions. A small useful center is better than a large outdated one.
Should the base be public?
It depends. General content can be public; sensitive instructions should be restricted or adapted.
How do I know if the base works?
Watch for fewer repeated tickets, searches with results and articles that solve questions without human contact.