Skip to content
Service Blueprint templates

Service Blueprint — Customer support ticket

Inbound ticket lifecycle from form submission to resolution survey.

Template previewService Blueprint
Customer Support TicketReported issue → resolution → CSAT captureEVIDPhysicalevidence1Help page2Contact form3Auto-reply email4Agent reply5Resolved email6CSAT surveyCUSTCustomerjourney1Reports issue2Receives ack3Replies to agent4Confirms fix5Rates experienceLINE OF INTERACTIONFRONTFrontstageactions1Show self-servearticles2Acknowledge receipt3Conduct dialogue4Confirm resolution5Send surveyLINE OF VISIBILITYBACKBackstageactions1Suggest KB matches2Tag + route ticket3Investigate +reproduce4Update KB5Roll up CSAT intodashboardLINE OF INTERNAL INTERACTIONSUPPSupportprocesses1Help-centre CMS2Ticketing system(Zendesk)3Internal runbooks +JIRA4Knowledge base5Analytics warehouseNOTES• 41% of tickets are deflected when KB match appears in the form's "before-you-submit" panel.• First-response SLA: 1h (P1), 4h (P2), 24h (P3).

Make it your own.

title: Customer Support Ticket
subtitle: Reported issue → resolution → CSAT capture

evidence:   Help page | Contact form | Auto-reply email | Agent reply | Resolved email | CSAT survey
customer:   Reports issue → Receives ack → Replies to agent → Confirms fix → Rates experience
frontstage: Show self-serve articles | Acknowledge receipt | Conduct dialogue | Confirm resolution | Send survey
backstage:  Suggest KB matches | Tag + route ticket | Investigate + reproduce | Update KB | Roll up CSAT into dashboard
support:    Help-centre CMS | Ticketing system (Zendesk) | Internal runbooks + JIRA | Knowledge base | Analytics warehouse

note: 41% of tickets are deflected when KB match appears in the form's "before-you-submit" panel.
note: First-response SLA: 1h (P1), 4h (P2), 24h (P3).