CUSTOMER SUPPORT
Agent: mine the resolved-ticket backlog into a batch of Confluence drafts
On demand, a Paperclip agent works through a backlog of resolved Zendesk tickets, decides which deserve documentation, drafts the articles.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator launches backlog run
- ActionPage through resolved Zendesk viewZendesk
- LogicDecide which themes warrant articles
- ActionDraft articles from grouped ticketsOpenAI
- OutputFile batch of Confluence drafts + indexConfluence
What it does
Stands up an agent to bootstrap a knowledge base from scratch. Pointed at a backlog of resolved Zendesk tickets, the agent reasons about which issues are documentation-worthy, writes the articles, and assembles them into one organized batch of Confluence drafts for editors to triage.
When to use it
Use it as a one-time or periodic catch-up when you have months of resolved tickets and no help center yet. Unlike the per-ticket workflows, the agent makes judgment calls across the whole backlog, deduplicating and prioritizing as it goes, so editors get a coherent starter set rather than a flood.
How it works
- 1An operator launches the run manually, pointing the agent at a Zendesk view of resolved tickets.
- 2The agent pages through the backlog, reading transcripts and grouping related tickets.
- 3It decides which themes warrant an article and which to skip, recording its reasoning.
- 4For each chosen theme it drafts an article via the LLM, merging insights from multiple tickets.
- 5The agent files every draft as an unpublished Confluence page under a single review batch with a summary index page linking them all for the editor.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.