Skip to content
LIVOI
Dashboard

What if knowledge organized itself?

Open
Open in ChatGPT Open in Claude

When information is found, not searched for

Section titled “When information is found, not searched for”

Every company has knowledge spread across ERP systems, file storage, ticketing systems and project documents. The problem: nobody has the full picture, and many things have to be explained or asked twice.

LIVOI brings these sources together in one agent. Not everything has to be copied: documents are prepared for knowledge search, and the agent queries current data directly in the source system when needed.

Core principle: two kinds of knowledge

Section titled “Core principle: two kinds of knowledge”
Stable knowledge

Manuals, policies, price lists, service reports: files are uploaded, split into sections and vectorized. Knowledge search finds matching passages with source references.

Live data

Stock levels, order status, open tickets: this data changes constantly. A custom tool or an MCP server retrieves it at the moment of the question.

Four ways knowledge reaches the agent
  • Knowledge
  • Custom tool
  • MCP
  • Project tool
  1. 1
    Knowledge Files

    Upload in the dashboard or directly in chat; prepared for knowledge search.

    PDF · Word · Excel · CSV
  2. 2
    Custom tool Your APIs

    Query ERP or CRM over HTTP – configured, not programmed.

    GET /service-reports
  3. 3
    MCP MCP servers

    Use existing MCP servers for storage, tickets or business applications.

  4. 4
    Project tool Project tools

    For systems without a suitable interface, P-CATION builds a connection as part of the project.

Source systems stay unchanged. LIVOI uses the interfaces they provide.

15-second demo: documents and live data in one answer

Section titled “15-second demo: documents and live data in one answer”
User

Please show me the last five service reports for product X.

Custom toolget_service_reports

5 reports from the ERP

Service agent

The last five reports in chronological order:
1. 2026-09-08 – Sensor replacement
2. 2026-09-17 – Calibration successful
3. 2026-09-29 – Maintenance interval notice
4. 2026-10-06 – Software update version 4.1
5. 2026-10-13 – Spare part request closed

User

What does the manual say about the maintenance interval? And is there an open ticket for it?

LIVOI toolrag_search_tool

Maintenance_manual_X.pdf, section 7.2

MCPsearch_issues

1 open ticket

Service agent

According to Maintenance_manual_X.pdf, section 7.2, maintenance is due every 2,000 operating hours. Ticket SUP-118 “Check maintenance interval” is still open.

What changes day to day

Section titled “What changes day to day”
Before
  • Knowledge spread across many systems and folders
  • No unified access or overview
  • Outdated exports instead of current data
After with LIVOI
  • One agent for documents and live data
  • Access in LIVOI Chat, Teams, WhatsApp or via the API
  • Connected through existing interfaces without changing systems

Benefits at a glance

Section titled “Benefits at a glance”
  • One source of knowledge for employees and agents
  • Current data directly from ERP, CRM or ticketing
  • Existing APIs and MCP servers are reused
  • Source references and visible tool calls make answers traceable