Find a customer ticket, prepare a grounded resolution, and add the approved comment or status update. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.
Designed for
Support teams resolving scoped customer tickets
Operating goal
A grounded resolution and one approved ticket update
2 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 2 connected tools with explicit auth and risk levels.
3 guardrails, 2 evals, and 1 harnesses before production use.
Reads the bounded Zendesk scope and prepares the smallest useful action.
Balanced reasoning model
Executes one native Zendesk operation after human review.
Structured output model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for Zendesk Resolution Team.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
Search up to ten agent-visible tickets.
Add one comment and optional explicit ticket status.
Open it in Codelit, refine it with the agent chat, then generate the architecture or product plan from the same workflow spec.
Open in Agent WorkflowReads one Jira project, converts a request into a scoped work item, pauses on the exact fields, creates it once, and returns the Jira issue proof.
Reads one Linear team's queue, turns incident evidence into a concise follow-up, pauses on the exact issue, creates it once, and returns Linear proof.
Find a conversation and post one approved admin reply with a durable receipt. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.