Skip to main content
The Service System Flow describes how Spine Fabric processes raw data from helpdesk systems and turns it into the views and actions practitioners use. It is the backbone of the Service domain.
1

Intake

Spine pulls updates from Zendesk, Salesforce, Freshdesk, Intercom, and Twilio via connectors and webhooks.
2

Load

Raw records are staged with source metadata and timestamps.
3

Normalize

Source-specific fields are mapped to the shared domain model: Case, Customer, Interaction, SLA, and so on.
4

Schema Mapping

The Schema Agent validates that normalized records conform to the Service domain contract. Misclassified items are flagged.
5

Context Assembly

Spine builds rep-specific context by linking cases, customers, SLAs, and prior interactions on demand.
6

Projection

The assembled context is rendered into views: Case Queue, SLA Dashboard, Customer History, and others.
7

OODA

Twin and domain agents observe changes, orient them to the domain model, decide on proposals, and surface actions.
8

Governance

Every proposed action is checked against capability authorization, scope, and approval rules.
9

Execution

Approved actions are dispatched to the target connector for source-system writeback.
10

State Update

The source system confirms the change. Spine emits an event, updates views, and preserves the receipt.