Built for Odoo Helpdesk

Your tickets, worked
end to end by AI.

FlowAgent reads every new Helpdesk ticket, drafts an estimate you approve, then does the actual work on your staging server — posting each step back into the ticket. Your customer signs off with one click, and you push it live.

  • Runs on your own Claude account
  • Works in the tickets you already have
  • Nothing reaches production without your click

From new ticket to shipped, in five steps

FlowAgent doesn't replace your Helpdesk. It works inside it, and leaves a note behind every time it moves.

  1. 1

    Connect your Helpdesk

    Paste a token from your Odoo Helpdesk team. New tickets start arriving within a minute, automatically.

  2. 2

    AI drafts an estimate

    Every ticket gets a scoped estimate. Edit it if you disagree — nothing is posted to the customer until you confirm.

  3. 3

    The agent does the work

    A live AI session works the ticket on your staging server: writing code, running commands, with every step visible.

  4. 4

    Your customer confirms

    They get a staging link and a one-click approve button in the ticket. No portal login, no chasing.

  5. 5

    You push it live

    One deliberate click deploys to production. Until then, production credentials are nowhere near the session.

What you actually get

Not a chatbot bolted onto a ticket form — an agent that does the work, with the guardrails a support team needs to trust it.

Estimates you approve first

AI proposes, you decide. The estimate only reaches the customer — and the ticket — once you've confirmed it.

Real work, not suggestions

A full Claude Code session with SSH to your staging box and your repo, working the ticket the way an engineer would.

A complete trail in the chatter

Picked up, estimated, started, staged, confirmed, deployed — each one lands as a note on the Odoo ticket itself.

Your own Claude account

Each workspace connects its own Claude subscription once. Your account, your usage — not a pool metered behind the scenes.

Staging and production, kept apart

Tickets are always worked on staging. Production access is wired in only for the deploy step you explicitly trigger.

Many projects, one workspace

Connect as many Odoo Helpdesks as you run. One account, one Claude connection, every project in one list.

Everything shows up where your team already looks

No second system to check. Every milestone FlowAgent reaches is posted straight into the Odoo ticket's chatter — including the staging link and the approval button your customer clicks.

Connect your Helpdesk

Questions worth asking

Do I have to move my tickets anywhere?

No. FlowAgent works on the Helpdesk tickets already in your Odoo. Your team keeps using Odoo exactly as before — the AI's work simply appears in the ticket.

Whose Claude account does the work run on?

Yours. Each workspace connects its own Claude account once, and every session in that workspace runs on it. There's no shared pool and no per-token resale.

Can it touch production by accident?

No. Ticket sessions only ever get credentials for your staging server. Production credentials are added to a session only when you click "Submit to live", after your customer has confirmed the staging version.

What gets installed in Odoo?

One small addon. It adds an API your Helpdesk team authorises with a token, a few fields on the ticket (status, estimate, staging link) and the one-click confirm page your customer uses.

Can I run more than one Odoo?

Yes. A workspace can hold as many projects as you like, each pointing at a different Odoo Helpdesk, with its own servers and repo access.

Start clearing the queue

Connect a Helpdesk and your Claude account, and FlowAgent is estimating your next ticket within minutes.

Get started