Diese Seite ist noch nicht auf Deutsch verfügbar. Es wird die englische Version angezeigt.

Technology

One owned stack, from the phone line to your ledger.

Vee has built customer-contact technology since 2012: controlled dialogue, design tools, studio voice, analytics and its own telephony. For operations, IT and risk, that means one accountable supplier and a call you can reconstruct step by step.

From design to outcome evidence.

Each technical discipline has a distinct responsibility within one managed contact operation.

  1. Design intelligenceShape the right process and conversation
  2. Execution controlRun authorised behaviour consistently
  3. Operational evidenceUnderstand what actually happened

Built for production, not for demos

48.6M

AI-executed customer cases

Cumulative to 31 October 2026. A case is a business record, not a person or a call.

2,000

Concurrent channels

Reference configuration of the Esense telephony layer, with 300 call attempts per second.

Since 2012

Building dialogue technology

Enterprise production at scale since 2017.

From your case file to a confirmed result.

Cases arrive from your system, run through the five products and return as statuses your system accepts. The result itself is read where it lives: in your ledger, calendar or CRM.

Process flow

6 steps, in order: Your system sends cases by SFTP, CSV or API; Vee DialogJourney holds the dialogue design; Brilliance StateGuard runs the released version; Esense places the call and Vee Lector/UX delivers the voice; Vee Analytics records every attempt and status; statuses return to your system, where the result is confirmed.

  1. Your systemCases sent by SFTP, CSV or API
  2. Vee DialogJourneyDialogue paths, wording and process logic
  3. Brilliance StateGuardThe released version runs state by state
  4. Esense and Vee Lector/UXCall placed, studio voice delivered
  5. Vee AnalyticsEvery attempt, status and recording
  6. Your systemStatuses returned, result confirmed

Your rules run the call. Every step can be reconstructed.

Language models help us design and test dialogue. In production, the released version runs on Brilliance StateGuard, so a regulated conversation follows your policy on the ten-thousandth call exactly as on the first.

  • Brilliance variants range up to fully deterministic execution for regulated processes
  • Answers come from a closed, versioned catalogue; a supplier's model update cannot reach your live call without a tested, approved release
  • AI disclosure is built into every conversation, in line with Article 50 of the EU AI Act
  • Personal data is processed in the EU/EEA; Vee Center Sp. z o.o. is certified to ISO/IEC 27001:2022

What IT and risk ask first.

Does a language model write the answers my customers hear?

Not in regulated processes. Answers come from a closed, versioned catalogue released through Vee DialogJourney and executed by Brilliance StateGuard. Statistical models recognise what the customer means; they do not invent what Vee says.

Which speech and language models do you use?

Own technology, selected components: speech, voice and language-model components are chosen per project for language, latency, privacy and cost. The platform page lists the components by role.

Do we need our own telephony or dialer?

No. Esense provides the servers, numbers and carrier connections. Where you already run a contact-centre platform, Vee connects to it for transfers and statuses.

How much integration does a first process need?

A case file in and statuses back. Most clients start with flat files over SFTP; REST API is available where real-time exchange matters. The integration model adapts to your systems, not the other way round.

Where is data processed?

Personal data is processed in the EU/EEA as a rule; any transfer outside the EEA only under Chapter V GDPR and the agreement. Operations run in Poland, Austria and Germany.

See the stack on your own process.

The Diagnostic maps one process onto the five products: data exchange, dialogue control, voice, telephony and reporting. Your IT and risk teams review the architecture before anything goes live.

  1. Performance Diagnostic

    Typically 2–4 weeks from data access · fixed scope and fee

    We map one process with your team: volume and segments, contact rules, systems, current results and cost, and the measure of success.

    You get Baseline, compliance map, business case and a pilot design you can approve, or a clear recommendation not to proceed.

  2. Controlled Pilot

    A defined period agreed in the Diagnostic

    Vee runs the process on a limited population against a comparable reference, with your rules, quality gates and stop criteria in place.

    You get The metric that matters, confirmed in your ledger, calendar or CRM.

  3. Managed Production

    Ongoing

    Vee operates and improves the process at scale: service levels, Vee Analytics™ reporting, a regular performance review and controlled changes.

    You get One accountable operation, priced per case or account.

No commitment for the process call. The Diagnostic includes an AI Act and data-protection review for regulated processes.

Bring your systems. We will show you the shortest path to production.

Tell us which systems own the case and the result. We will show you what Vee needs, what it returns and how every call can be reconstructed.