Technology & Software

Customer Success Intelligence

Designed for Customer success manager

Give the customer success manager a defensible account health picture that ties product usage against entitlement, support burden, contract commitments and stakeholder sentiment into a specific renewal or expansion play grounded in the account's own evidence.

Contract TEC-02 · primary aggregate CustomerAccountHealth · mode loading

Decision brief

CSM and manager commitment to the play: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Customer success manager and CS leader

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A 480,000 dollar ARR account renewing in 74 days shows its health score falling from 78 to 54.

Decision to make

Give the customer success manager a defensible account health picture that ties product usage against entitlement, support burden, contract commitments and stakeholder sentiment into a specific renewal or expansion play grounded in the account's own evidence.

Outcome to show

committedPlay gives Customer success manager and CS leader the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Signal consolidation across systems
  2. 2Health scoring with driver attribution
  3. 3Commitment and objection retrieval
  4. 4Play recommendation
  5. 5CSM and manager commitment to the play

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Customer success manager and CS leader verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved CustomerAccountHealth evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Give the customer success manager a defensible account health picture that ties product usage against entitlement, support burden, contract commitments and stakeholder sentiment into a specific renewal or expansion play grounded in the account's own evidence.
Primary aggregate
CustomerAccountHealth
Primary container
customerAccountHealths
Hierarchical key
/tenantId + /accountId
Schema version
1

Sample scenario

A 480,000 dollar ARR account renewing in 74 days shows its health score falling from 78 to 54. The intelligence attributes 18 points to workflow-automation seats sitting at 41 of 300 entitled for two quarters, 9 points to three severity-2 cases averaging 61 hours to resolution in the integrations area, and the remainder to the executive champion going 97 days without contact against a 30-day cadence. It retrieves the onboarding call passage where the customer set a 200-seat activation target by Q3 and drafts a recovery play pairing an enablement sprint with an executive re-engagement, holding back the expansion ask. The CSM commits the play with the cited evidence frozen for the pipeline review.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
customerAccountHealths Primary /tenantId + /accountId Account, UsageFact, SupportSignal, StakeholderRecord, InteractionChunk, AccountPlay

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Account customerAccountHealths /tenantId + /accountId account::{accountId} None
UsageFact customerAccountHealths /tenantId + /accountId account::{accountId}::usage::{periodEndUtc}::{featureCode} None
SupportSignal customerAccountHealths /tenantId + /accountId account::{accountId}::support::{signalTimestampUtc}::{caseNumber} None
StakeholderRecord customerAccountHealths /tenantId + /accountId account::{accountId}::stakeholder::{stakeholderId} None
InteractionChunk customerAccountHealths /tenantId + /accountId account::{accountId}::interaction::{interactionDocId}::{chunkOrdinal} chunkVector
AccountPlay customerAccountHealths /tenantId + /accountId account::{accountId}::play::{playId} rationaleVector

Query patterns