Get started

REFERENCE ARCHITECTURE

The platform behind the process.

Business actions sit within a larger architecture of models, state, connectivity, memory and controls.

VOCOMOTIV / SYSTEM MAPInteractive reference architecture
01 / NORTHBOUND — PEOPLE & CHANNELS
Voice / SIPWhatsAppTelegramTeamsWeb / mobileEmail / SMS
Intent · identity · case context
02 / WORKFLOW ENGINE

One case.
One connected process.

BlueprintStateAction
WorkflowRAGQAAnalyzer

Wait · resume · branch · hand off

MCP · OpenAPI · A2A · events
Permitted tool call · event · recorded result
03 / SOUTHBOUND — ENTERPRISE SYSTEMS
CRM / helpdeskHIS / EMR / FHIRBanking / LOSLMS / SISCalendarsPayments / UPI
DATA & MEMORY FOUNDATION
PostgreSQLpgvectorRedisOpenSearchObject store / graph

INSPECT / ORCHESTRATION

State carries the workflow.

The blueprint defines conversation paths, tool actions, waiting steps and escalation. Workflow, RAG, QA and analyzer agents have different responsibilities around the same case.

Read state → choose the allowed step → record the result

Keep runtime placement separate from the choice of hosted or local models.

The technology inventory

01
NORTHBOUND / CHANNELS

Reach the customer

Calls, messages and application surfaces enter the same workflow.

WhatsAppTelegramMicrosoft TeamsSIP / PSTNWebRTC

SMS / RCS · email · web chat · mobile · APIs / SDKs

02
SPEECH + REASONING

Choose the intelligence

Choose speech recognition, reasoning and voice providers around the workflow, language and deployment you need.

DeepgramAssemblyAIElevenLabsCartesiaOpenAIAnthropicAzure AISarvam

Speech recognition → reasoning → voice · realtime speech · provider options · hosted or local inference by configuration

03
SOUTHBOUND / ACTIONS

Connect the enterprise

Use permitted APIs and events to read context and carry out business actions.

KafkaMuleSoftAzure Logic Apps

MCP servers · A2A · OpenAPI · API gateway · webhooks

CRM / helpdesk / calendars / core banking / LOS / HIS & EMR / FHIR / LMS & SIS / payments

04
DATA + MEMORY

Keep the right context

Give workflow state, cache and retrieved knowledge distinct roles.

PostgreSQLRedisOpenSearchMicrosoft Fabric

pgvector · object storage · knowledge graph · organizational memory

05
INFRASTRUCTURE + OBSERVABILITY

Operate the platform

Place the runtime, manage releases and inspect the operation.

KubernetesTerraformGitLabOpenTelemetryGrafanaVault

Customer keys · OIDC / roles · consent · audit / versioning · ELK

Technology ecosystem and AI provider options. Availability, connector actions and data handling depend on the configured workflow and deployment. Provider names do not imply a partnership or that every service runs locally.

Map your systems

SECURITY THROUGH THE STACK

01

Identity at entry

OAuth2 / OIDC · RBAC · tenancy

02

Keys under your control

Customer keys · Vault · scoped credentials

03

Rules around each action

Consent · PII guardrails · permitted tools

04

A record of the operation

Audit · agent versions · human decisions

Review trust & controls
Approved channel / API ingress
Customer-controlled cloud boundaryConceptual placement
KubernetesRuntime placement · not a live server monitor
Agent runtime

Orchestration · state · campaign engine

Connector execution

Permitted enterprise actions

Speech / reasoning placementApproved hosted or local model services
PostgreSQLRedisOpenSearch
DEPLOY & OPERATE
TerraformGitLabOpenTelemetryGrafana
Explicitly reviewed external connections
Telephony · messaging · email · hosted identity · external models if selected

Network routes, identity, data placement and provider connections must be agreed for the chosen cloud configuration. Controls shown here are from the reference architecture; implementation and security evidence are reviewed for your deployment.

START WITH ONE WORKFLOW

Bring your SOP. Let’s map the first process.

Define the task, connect the systems and agree what a useful pilot should prove.

Discuss a workflow pilot