Skip to main content
Platform · Knowledge Base

Publish trusted knowledge for people and automation

Govern sources, articles, collections, permissions, synchronization, hybrid retrieval, citations, provider policy, and rollout through one versioned knowledge lifecycle.

Knowledge Base

Published knowledge with governed retrieval

Governed workspace

Grounded answer preview

How are charges handled after a plan change?

Charges are adjusted from the effective time of the plan change. The next invoice uses the newly selected monthly plan.

Authorized sources

  • Billing adjustments · article version 8Cited
  • Plan changes · article version 5Cited

Source and document permissions are applied before retrieval, ranking, caching, and provider input.

For 01

Knowledge leaders

For 02

Customer-service operations

For 03

Security and governance teams

Knowledge lifecycle

Move verified content from source to authorized answer.

Ingestion, review, publication, retrieval, citation, synchronization, and retirement remain one governed lifecycle.

  1. 01

    Ingest

    Verify the source, scan and parse content, create structured chunks, and prepare a versioned index generation.

  2. 02

    Publish

    Review articles and collections, approve immutable versions, and bind authorized consumers.

  3. 03

    Retrieve

    Filter by authorization, rank evidence, validate citations, and return a grounded or explicitly unsupported answer.

Give every customer-service experience a shared, permission-aware evidence layer while keeping source authority, publication, citations, provider use, and failure behavior explicit.

Knowledge operating model

Give content teams, administrators, agents, and automation one trusted evidence layer.

Separate content authority, retrieval permission, provider execution, and consumer experience while preserving traceability.

01Verified ingestion and sources
Quarantine and verify uploads, synchronize governed connectors, and keep source health visible.
02Articles and collections
Author, review, publish, retire, restore, and bind immutable knowledge versions.
03Authorized hybrid retrieval
Apply tenant, actor, source, and document access before lexical and vector ranking, caching, or provider input.
04Grounded answers and operations
Return validated citations or a safe unsupported state, with reindex, analytics, rollout, rollback, and kill controls.
01

Content lifecycle

Keep every source and published answer tied to a verified authority.

  • Sources and connectors

    Ingest verified uploads, synchronized web sources, and governed connector content.

  • Articles and review

    Draft, review, publish, retire, restore, and version authored knowledge.

  • Collections and bindings

    Publish immutable collections and bind exact versions to agents, automation, and cases.

02

Authorized retrieval

Apply access policy before search, grounding, generation, and caching.

  • Permissions and previews

    Scope retrieval by workspace, actor, role, queue, source, collection, and document.

  • Hybrid search

    Fuse lexical and vector retrieval while retaining ranked evidence and safe filtering.

  • Grounded answers

    Return validated article and chunk citations or an explicit unsupported result.

03

Operate and govern

Keep synchronization, indexing, provider behavior, and content risk visible.

  • Sync and index health

    Monitor sources, retries, traces, reindex generations, activation, and rollback.

  • Retention and legal hold

    Apply governance policy without bypassing publication or authorization boundaries.

  • Analytics and rollout

    Review search, grounding, gaps, consumer outcomes, provider health, rollout, rollback, and kill controls.

Grounded answer

A governed knowledge lifecycle from source to cited answer

OCXCenter separates source verification, ingestion, publication, authorization, retrieval, grounded answers, operations, and rollout so agents and automations use the same approved evidence without bypassing access policy.

Current product boundary

A governed knowledge lifecycle from source to cited answer

OCXCenter separates source verification, ingestion, publication, authorization, retrieval, grounded answers, operations, and rollout so agents and automations use the same approved evidence without bypassing access policy.

Evidence to review

  • Verified ingestion before readability
  • Immutable article and collection publication
  • Authorization before retrieval and provider input
  • Versioned reindex, rollout, rollback, and kill controls
01Verified ingestion and sources
Quarantine and verify uploads, synchronize governed connectors, and keep source health visible.
02Articles and collections
Author, review, publish, retire, restore, and bind immutable knowledge versions.
03Authorized hybrid retrieval
Apply tenant, actor, source, and document access before lexical and vector ranking, caching, or provider input.
04Grounded answers and operations
Return validated citations or a safe unsupported state, with reindex, analytics, rollout, rollback, and kill controls.

Role-specific workflows

Connect authoring, administration, and service consumption.

Product responsibilities stay connected without collapsing administrators, operators, agents, and reviewers into one generic persona.

Knowledge author

01

Create trusted content

Draft, review, publish, maintain, and retire content with clear ownership.

  1. 1Draft from an authorized source
  2. 2Review and approve
  3. 3Publish an immutable version

Knowledge administrator

02

Operate the evidence layer

Manage sources, connectors, collections, permissions, indexing, providers, and rollout.

  1. 1Connect and scope sources
  2. 2Validate retrieval
  3. 3Monitor health and gaps

Agent and automation

03

Use authorized evidence

Search or retrieve contextually, inspect citations, and handle unsupported answers safely.

  1. 1Request relevant guidance
  2. 2Inspect the evidence
  3. 3Use, escalate, or report a gap

Enterprise integration and governance

Define authority, dependencies, and controls before launch.

Review integration boundaries and governance controls together so deployment assumptions remain explicit.

Integration boundaries

  • Source credentials and provider routes remain inside trusted service boundaries
  • Knowledge publication does not replace the authority of source systems
  • Consumers receive authorized evidence and citations rather than unrestricted source content

Governance controls

  • Verified ingestion before readability
  • Immutable article and collection publication
  • Authorization before retrieval and provider input
  • Versioned reindex, rollout, rollback, and kill controls

Connected product family

Continue the customer journey.

Where it fits

Own a clear part of the customer journey.

Start with a bounded responsibility, then connect it to shared context, work, policy, knowledge, and evidence.

01

Unify trusted sources

Ingest verified uploads, synchronized sources, and authored articles through one governed administration workspace.

02

Publish reusable knowledge

Create reviewed article and collection versions that remain immutable for the consumers pinned to them.

03

Ground service answers

Retrieve authorized evidence for agents and automations with validated article-version and chunk citations.

  • One approved evidence layer across agent and automated service
  • Source and document permissions applied before content reaches a provider
  • Visible synchronization, indexing, retrieval, and rollout health

Adoption path

Start with one bounded workflow and expand with evidence.

Sequence configuration, integration, testing, and rollout around measurable service outcomes.

  1. 01

    Inventory sources and authority

    Identify source owners, access policy, update cadence, content types, retention, and publication responsibilities.

  2. 02

    Publish a bounded collection

    Verify representative content, configure permissions and provider policy, test citations, and approve the first immutable version.

  3. 03

    Connect and observe consumers

    Bind Agent Assist and automation, monitor retrieval and unsupported states, and use staged rollout and rollback controls.

Evaluation questions

Resolve these before rollout.

  1. 01Which sources are authoritative, who may publish them, and how quickly must revocation take effect?
  2. 02Which roles, queues, agents, and automations may retrieve each source, collection, and document?
  3. 03What should consumers do when evidence is insufficient, stale, unavailable, or blocked by policy?

Evaluate it as one system

Bring a real knowledge base journey into the walkthrough.

Request a tailored walkthrough