Customer support · Production

One engineer saves ClickUp's support team 917+ hours a month with Zapier MCP ticket triage

The problem

ClickUp's support team handled ~5,000 tickets a month, each requiring 15 minutes of manual context-gathering — pulling from Zendesk, cross-referencing internal documentation, and matching help articles or runbooks — before a rep could type a reply.

First attempt

Traditional Zapier automations (triggers and actions wiring Zendesk to other tools) covered straightforward flows but could not handle workflows requiring unstructured ticket data to be pulled, interpreted by AI, and routed into a rep-ready output.

Workflow diagram · grounded in source

Ticket arrives in Zendesk

trigger

“When a ticket lands in Zendesk, his system pulls the full context”

AI maps context to knowledge base

ai_action

“maps it against ClickUp's internal knowledge base using AI”

Structured summary delivered to rep

output

“The rep gets a structured summary before they type a word: relevant docs, recommended steps, and any related past tickets”

Post-resolution feedback pull

feedback_loop

“After a resolution, Corey's system pulls feedback data and review summaries so team leads can see how tickets are landing without running manual audits”

Reported outcome

Research time per ticket dropped from 15 minutes to about 4 minutes, saving the team 917+ hours per month across 5,000 tickets.
Other teams at ClickUp noticed and started requesting the same system.

Reported metrics

Support hours saved per month917+ hours

Research time reduction per ticket73%

Research time per ticket before and after15 minutes to about 4

Tickets handled per month5,000

Reported stack

Zapier MCPZendesk

Source

https://zapier.com/customer-stories/clickup

Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Research time per ticket dropped from 15 minutes to about 4 minutes, saving the team 917+ hours per month across 5,000 tickets.

What tools did this team use?

Zapier MCP, Zendesk.

What results were reported?

Support hours saved per month: 917+ hours; Research time reduction per ticket: 73%; Research time per ticket before and after: 15 minutes to about 4; Tickets handled per month: 5,000 (source-reported, not independently verified).

What failed first in this deployment?

How is this customer support AI workflow structured?

Ticket arrives in Zendesk → AI maps context to knowledge base → Structured summary delivered to rep → Post-resolution feedback pull.

Research time per ticket dropped from 15 minutes to about 4 minutes, saving the team 917+ hours per month across 5,000 tickets.Other teams at ClickUp noticed and started requesting the same system.