Skip to content
Explore DCS-PIS

THE DCS PLATFORM

The foundation both products share.

Under DCS-PIS and VoiceOS is one platform: a typed model of the business, intelligence that reasons over it, agents that act within permissions, memory that persists, governance that decides what runs, and integrations that connect it to the systems already in use.

Talk to DCSExplore DCS-PIS

Pillars

Six pillars.

Intelligence

Intelligence that shows its working.

  • Metrics

    A metric is a saved definition over the business graph — numerator, denominator, filters, grain, window. One definition, org-wide. Every chart can show how it is computed.

  • Models

    Churn (30/60/90 days), lifetime value, lead conversion, deal win, revenue forecast and anomaly detection. Each retrained on a schedule, monitored for drift, and reported with calibrated confidence.

  • Data Health

    Predictions are withheld — with the reason shown — when completeness, freshness or consistency falls below threshold. A prediction on bad data is worse than none.

  • Causal discipline

    Uplift models, experiments with held-out controls and off-policy evaluation. Until an experiment concludes, the word is “correlated”.

Architecture

Built as an intelligence system, not a chatbot wrapper.

Architecture · simplified
  1. BUSINESS SYSTEMS01
  2. DATA + EVENTS02
  3. BUSINESS CONTEXT03
  4. INTELLIGENCE04
  5. AI MODELS05
  6. AGENTS06
  7. ACTIONS07
  • 01

    APIs

    One versioned API, generated client, a permission on every route.

  • 02

    Integrations

    Every connector implements one contract; every event it emits is declared in a catalogue.

  • 03

    Model infrastructure

    A Model Gateway: application code makes no provider-specific call, and no model is asked to compute a business figure.

  • 04

    Data layer

    Canonical entities and an event stream; row-level isolation enforced by the database.

  • 05

    AI / ML

    Feature engineering from the graph; models with calibration, drift monitoring and promotion gates.

  • 06

    Agents

    A runner, a tool registry, an autonomy engine and a governance layer between every proposal and every action.

  • 07

    Governance

    Classification, grants, budgets, approvals, audit — and a kill switch that fails closed.

Agents

What every agent carries.

Each catalogued agent is defined by:

  • Identity
  • Role
  • Permissions
  • Allowed tools
  • Spending limits
  • Action limits
  • Data access scope
  • Approval requirements
  • Confidence threshold
  • Risk level
  • Audit trail
  1. Level 0

    Read-only

    Pull a report, summarise an account.

    No approval

  2. Level 1

    Low-risk automated

    Log an activity, update a score, tag a record.

    Runs, and is logged

  3. Level 2

    Configurable

    An internal notification, a draft campaign.

    Your organisation decides

  4. Above this line, a person approves
    Level 3

    Financial or customer-facing

    A discount, an outbound email.

    Explicit approval, every time

  5. Level 4

    Highly sensitive

    Never automated, with or without approval.

    Never automated

Six actions exist on no agent: reject a candidate, terminate, change compensation, promote, issue a refund, alter a contract.

  • The approval queue

    A queued action shows the proposing agent, the action and its parameters, expected impact, confidence, evidence, cost — and the reason approval is required. The approver may approve, modify or reject; a modification is recorded and feeds learning.

  • Behavioural monitoring

    Permission checks catch an agent doing something forbidden. Behavioural monitoring catches an agent doing something permitted but unusual — and throttles it to suggestions until a person releases it.

Security & trust

Trust you can inspect.

  • 01

    Isolation

    Each organisation’s rows are separated by row-level security — verified continuously as a non-privileged database role, because the policies mean nothing to a superuser.

  • 02

    Access

    A named permission on every route. Roles. Multi-factor authentication. Sessions revoked immediately on logout, password change or MFA enrolment.

  • 03

    Audit

    An append-only audit log, retained seven years, that outlives the workspace it describes.

  • 04

    Data protection

    TLS in transit. Integration secrets encrypted at rest. Backups encrypted and verified. Erasure and export of personal data on request.

  • 05

    Supply chain

    Dependency, container and secret scanning fail the build.

Not yet: SOC 2, ISO 27001, a third-party penetration test. We say so here because a reviewer will ask, and the full posture — including open items — is available to any prospect’s security team.

Integrations

Connects to what you already run.

  • CRM

    • HubSpot
    • Salesforce
    • Zoho CRM

  • Commerce & payments

    • Shopify
    • Razorpay

  • Finance & HR

    • Zoho Books
    • RazorpayX
    • Keka

  • Communication

    • Slack
    • Exotel
    • Email (SMTP)

  • Advertising

    • Meta Ads
    • Google Ads
    • LinkedIn Ads

  • Generic

    • REST / webhook
    • ERP (REST)
    • Inventory (REST)

Language models are reached through a gateway, not called directly. The provider can change; the product does not.

Evaluate the platform with the people who built it.

Talk to DCSExplore DCS-PIS