Prepare a support escalation brief from Zendesk and Slack
When a ticket needs another team, give the handoff enough context to act without forwarding an unbounded conversation history.
For support leads handing a specific customer issue to an internal team.
What needs to be in place
- In My apps, add Zendesk and Slack, then connect the accounts you want your AI client to use.
- A ticket ID and a Slack search phrase or channel-specific query. Check the matching messages before treating them as related.
In My apps, add the apps listed above and connect the accounts you want your AI client to use. Then connect your AI client to Weavz. A workspace template is optional: it can configure app access and defaults, but your AI client runs the task.
Work through the selected sources
The exact actions available depend on the integrations and actions enabled in the workspace. These steps keep the task bounded to the account and records you selected.
Confirm the customer report
Read the ticket and its relevant comments. Preserve the customer’s own description separately from the team’s diagnosis.
Search the team context
Use a short Slack query tied to the issue or incident. Keep unrelated matches out of the handoff.
Write the internal brief
Summarize verified observations, reproduction details, what is still unknown, and a proposed next owner. Do not claim an engineering cause without evidence.
App actions and developer details
Action names and inputs
These details help when configuring or implementing the task. You can follow the guide without starting from the action identifiers.
zendesk.get_ticketRead the specified ticket and optional comments.
Required inputs:
ticket_idslack.search_messagesFind messages using a bounded search query.
Required inputs:
query
A starting instruction for your AI client
Replace bracketed details with the records and scope you chose. Review the returned result against its sources.
Example instruction
Prepare an internal escalation brief for Zendesk ticket [ticket ID]. Search Slack for [specific issue phrase] and include only messages that clearly match this case. Separate what the customer reported, what our records confirm, and what remains unknown. Suggest a next team or question, but do not assign anyone, create an issue, post to Slack, or reply to the customer.
What the result contains
A compact internal handoff that keeps the ticket and matching team messages visible as separate sources.
Keep the source trail with it
Include the Zendesk ticket identifier and the Slack message permalink or timestamp when the result provides one.
Keep drafts and writes separate
The example is read-only. Creating a Linear issue, posting an escalation, or changing ticket status is a separate write with its own destination and review.
If a source or connection is missing
If Slack search is noisy, narrow the query or ask the support lead for the right channel. If the ticket does not establish the customer impact, leave it as unknown.
Set up the accounts and task
Optional workspace template: Customer Escalation Desk.
Integrations
Includes Zendesk and Slack. The example prepares an escalation brief; it does not send or update records.