Jimothy
Download
Use case · Support reply drafts

Ticket comes in.
Reply is ready.

Your helpdesk posts each new ticket to Jimothy. A fast model triages it, a stronger one drafts a reply that sticks to your refund and support policies, and after you approve it, the reply goes back to your helpdesk through a webhook.

Set it upDownload Jimothy
WebhookTCK-2291Charged twice for my annual planhelpdesk
Pipeline
  1. Triage Claude API · haiku
  2. Draft reply Claude API · sonnet
  3. Review reply you
  4. Send reply webhook
ReplyTCK-2291billing / urgent · apology and refund, within policySent
Why it holds up

What the pipeline does for you

  • Policies are part of the prompt

    Your refund and support rules go in a pipeline variable that every draft is written against. If they don’t cover a question, the reply says the team is checking.

  • Triage you can filter on

    Every ticket gets a category and urgency like billing / urgent, and the step fails if the model answers in any other shape.

  • Reject with a note

    Say “too formal” or “offer credit instead” and the reply is rewritten with your note, up to three times.

  • Works with any helpdesk

    Tickets arrive and replies leave through webhooks, so Zapier, Make or n8n can connect Zendesk, Help Scout, Intercom or a shared inbox.

Set it up

Four steps, once

  1. Import the Support reply drafts pipeline and write your policies into its variables.
  2. Triggers → Add trigger → Webhook, and have your helpdesk (or a Zapier zap) POST new tickets to it.
  3. Set replyWebhookUrl to a catch hook that adds the reply to the ticket.
  4. Approve replies from the app, the tray or your phone.

Webhooks need Jimothy’s webhook server turned on, and a tunnel such as Cloudflare Tunnel or Tailscale Funnel if the sender is on the internet.

More use cases

Same engine, different jobs

For engineering

Linear → Pull request

Issues → pull requests

Hand off a Linear, Jira or GitHub issue. Agents plan, build and review it, and you approve the PR.

See how it runs →Schedule → Pull request

Nightly maintenance

A schedule updates dependencies overnight, fixes what breaks, and opens a PR only if something changed.

See how it runs →GitHub → Comment

Specs from vague issues

A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.

See how it runs →

Beyond engineering

Schedule → Slack

Weekly product updates

Every Friday the week’s changes become a customer-facing “What’s new” post, ready to approve and publish.

See how it runs →Webhook → CRM

Inbound lead research

Each contact-form lead gets a cited research brief, a fit rating and a first reply before you’ve opened the email.

See how it runs →
Any trigger → anything

Build your own

Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.

Pipeline docs →