OCLT

Comparison

The AI agent options for a Chatwoot WhatsApp inbox

Chatwoot ships an AI add-on. Chatwoot also ships an API for building your own. And then there's what we run: an AI sales agent deployed on top of the same inbox. Three different jobs, wearing the same "AI agent" label. Here's what each one actually does.

Book a teardownSee how we build on Chatwoot

Where it plugs in

Same socket, three different builds.

Chatwoot's Agent Bot API is the actual door here. Every option in this comparison, ours included, goes through it. What changes is who wrote the code behind the webhook, and what job it was written to do.

Register a bot, point it at an inbox, and Chatwoot starts sending it webhook events for every conversation and message. Captain is Chatwoot's own answer built on top of that door. Botpress and Rasa have public integrations that use the same door. Our AI sales agent is a third build on it, one written for sales instead of support and run in production across our deployments, not handed to you as a framework to finish. It sits alongside the rest of what we call the AI Sales OS.

Side by side

Where they actually differ.

 
Chatwoot Captain
DIY bot-framework build
RxFlow AI sales agent
What it is
Chatwoot's own AI add-on: chats with customers, drafts replies, learns from your help docs
A bot framework (Botpress, Rasa, Typebot) you wire to Chatwoot's Agent Bot API yourself
An AI sales agent OCLT builds and runs for you on that same Agent Bot API
Setup
Turn it on in Chatwoot settings, feed it your help center
A developer writes the webhook backend, hosts it, and keeps it patched
We build it, deploy it, and operate it on your inboxes
Built for
Support triage: answering FAQs, drafting replies for a human to send
Whatever the framework can do. Intent detection and flows you design
Sales: answering, qualifying, negotiating, and closing on WhatsApp
Pricing
Credit-based. 300–800 Captain credits/month by plan, then $20 per 1,000 credits
The framework is free. You carry the engineering hours and hosting
Custom, scoped on your teardown call. No per-seat fees
Handoff to humans
Hands off with context when it can't resolve the query
You build the handoff and escalation logic yourself
Full thread moves to your floor at its handoff line, no copy-pasting context
Ownership
Runs on a Chatwoot Cloud plan; self-host support is still rolling out
Yours. You own the code, the uptime, and the maintenance
Chatwoot self-hosted, on infrastructure you control. We operate it, you own it
Best for
Support teams wanting FAQ automation inside a plan they already pay for
Technical teams with the capacity to build and maintain a bot long-term
D2C brands with a real sales floor who want an agent that sells, deployed for them

Captain figures: chatwoot.com/captain and Chatwoot's published Startup/Business/Enterprise credit allowances, July 2026. Agent Bot API and third-party integrations: Chatwoot developer docs and the public Botpress and Rasa Chatwoot integrations, July 2026.

Honest fit

None of these is right for everyone.

When Captain is the right choice

  • Your core problem is support volume, not sales conversion
  • You're already on a Chatwoot Cloud plan and want to try the built-in option first
  • Agent-copilot drafting is enough. A human still sends the final reply
  • You don't have a floor to hand tough conversations to

When a DIY build is the right choice

  • You have engineers who can own a webhook backend for the long run
  • Your flows are simple enough that a bot framework covers them
  • You want full control over every line of the logic
  • You're fine building the monitoring and escalation paths yourself

When RxFlow is the right choice

  • You run WhatsApp as a sales channel, not only a support one
  • You have a telecaller floor that needs the hard conversations routed to it, not dropped
  • Here, a missed handoff costs a sale. In support, it costs a slower ticket
  • You want it built and operated, not something you configure yourself

If WhatsApp cart abandonment is part of what you're trying to fix, run the numbers in the cart recovery calculator before the call.

Questions

Before you pick one.

Does Chatwoot have its own AI agent?

Yes. Captain is Chatwoot's native AI add-on. It answers from your help docs, drafts replies for agents to send, and flags questions your FAQ is missing. It runs on a monthly credit allowance (chatwoot.com/captain) and is built for support triage and agent copilot work, not sales negotiation.

Can I build my own AI agent on Chatwoot instead of using Captain?

Yes, through Chatwoot's Agent Bot API. You register a bot, connect it to an inbox, and it starts receiving webhook events for every conversation and message. From there you write the backend yourself. Reference builds exist for Rasa and Botpress, but each is a starting point you finish and maintain, not a finished product.

What does OCLT's AI agent do differently from Captain?

Captain triages support. Our agent sells. It answers, qualifies, negotiates, and closes inside the same Chatwoot inbox, then hands the thread to a human the moment it hits its line. 70–95% of conversations get handled by AI across deployments, and the person who picks up the rest gets the full history instead of a summary someone typed out.

Do I need to migrate off Chatwoot to get this?

No. We build on Chatwoot, we don't replace it. If you're already running it, we extend the instance you have. If it's better to stand up a fresh one, we'll say so plainly on the teardown call, not after you've signed anything.

Does this work with a telecaller floor, or just chat?

Both, and that's the point of pairing an AI agent with RxFlow instead of a chatbot alone. The same conversations sit under a native Android telecaller app with a built-in dialer, so a rep can call straight from the thread the AI agent already worked.

See it work a conversation on your own inbox.

Compare more setups on the full comparison hub, or go straight to a teardown call.

Book a teardown