CUSTOMER SUPPORT
Agent investigates a support escalation and drafts a reproducible bug report
A Paperclip agent reads an escalated Front conversation, autonomously gathers Sentry traces, Datadog logs, and the customer's session timeline.
How it runs
The automated pipeline, trigger to output.
- TriggerConversation moved to Front escalations inboxFront
- ActionAgent reads thread and identifies symptom/timeframeFront
- ActionGather Sentry exceptions and Datadog logsDatadog
- LogicAgent judges evidence sufficiency
- ActionDraft report and file Linear issueLinear
- OutputReply in Front with investigation summaryFront
What it does
Runs an autonomous investigation instead of a fixed pipeline. The agent reads the escalated conversation, decides which signals it needs, and gathers Sentry exceptions, Datadog request logs, and a reconstructed session timeline. It then synthesizes a coherent reproducible bug report with a hypothesis about root cause and files it to Linear.
When to use it
Use for hard escalations where the cause isn't obvious and a static log-pull misses context. Best when you want a first-pass investigation done before an engineer is paged.
How it works
- 1A Front conversation is moved to the escalations inbox (trigger).
- 2The agent reads the thread and identifies the customer, timeframe, and symptom.
- 3It queries Sentry for related exceptions and Datadog for correlated request/error logs around that window, iterating until it has enough to reconstruct a timeline.
- 4A logic step has the agent judge whether evidence is sufficient or whether the report should be marked "needs customer info."
- 5It writes the structured report with steps, environment, evidence links, and a root-cause hypothesis.
- 6It creates the Linear issue and replies in Front summarizing what it found.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect SentryErrors, performance, releases.
- 3Connect DatadogMetrics, traces, log search.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
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.
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.
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.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.