Product Usage Scoring & Routing
All accounts

CorCor Data

corcor-data.example · Customer3 employees · Logistics · Scale
Policy northfield_v1

Product-event timeline

  • Plan utilization observedAug 11, 2026, 12:00 PM
  • Connected serviceAug 9, 2026, 12:00 PM
  • Weekly actives observedAug 9, 2026, 12:00 PM
  • Usage change observedAug 9, 2026, 12:00 PM
  • Viewed pricingAug 9, 2026, 12:00 PM
  • Invited teammatesAug 6, 2026, 12:00 PM
  • Added workspaceAug 4, 2026, 12:00 PM
  • Viewed pricingAug 2, 2026, 12:00 PM
  • Resolved incidentAug 1, 2026, 12:00 PM
  • Account createdMay 15, 2026, 12:00 PM

Scores

fitLow
  • at is a supported geography+10
usageMedium
  • Resolved the first incident in Northfield Incident Management+11.25 / cap 15
  • Additional resolved incident (5 points each, cap 15)+3.75 / cap 15
  • Additional resolved incident (5 points each, cap 15)+3.75 / cap 15
  • Additional resolved incident (5 points each, cap 15)+3.75 / cap 15
  • Additional resolved incident (5 points each, cap 15)+3.75 / cap 15
  • Invited 8 teammates (exclusive band 6to10)+20 / cap 20
  • At least 3 weekly active users+10 / cap 10
  • Customer added a second workspace (2 total)+11.25 / cap 15
intentLow
  • No contributing signals.

Decision

Selected play
Manual review
Owner
GTM Ops
SLA
1 business day
Strongest rejected alternative
Monitor

All evaluated gates

  • hard_blocksNo hard blocks present
  • manual_reviewManual review: No resolved person identity
  • explicit_requestNo in-window explicit sales request
  • expansionExpansion intent 0 < 30
  • acquisition_sales_assistNot a prospect (acquisition is prospect-only); Fit 10 < 70; Intent 0 < 40
  • monitorNot a prospect (monitor is prospect-only); Fit 10 < 70
  • self_serveNot a prospect (self-serve is prospect-only)
  • default_no_sales_actionCustomer below the expansion threshold — monitor for future expansion (no task, existing ownership preserved)

Decisive evidence

  • No resolved person identity

Simulate a bounded signal

One bounded, allowlisted signal. The server maps it to a bounded event, recomputes deterministically, and explains the change — nothing is persisted.

CRM state

Not synced — this evaluation did not request a CRM sync. Sync is a separate, designated action; the decision is revealed independently of any CRM write.