An agent that reads every support ticket before your team does.
Every new ticket in Zendesk or Intercom is read and grouped as it arrives. Where the answer is already written down, the reply is drafted in the ticket and waits for a name. Where the ticket is a bug, it is filed as a GitHub issue.
What the agent does
It acts behind an approval gate. Reading the ticket, grouping it, drafting the reply and filing the issue needs nobody, and every reply then stops.
- Reads the ticket as it arrives
The new ticket wakes the agent. It reads what the customer wrote and what your team has already told that customer.
- Groups it with the tickets like it
A question your help centre answers, a bug three people have hit this morning and a request nobody has seen before are three different queues. The agent puts the ticket in the one it belongs to.
- Drafts the reply where the answer is known
Where the answer is already written down, in your help centre or in a reply your team sent before, the agent writes it into the ticket as a draft, in your team’s own wording. The draft waits for a name.
- Files the bug
Where the ticket is a bug, the agent opens an issue in your GitHub repository: what the customer did, what happened, and which tickets report it. A bug three people report is one issue with three tickets on it.
The gate sits before a reply reaches your customer. A drafted reply waits in the ticket, and a named person on your support team reads it and sends it. An issue in your own repository crosses no gate.
What it touches
Your agent works in the systems your team already pays for. We connect it to each one, and the spec names every account it needs before you commit to anything.
- Zendesk or Intercom
The new ticket wakes the agent, and this is where it reads, groups and drafts. Every draft waits here, unsent, for a named person.
- GitHub
Where a bug becomes an issue in your own repository, linked back to every ticket that reports it. Your engineers read it where they already work.
Where your agent lives
A person addresses your agent by name in a chat channel. A system wakes it with an event. Both lists are what Flue verifies, so you can check them.
A person reaches it in
- Slack
- Microsoft Teams
- Discord
- Telegram
- Google Chat
- SMS through Twilio
Teams needs one step that Slack does not: an Azure Bot registration and an app password stored in your project. We do that work and quote it as its own line.
An event wakes it from
- GitHub
- Linear
- Notion
- Stripe
- Shopify
- Zendesk
- Intercom
- Resend
- Salesforce Marketing Cloud
What it costs
A job we have not built before is custom work, so this one is priced at the custom door. The numbers below are floors: we read your workflow first, then name one fixed price.
The door says what a custom agent needs from you, and what the month after it goes live buys. How a custom agent is built