← Back to templateSupport escalation guideEditable copy on this deviceDownload MarkdownEdit your copy in Markdown# Support escalation guide Identify the right receiving team and preserve the promise already made to the customer. ## When to escalate Issue family: [topic] Escalate when [observable condition] affects [scope]. Owning team: [team and intake channel] Expected acknowledgment: [service window] Example trigger: Two workspace owners cannot complete an export after a retry, and their deadline is today. ## What to include Case reference: [internal link] Observed behavior and time: [facts and time zone] Customer impact: [task blocked and deadline] Already checked: [step and result] Requested help: [specific decision or investigation] ## Who follows up [Support owner] keeps the customer updated by [next promised time]. [Receiving owner] records findings in [case]. If acknowledgment misses [window], contact [backup role]. Close the escalation when [working result] is confirmed by [person or check].