Platform·How it works

Connect, observe,
then let it run.

Perceptive isn't a chatbot you bolt on. It's an orchestration layer that watches every signal across your channels and decides — page by page, call by call — which agent should act, with full audit and human-in-the-loop guardrails.

How it works

Three layers,
one runtime.

The platform is built around shared signals, an orchestration policy, and a typed tool layer your engineers will actually trust.

Layer 01

Shared signals

Every interaction across web, app, email, SMS and voice writes to a single context graph. Agents read each other's notes; the customer never repeats themselves.

Layer 02

Orchestrator

A policy engine routes each event to the right agent based on intent, risk, channel and live business rules — and learns from outcomes.

Layer 03

Tools & guardrails

Agents call your APIs through a typed tool layer with full audit, rate limits, PII scoping and human-in-the-loop checkpoints. Nothing happens by accident.

control vs. agent · 30-day rolling
Integrations

Speaks the
systems you run.

Pre-built connectors for the platforms enterprises actually use. Custom systems plug in via a one-page OpenAPI manifest — no rip and replace.

Connector

CMS

Read & write, scoped credentials, audit on every call.

Connector

CRM

Read & write, scoped credentials, audit on every call.

Connector

Helpdesk

Read & write, scoped credentials, audit on every call.

Connector

OMS / TMS

Read & write, scoped credentials, audit on every call.

Connector

Claims

Read & write, scoped credentials, audit on every call.

Connector

Data warehouse

Read & write, scoped credentials, audit on every call.

Connector

Telephony / CCaaS

Read & write, scoped credentials, audit on every call.

Connector

Marketing

Read & write, scoped credentials, audit on every call.

Deployment & Governance

A workforce of agents.
Run like a real workforce.

You wouldn't hire a thousand contractors with no onboarding, no review process and no audit trail. Perceptive agents ship with the same governance scaffolding your people get — from probation period to performance reviews.

12 wks
From kickoff to full production rollout
3
Independent deployment environments
100%
Auditable interactions, byte-level
4-eyes
Human review required for policy changes
12-week rollout

A measured ramp,
not a vendor swap.

Every customer follows the same four-phase plan, instrumented end-to-end. You'll know exactly what's running, on which traffic, with what guardrails — every week.

Weeks 1–3

Integrate

  • Connect your CMS, CRM, helpdesk, OMS & warehouse
  • Provision a dedicated tenant inside your cloud
  • Map your data model + PII boundaries
  • Joint architecture & security review
Weeks 4–6

Shadow

  • Agents observe real traffic, take no actions
  • Side-by-side scoring vs. your team's responses
  • Tune playbooks & tone of voice
  • Calibrate confidence thresholds per intent
Weeks 7–9

Flagged ramp

  • Live behind a feature flag on a slice of traffic
  • A/B against control, with daily check-ins
  • Human-in-the-loop on every high-risk action
  • Weekly performance review with your team
Weeks 10–12

Production

  • Full traffic, all channels, all hours
  • SLA-backed escalation paths to your humans
  • Monthly business review against your KPIs
  • Roadmap for the next agent in your stack
Governance principles

Six rules
every agent obeys.

These aren't aspirations — they're enforced by the runtime. Every agent message and every tool call passes through the same policy layer.

Principle 01

Typed tool layer

Agents can only call functions you've explicitly exposed. Every parameter is type-checked, rate-limited and audit-logged. No SQL escape hatches, no shell access.

Principle 02

PII scoping by role

Each agent gets a minimum-viable view of customer data, scoped to its task. Voice agents never see medical records; back-office agents never see plaintext payment data.

Principle 03

Human-in-the-loop thresholds

You set the confidence and risk thresholds. Anything above them is auto-routed to a named human queue with full conversation history and recommended action.

Principle 04

Auditable by default

Every interaction stores the model used, the tools called, the policies evaluated and the decision path. SOC 2 auditors get a SQL view of the whole ledger.

Principle 05

4-eyes on policy changes

No single operator can change an agent's behaviour in production. Playbook edits require a second approver from your team — even from Perceptive engineers.

Principle 06

Reversible by design

Every action an agent takes is reversible inside the platform with one click. Refunds, address changes, schedule swaps — your team can undo a day's work in seconds.

Observability

See every
thing an agent did.

A unified ledger captures every prompt, every tool call, every escalation, every cent moved. Stream it to your SIEM, your data warehouse, or your auditor's laptop.

10:42:13 Customer agent → refund authorised £ 42.10
10:42:14 Policy check · refund < £50 · PASSED
10:42:16 Tool · stripe.refunds.create 200
10:42:42 Customer agent → escalating to billing-team human

Security & compliance,
by default.

Perceptive runs in your tenant, on your cloud, with your keys. We don't train on your data.

SOC 2
Type II audited annually
ISO 27001
Information security management
GDPR
EU + UK data residency available
HIPAA
BAA-ready deployments for health
Ready for production

A platform your CISO will sign off on.

Bring our team a security review and an integration list. We'll come back with a deployment plan, scoped to your stack and your risk appetite.

Book a demo