Team workflows / BLOCK KIT JSON
Escalate a support ticket with customer impact, priority, ownership, and the response deadline.
Blank optional fields are omitted. Fallback text updates with your fields.
Approximate Slack rendering. Buttons are visual previews; no actions are sent.
Local validation checks the supported schema. It does not guarantee Slack API acceptance.
Manual editing and validation run in your browser. Opening Slack’s Builder shares the message with Slack.
Support escalation · SUP-1842 CSV export stops at 10,000 rows. Fieldwork Studio needs a complete order export for their month-end reconciliation. The issue is reproducible on the Team plan. Priority: High · customer blocked Customer: Fieldwork Studio Assigned to: Data platform team Response due: Today · 16:00 UTC Escalated by Alex Rivera · Workaround under investigation Open ticket: https://example.com/support/SUP-1842
Download the payload or use this command in your own terminal. Replace the placeholder URL with your Slack incoming webhook. Keep the real URL secret. This tool never sends a Slack message.
curl --request POST \
--header 'Content-Type: application/json' \
--data-binary @- \
'https://hooks.slack.com/services/YOUR/WEBHOOK/URL' <<'SLACK_MESSAGE_JSON'
{
"text": "Support escalation · SUP-1842\nCSV export stops at 10,000 rows.\nFieldwork Studio needs a complete order export for their month-end reconciliation. The issue is reproducible on the Team plan.\nPriority: High · customer blocked\nCustomer: Fieldwork Studio\nAssigned to: Data platform team\nResponse due: Today · 16:00 UTC\nEscalated by Alex Rivera · Workaround under investigation\nOpen ticket: https://example.com/support/SUP-1842",
"blocks": [
{
"type": "header",
"text": {
"type": "plain_text",
"text": "Support escalation · SUP-1842"
}
},
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*CSV export stops at 10,000 rows.*\nFieldwork Studio needs a complete order export for their month-end reconciliation. The issue is reproducible on the Team plan."
}
},
{
"type": "section",
"fields": [
{
"type": "mrkdwn",
"text": "*Priority*\nHigh · customer blocked"
},
{
"type": "mrkdwn",
"text": "*Customer*\nFieldwork Studio"
},
{
"type": "mrkdwn",
"text": "*Assigned to*\nData platform team"
},
{
"type": "mrkdwn",
"text": "*Response due*\nToday · 16:00 UTC"
}
]
},
{
"type": "context",
"elements": [
{
"type": "mrkdwn",
"text": "Escalated by Alex Rivera · Workaround under investigation"
}
]
},
{
"type": "divider"
},
{
"type": "actions",
"elements": [
{
"type": "button",
"text": {
"type": "plain_text",
"text": "Open ticket"
},
"action_id": "ticket",
"url": "https://example.com/support/SUP-1842",
"style": "primary"
}
]
}
]
}
SLACK_MESSAGE_JSONRoute a ticket to the team that can resolve it while preserving the support system as the source of truth. A short problem statement and explicit owner help prevent escalation messages from becoming an unowned queue.
Summarize the issue without exposing the full customer conversation. Set the response deadline from the applicable service agreement and remove it if none exists. Link to the ticket for authorized access to details.
Send from your support platform when a ticket is escalated. The button opens the ticket; assignment, SLA tracking, and replies remain in your support workflow.
To post this JSON, create a Slack app with an incoming webhook for your channel, or use chat.postMessage with the appropriate bot token and permissions. Keep credentials on your server.
For buttons, enable Interactivity and handle Slack’s interaction requests, including URL buttons. Acknowledge requests promptly. This preview does not execute actions, authorize users, or save decisions.
Use the top-level fallback text for notifications and accessibility. Test your final payload in Slack; local validation covers the declared subset, and visual details vary by client.
Slack interaction setup ↗