Problem 01
Route continuity
Old links continue to explain knowledge ingestion without duplicating product concepts.
Legacy knowledge route
Legacy knowledge pages now point to the approved source library.
The old Knowledges route keeps route coverage while explaining the same governed retrieval model used by the V2 Knowledge Base.
Collect existing materialGroup by support workflowApprove for AuraReview from tickets
Legacy knowledge
older route
knowledge ingestion
Approved source library
retrieval trace visible
Source collections
PDF
Returns policy v2.4.pdf
indexed, 42 chunks
Docs
Help center / shipping
synced 6 minutes ago
URL
status.acme.example/incidents
restricted collection
Tickets
Historical resolved cases
8,420 threads, PII filtered
Retrieval trace
Query
damaged item return window
semantic + keyword
Top source
Returns policy v2.4 / section 3.2
score 0.91
Rejected
Outdated policy v1.9
not approved
Solutions overview
Knowledges
The old Knowledges route keeps route coverage while explaining the same governed retrieval model used by the V2 Knowledge Base.
How it works
older route
01
Collect existing material
Gather help docs, FAQs, policy pages, and uploaded files.
02
Group by support workflow
Separate shipping, billing, product, setup, and internal SOP content.
03
Approve for Aura
Choose what AI can cite and where human review is required.
04
Review from tickets
Use unresolved conversations to improve weak collections.
Problem Replofy solves
Legacy content names should not create a second knowledge model.
Knowledges keeps the old route while pointing to the same approved source library.
Problem 02
Single source model
Docs, URLs, PDFs, and policies all belong to approved source collections.
Problem 03
Reviewable output
Answers and escalations remain tied to retrievable, inspectable material.
Migration path
Legacy knowledge to operating knowledge.
Inventory
01Collect existing material
Gather help docs, FAQs, policy pages, and uploaded files.
Structure
02Group by support workflow
Separate shipping, billing, product, setup, and internal SOP content.
Policy
03Approve for Aura
Choose what AI can cite and where human review is required.
Improve
04Review from tickets
Use unresolved conversations to improve weak collections.
Guardrails
Keep legacy knowledge useful.
01
Avoid duplicate source copies
02
Mark outdated files before ingestion
03
Use specific collections for sensitive policies
04
Review low-confidence tickets weekly
Related pages
See what to read next.
Solutions
Knowledge Base
Upload documents, PDFs, help articles, websites, policies, and process docs so Aura and operators can answer from material the team approves and maintains.
Solutions
Aura
Aura resolves routine cases only when source, confidence, policy, and ticket status line up. Operators can inspect the reason, approve the action, or take over.
Solutions
Chat Inbox
Email, live chat, WhatsApp, Instagram, Facebook messages, and web chat become one operating surface with ownership, tags, summaries, drafts, handoff, and ticket status.
Review knowledge model
Move legacy knowledge into governed source collections.
Keep the route, but make the operating model source approval, retrieval, and review.