REPRODUCIBLE WORKFLOW SPECIFICATION
Support escalation with Intercom, HubSpot, Linear, and Slack
REVIEWED SEPTEMBER 2, 2026 / NOT A CUSTOMER PERFORMANCE CLAIM
Produce a sanitized escalation packet, connect it to the correct customer and engineering records, and prepare an internal notification without exposing unrelated conversation data.
EXECUTION ORDER
Actions, purpose, and confirmation
- 01Intercom
get_conversationRetrieve the selected support conversation and its current state.
Confirm before reading attachments or broader customer history.
- 02HubSpot
search_contactsResolve the customer identity and relevant account context.
Confirm identity when multiple records match.
- 03Linear
create_linear_issueCreate engineering work only after checking for an existing issue.
Confirm team, priority, owner, and sanitized evidence.
- 04Slack
post_messageNotify the approved internal channel with links to canonical records.
Confirm channel and final text before posting.
Verification checklist
- The support conversation and CRM record refer to the same customer.
- Sensitive customer content is minimized in engineering and chat systems.
- The Linear issue is not a duplicate and links to source records.
- The Slack message contains no unsupported resolution claim.
Known limitations
- This is a reference specification, not a customer outcome claim.
- Identity matching may require human review.
- Support conversations may contain personal or regulated data.
- An escalation does not establish root cause or resolution.
How to run this workflow safely
Begin with discovery and read-only actions, then verify the selected accounts before any write. Ask for confirmation at the step where the workflow becomes externally visible, financial, destructive, or difficult to reverse. Keep the structured result from every action so the final response can separate completed work from skipped, rejected, or failed steps. Retry only operations that are safe to repeat or protected by an idempotency key.