AgentWorks for Software and SaaS companies
Support, sales and release notes, handled by a team that never sleeps.
A support agent sorts the inbox and drafts answers from your docs. A research agent briefs sales on every new lead. Bug reports become clean issues and every release gets notes your customers can read. Your people approve what goes out.
Software and SaaS companies of roughly 10 to 250 people.
The work that comes back every week.
Support inbox
How-to questions, bug reports and billing questions, all in one queue.
Bug reports
Vague reports that need steps, versions and a clean issue before anyone can work on them.
Lead research
Who signed up, what the company does, whether they fit.
Release notes
From merged pull requests and closed issues to notes a customer understands.
Onboarding emails
Helping new customers to the first result in their first week.
Your team
A team of agents, each with one job.
Each agent does one thing well, in your own apps, and asks before it sends or changes anything. You give them their rules. They share the board with your people.
Support triager
Called by the workflow
Sorts every support email, drafts the answer from your docs, and turns bugs into issues.
Drafts and creates issues on its own. Replies to customers ask first.
Ready-madeBug report normaliser
Called by the workflow
Rewrites a vague report into steps to reproduce, expected and actual result, and environment.
Writes the issue on its own. Nothing goes to the customer.
Ready-madeLead researcher
Started by your system
Briefs sales on each new sign-up: company, size, use case and fit.
Researches and updates the CRM. Outreach stays with sales.
Ready-madeRelease notes writer
You ask in chat
Writes customer-facing release notes from the pull requests and issues in a release.
Drafts only. Publishing stays with your team.
Ready-madeWorking together
From a support email to an answer, or a clean bug issue
Starts when a new email lands in your support inbox. One workflow hands the work from agent to agent, and stops where a person needs to decide.
- Every reply to a customer is approved by a person.
- Engineering decides priority on new issues.
- Release notes are published by your team.
Start · Gmail
New email in support@
Attachments come along as files
Agent
Support triager reads it
How-to, bug or billing question
Check
Is it a bug?
Bugs go to engineering, questions get an answer
Agent
Bug report normaliser writes the issue
Steps, expected, actual, environment
Action · Jira
Issue created
Linked to the customer email
Asks first
Support approves the reply
Answer, or a note that engineering has it
Action · Gmail
Reply sent
From your support address
The apps it works in
Gmail
OutlookZendesk
IntercomJiraLinearGitHubHubSpotSlackYour own product can start workflows through a webhook (for example on a new sign-up), and agents can call your API through the HTTP request step or an MCP server.
All 40 appsWhat you need
Webhooks and one email trigger work on Free, so you can try the support flow. More triggers, schedules and team boards need Business.
PricingStart from a ready-made agent.
These are in the product today. Start one and it is waiting in your workspace after you sign up.
Support Inbox Triager
Works your support mailbox: reads what came in, finds the answer in your own knowledge base, tells you which messages you can close with it, and opens a tracker issue for the ones that need engineering.
Use this agentBug Report Normaliser
Turns a messy bug description, a chat message, a screenshot caption, or a rambling email, into a clean, reproducible bug report with steps, expected vs actual behaviour, and a severity suggestion.
Use this agentLead Research Brief
Researches a company or contact before you talk to them: what they do, what changed recently, what your CRM already knows, and how well they match your ideal customer profile.
Use this agentRelease Notes Composer
Turns a raw changelog, commit list, or ticket titles into polished release notes for two audiences at once, a customer-facing summary and an internal changelog.
Use this agentStep by step
Your support desk on one board
Every request becomes a ticket. An agent sorts it and drafts the answer. A person checks it and sends.
WorkflowA research brief for every new lead
When a lead lands in the CRM, a brief on the company and the person is waiting in your team channel.
WorkflowAnswer “where is my order?” emails
The agent reads the question, looks the order up in your system and drafts the reply with tracking.
Questions
AgentWorks for Software and SaaS companies
Runs in the EU. Every action that changes something asks first.
Yes. Put your docs in a knowledge base, or sync them from Notion, Confluence or Google Drive on Business. Answers cite the page they came from.