Service Domain: How Spine Fabric Assembles Context - Spine Innov Labs

Spine Fabric turns scattered support signals into a coherent Service domain. Cases, interactions, SLAs, and feedback from multiple helpdesk systems are unified into one workbench where reps can see the full customer picture.

Sources and Scopes

Source	Scope	Data Provided
Zendesk	Tickets, macros, satisfaction	Case records, interaction history, feedback scores
Salesforce Service Cloud	Cases, contacts, entitlements	Case details, customer profiles, SLA terms
Freshdesk	Tickets, contacts, solutions	Case queue, interaction threads, solution articles
Intercom	Conversations, contacts	Chat transcripts, customer metadata
Twilio	Calls, SMS logs	Voice and message interaction records

Event Sequence

Ingest — Spine pulls updates via API or webhook from each helpdesk.
Normalize — Cases, customers, and interactions are mapped to the shared Service model.
Enrich — Customer profiles, SLA terms, and prior case history are linked.
Assemble — A rep’s current context (open cases, SLA risks, assigned escalations) is built on demand.
Project — The assembled context is rendered into Case Queue, SLA Dashboard, Customer History, and other views.

When a ticket is updated in Zendesk, Spine Fabric emits an event, refreshes the queue, and may alert Twin if an SLA breach is imminent.