Duual

Architecture

An architecture designed for serious operations.

From channel to result, every layer has one clear responsibility. Everything communicates through governed APIs, events and rules; nothing touches your systems without permissions and traceability.

01

Input sources

Everything that enters the platform: interaction channels, corporate systems, and data. Every source connects through governed integrations, never direct access to production.

  • Channels: WhatsApp, web, app, kiosks and voice
  • Corporate systems: CRM, ERP, billing
  • Master data
  • IoT and telemetry
  • Documents and knowledge
  • External integrations
02

Enterprise interface

Client Command Center

The enterprise layer where your team observes, operates, and governs its instance: every role sees its workspace and every action is audited.

Workspaces

ExecutiveConversationsCustomerTransactionOperationsKnowledgeCampaignAdministrationGovernanceIntelligenceAutomationExperience Design

Transversal capabilities

Unified search · Reports and dashboards · Alerts and notifications · Collaboration · Export and APIs · Personalization

03

Foundational services

Data, events, APIs, rules and observability

Duual Platform

Conversational Engine

Understands intent and context on every channel

Data & Analytics

Identity & Access

Integration Hub

Content & Knowledge

Workflow & Cases

AI & Copilot

Observability & Telemetry

04

Infrastructure and security

The foundation that holds everything, operated 24x7.Multi-tenant with logical isolation · High availability · Encryption in transit and at rest · Backups and recovery · Compliance: ISO, SOC, GDPR

Outcomes

  • Full real-time visibility
  • Evidence-based decisions
  • Continuous experience improvement
  • Efficiency and lower costs
  • Revenue growth and loyalty
  • Governance, risk and compliance

Architecture principles

01

API-first

The interface consumes domain services; nothing accesses your production sources directly.

02

Event-driven

Interactions, transactions, and changes emit normalized events for analytics, automation, and audit.

03

Zero trust

Every access is authenticated, authorized, logged, and evaluated in context.

04

Tenant isolation

Data, configuration, secrets, and permissions are isolated per client and per instance.

05

Privacy by design

Minimization, consent, retention, and deletion are part of the model, not an annex.

06

Observability by default

Services, integrations, and automations emit actionable telemetry; every decision is traceable.