Skip to main content
The Service domain exists to help teams deliver consistent, fast, and well-documented customer support. It brings service reps, service managers, and field engineers into one shared surface where every case, interaction, and escalation is visible and traceable.

​
Operating Model

Service teams operate on queues, tiers, and SLAs. The Service domain reflects this: cases are triaged into priority order, escalations preserve full context, and SLA timers are visible from the queue. The domain is not a standalone helpdesk. It is a projection of the Spine Fabric that unifies Zendesk, Salesforce, Freshdesk, Intercom, and Twilio into one context layer.

​
Responsibilities

  • Triage incoming cases and assign them to the appropriate tier or agent.
  • Resolve cases within SLA while documenting interactions and outcomes.
  • Escalate complex cases with full context intact.
  • Collect and act on customer feedback after resolution.
  • Monitor SLA performance and queue health.

​
KPIs

  • First response time per case.
  • Average resolution time by tier.
  • SLA breach rate.
  • Escalation rate and escalation resolution time.
  • Customer satisfaction score (CSAT) per interaction.

​
Non-Goals

  • The Service domain does not handle sales pipeline management. Opportunities remain in the Sales domain.
  • It is not a billing or invoicing system. Subscription issues are surfaced but billing actions belong elsewhere.
  • It does not replace field hardware diagnostics. Engineering tools remain in Engineering.