OrthancIQ Integration Guide

Connect the systems where customer value is created, lost, and recovered.

Atlas maintains a live Customer Signal Graph across product, support, billing, CRM, and team context. Brain Engine turns that graph into Customer State Intelligence; Atlas turns the decision into Intervention Intelligence.

Connect OrthancIQ View signal contract
01

Guided OrthancIQ setup

Map the first customer signal path with our team and choose the fastest route to the initial Revenue Intelligence Audit.

02

Atlas Data Agent

Maintain a recurring, read-only signal feed across the customer systems your team authorizes.

03

CSV / JSON first audit

Initialize the first customer-state model from structured exports for usage, billing, CRM, support, and product context.

The shared intelligence boundary

One customer graph. One state model. One operating loop.

Atlas converts fragmented records into live operating context while preserving source lineage, freshness, identity, and permissions. Brain Engine reasons over the same governed graph.

Atlas maintains

  • Normalized customer events
  • Account and user identity resolution
  • Source reliability and freshness
  • Missing-signal and instrumentation tasks
  • Auditable transformation and action history

Guardrails remain explicit

  • No fabricated customer history
  • Brain Engine owns diagnosis and prioritization
  • New tracking requires approval
  • No shared-model training by default
  • Sensitive data stays scoped to approved policy
Customer Signal Graph

The signal contract that powers the intelligence loop.

During private rollout, we provision the tenant, credentials, and exact connection path. The contract below shows the customer signals Atlas normalizes into the live graph Brain Engine uses for state inference and intervention decisions.

AccountsCompany/account, contract value, lifecycle stage, owner, renewal date.
UsersKey people inside accounts: admin, champion, billing owner, workflow owner.
EventsMeaningful product actions, not just logins. Example: workflow run, export, invite, integration connected.
SubscriptionsMRR, plan, renewal timing, cancellation state, seat count, invoice events.
SupportTickets, sentiment, unresolved blockers, cancellation notes, success-manager context.
POST /v1/eventsExample payload
{
  "tenant_id": "tenant_provisioned_by_orthanciq",
  "account_id": "acct_123",
  "user_id": "user_456",
  "event": "workflow_export_completed",
  "occurred_at": "2026-06-08T10:24:00Z",
  "properties": {
    "workflow": "board_report",
    "source": "product",
    "success": true
  }
}

From signal to intelligence to action. Once the first signals are connected, Brain Engine initializes the customer-state model and Atlas opens the first ranked interventions.

Setup sequence

What happens when you connect OrthancIQ.

1

Join private rollout

Tell us your company, MRR range, and which data systems matter.

2

Define data and action permissions

Choose which sources Brain Engine can learn from, what Atlas can retain, and which interventions require approval.

3

Connect customer signals

Use an API, data agent, CSV, JSON, or guided import—whichever gets the first live graph running fastest.

4

Open the first risk cases

Brain Engine infers and ranks the first customer states; Atlas turns them into an actionable Revenue Continuity Queue.

Ready to connect?

Connect the first signal path.

Choose the fastest route to a live Customer Signal Graph, an initialized Brain Engine, and the first Revenue Continuity Queue.

Join private rollout Review permissions