Back to HomeDocumentation
Home/Docs

Documentation

VOCAL Documentation Hub

Explore implementation guidance for ingestion, transcription, analysis, KPI governance, exports, and integrations across the VOCAL platform.

Start Here

Choose your first reference based on your immediate implementation goal.

Start with Architecture

Use the platform architecture page to understand core data flow, layers, and delivery surfaces.

Open Product Architecture

Start with API

For implementation and automation planning, begin with the API overview and workflow model.

Open API Overview

Start with Ingestion

If you are configuring source systems and metadata contracts, begin with ingestion documentation.

Open Ingestion Docs

Start with KPI Definitions

For measurement governance, scorecards, and reporting alignment, start with canonical KPI docs.

Open KPI Definitions

Documentation by Category

Documentation by Role

Developer / Technical Implementer

  • - API Overview
  • - Ingestion
  • - Integrations
  • - Exporting Data

Analyst / BI / Data Owner

  • - KPI Definitions
  • - Exporting Data
  • - Analysis Pipeline
  • - Product Architecture

Operations / QA Manager

  • - KPI Definitions
  • - Analysis Pipeline
  • - How AI Analyzes Sales Calls
  • - Use Case Pages

Executive / Evaluator

  • - Product Architecture
  • - What Is Call Intelligence
  • - API Overview
  • - Call Analytics KPIs

Core Implementation Flow

  1. 1. Understand product architecture and processing boundaries.
  2. 2. Configure ingestion inputs and metadata normalization expectations.
  3. 3. Review transcription and analysis behavior for your use case.
  4. 4. Align KPI definitions and scoring logic to governance standards.
  5. 5. Set up exports and integration pathways for operational systems.
  6. 6. Use API and event-driven workflows to automate downstream actions.

Documentation Principles

  • - Documentation is organized by implementation flow, not by isolated feature pages.
  • - KPI definitions in docs are canonical for governance and scoring interpretation.
  • - Architecture and API terminology should remain aligned.
  • - Outputs should be explainable, auditable, and exportable.
  • - Docs should support both business and technical audiences with clear handoffs.

Featured References

Product Architecture

Canonical system overview and data-flow model.

API Overview

Developer entry point for integration and automation workflows.

KPI Definitions

Governance-first metric and scoring reference.

Analysis Pipeline

Signal detection, processing stages, and findings-to-metrics mapping.

Related Pages