Support · Tickets to action

Support triage

Cluster bugs and feedback from Zendesk, Intercom, or Linear. Draft replies and issue notes. Do not close tickets without you.

Support is a firehose. Engineering wants themes. Customers want replies that sound human.

What the Bot does

  • Read the queues you name.
  • Cluster themes and severity with ticket links.
  • Draft customer replies and engineering notes. Leave status yours.

Never without you

  • Send customer replies
  • Close or delete tickets
  • Issue refunds

First message

Talk first. The first message is a real task — not a template to configure.

Support triage

Triage this support queue. Themes, severity, draft replies. Do not send or close.

Message Support triage

Tools this job uses

Connect them when the Bot hits a wall. Nothing goes live until you say so.

FAQ

Will it auto-close duplicates?

It flags them. Close stays a human click.

Also hire

Other jobs

Hire for the work. Each Bot is a person in the sidebar.

Gmail without the guilt

Inbox triage

Sort the pile. Draft the replies. Never send. The inbox is still yours.

Churn risk with evidence

Account health

Watch the accounts you name. Flag churn risk with evidence. Do not message the customer until you say so.

A computer, a ticket, a fixture

Bug reproduction

Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.

GitHub and Linear, in English

Shipping updates

What shipped, what is stuck, what needs you. No merge, no deploy.

Hire the first one

Meet your first Bot.

Name, optional job, how it should work. Open the thread. The first message is a real task.

Request an invite