Skip to main content

Apparatus

Common core components and architecture used across the Contacter ecosystem.

CTT Files​

A JSON file containing complete interaction data and metadata.

Main Information​

  • Line in
  • Agent
  • Customer
  • Date and time

Call Information​

  • Unique Call UUID
  • Original voice file name
  • Original sample rate and volume
  • Original tracks
  • Languages (turns, duration, language probability)
  • Speaker overlay information
  • Tags
  • Call summary
  • Call issues

Speaker Information​

  • Languages (turns, duration, language probability)
  • Duration and volume
  • Transcription confidence score
  • Technical transcription metadata
  • Speaker profile

Dialogue Information​

  • Text
  • Duration
  • Speaker
  • Transcription confidence score
  • Volume, start time, and duration
  • Speaker overlay
  • Tags

Incremental Data Enrichment​

  • Transcriber Ingestion – Populates transcription data.
  • Ainter Enrichment – Enriches files with AI-generated data:
    • Speaker profile identification
    • Summaries and issues tracking
    • Custom programmable extensions
  • CTT Version Control – Tracks and manages document history:
    • Supports multi-version information updates
    • Ensures all information is fully versioned and maintained
    • Stores every version with detailed data and metadata
    • Includes comprehensive configuration details per version
    • Supports full version rollback
    • Optional automatic deletion of old versions
    • Optional archiving/moving of legacy version files

Cryptographic Digital Signatures​

  • Secures files using your own keys or Contacter Master Keys
  • Invalidates the digital signature if information is modified externally
  • Offers flexible execution (can operate with or without signatures enabled)
  • Delivers immutable, signed data ready for compliance, technical, and legal backups

Logical Lifecycle Path​

  1. Creation: The first version is generated by the Transcriber or Importer.
  2. Augmentation: Subsequent versions are enhanced and enriched by Ainter.
  3. Ingestion: Data is uploaded to the database by Placer.
  4. Archiving: The final file version is securely backed up.

Configuration Files​

Contacter uses a set of configuration files to define and manage system behavior.

contacter.yaml (Main Configuration File)​

  • DIARIZATION: Configures the speaker diarization process (currently powered by Pyannote).
  • SIGNATURE: Configures cryptographic digital signing features.
  • LEVEL_NORMALIZE: Defines audio volume normalization rules.
  • OVERLAY_CORRECTION: Sets rules for audio overlay detection and correction.
  • MULTIPLE_CHANNEL: Manages multi-track audio processing instructions.
  • WHISPER_MODEL: Defines the specific Whisper model architecture to be loaded.
  • WHISPER_TRANSCRIBE: Configures speech-to-text transcription parameters.
  • WHISPER_PROMPT: Sets custom initial prompts for the Whisper model.
  • WHISPER_REDO: Establishes conditions and thresholds for re-transcribing phrases.
  • DATABASE: Manages database access credentials and connection strings.
  • EMBEDDINGS: Configures vector embedding models and tool parameters.

keys.yaml (Security & Credentials File)​

  • An auxiliary file used to store sensitive API tokens, keys, and passwords securely.

tag.yaml (Tagging Instruction File)​

  • A Cequation file containing conditions to automatically tag calls, individual speakers, and specific dialogue segments.

command_*.yaml (Command Configuration File)​

  • A Cequation file designed to modify or update data and metadata within the CTT file.

ainter_*.yaml (AI Enrichment Configuration File)​

  • A Cequation file combined with structured AI query instructions.
  • Defines system and user prompts for AI processing.
  • Handles AI response parsing and writes the enriched data directly into the CTT file.

placer_*.yaml (Database Mapping Configuration File)​

  • A Cequation file that controls the data upload process to your database.
  • Defines the target database schema structure.
  • Configures data mapping and database ingestion workflows.

Cequation​

Contacter includes a proprietary module named Cequation that allows you to access, manipulate, modify, and transform CTT data for various workflows. With Cequation, you can program exactly how data behaves and is processed across multiple tools in the ecosystem.

Where Cequation is Used​

  • Transcriber
    • Defines the logical conditions and confidence thresholds under which a phrase must be re-transcribed.
  • Contacter
    • Dynamically modifies data within the CTT file, including the automated generation of tags.
  • Ainter
    • Serves two critical functions:
      1. Constructs context-rich dynamic prompts using CTT data and metadata to feed the LLM.
      2. Parses the LLM's JSON output to seamlessly write responses back into the CTT file.
  • Placer
    • Filters and maps specific data points from the CTT file to align with and upload to your target database schema.

How Cequation Works​

  • Structure: A Cequation statement consists of an assignment side (left) and a retrieval side (right). You can retrieve data from either the CTT file or the database, and assign values back to the CTT file or the database.
  • Syntax: Cequation uses Polish (Prefix) Notation. Every operator and operand must be separated by spaces.
  • Example: $call.trust: "{ $call.trust 10 + }"
    • Explanation: This statement retrieves the current value of the call.trust field from the CTT file, adds 10 to it using prefix addition, and assigns the new result back to the same call.trust field.
  • Flexibility: Pre-configured YAML templates with real-world Cequation examples are provided. You can freely modify these YAML files to define custom data management workflows, append new fields, alter existing metadata, and adapt database uploading processes.
  • Traceability: All changes made to CTT files via Cequation are fully audited, tracked, and cryptographically signed. While you have the freedom to modify any data point, an unalterable version history is always maintained.

YAML Cequation Reference​

(Detailed YAML syntax guide to be provided here)

CTT SDK​

To allow deep workflow customization, Contacter provides a powerful Software Development Kit (SDK) that enables developers to programmatically read, validate, and enrich CTT files.files.

Read Structured CTT Files​

  • Access current interaction data and comprehensive metadata.
  • Query and inspect historical file revisions and audit logs.
  • Validate cryptographic digital signatures to ensure data integrity.

Enrich CTT Files​

  • Programmatically generate entirely new CTT files from scratch.
  • Inject new information and AI insights into existing CTT structures.
  • Automatically sign every data modification to maintain security compliance.