Definitions, not marketing copy
This glossary defines the specific architectural mechanisms Voz360 is built on, plus category terms buyers encounter across the industry — not generic marketing copy — in one bolded sentence each, before any narrative expansion.
This glossary defines the specific architectural mechanisms Voz360 is built on, plus category terms buyers encounter across the industry — not generic marketing copy — in one bolded sentence each, before any narrative expansion.
Schema-per-tenant multi-tenancy means each Voz360 customer gets its own dedicated database schema, not a shared table filtered by a tenant_id column — tenant data is isolated at the database level, not just the application layer.
Explore the full definitionThe Voz360 audit log is a hash-chained record of every privileged action: each row is SHA-256 chained to the row before it, written under a row lock, so any tampering breaks the chain and is immediately detectable.
Explore the full definitionVoz360 encrypts tenant data with AES-256-GCM under a per-tenant Data Encryption Key (DEK), and every DEK is itself wrapped by a platform Key Encryption Key using AES-KW (RFC 3394) — no tenant shares another tenant’s key material.
Explore the full definitionAgentic AI refers to AI systems that autonomously plan and execute multi-step actions toward a goal, not just respond to a single prompt — a plain-language definition, and why Voz360 doesn’t currently market itself with the term.
Explore the full definitionA DNC scrub is the process of checking an outbound calling list against Do-Not-Call registries and an internal suppression list before dialing, removing matches so they are never called.
Explore the full definitionA vendor-neutral distinction between three deployment models frequently conflated in marketing — who operates the infrastructure, and where it runs.
Explore the full definitionOne-party and two-party consent laws for call recording vary by jurisdiction — a plain-language explanation of the difference and why the applicable rule is a legal, not technical, question.
Explore the full definitionSTIR/SHAKEN attestation, caller-ID reputation, and number rotation all affect whether an outbound call gets answered, independent of legal compliance.
Explore the full definitionA webhook is an HTTP callback a platform sends the moment a specific event happens, so a downstream system doesn’t have to keep asking for updates.
Explore the full definitionRAG pairs a retrieval step with a generation step — both are required for a system to accurately be called full RAG, a distinction most vendor marketing blurs.
Explore the full definitionNamed-seat pricing charges for every licensed agent; concurrent-agent pricing charges for peak simultaneous usage — a common CCaaS pricing distinction.
Explore the full definitionSOC 2 reports are scoped against up to five trust service criteria — Security, Availability, Processing Integrity, Confidentiality, and Privacy — and only Security is mandatory in every SOC 2 report.
Explore the full definitionNumber pooling rotates outbound calls across a pool of caller-ID numbers rather than dialing from one number, intended to distribute volume and avoid a single number accumulating a poor reputation.
Explore the full definitionWrap-up time (after-call work, or ACW) is the time an agent spends on tasks tied to a completed interaction — logging dispositions, updating records, scheduling follow-ups — before becoming available for the next one.
Explore the full definitionQuestions, answered
Self-contained answers, so the questions a security or procurement reviewer asks first don't require reading the whole page.
Schema-per-tenant multi-tenancy, DEK-per-tenant encryption, agentic AI, DNC scrubbing, deployment models, recording consent, answer-rate optimization, webhooks, RAG, named-seat/concurrent-agent pricing, SOC 2 trust service criteria, number pooling, and wrap-up time are general industry patterns and terms; each definition here explains the pattern or term generically first, then (where relevant) how or whether Voz360 specifically uses it.
Talk to Voz360
Bring your deployment constraints, compliance requirements, and channel mix. We will show you exactly where control lives in the architecture.