Suptask alternative: BotFerry vs Suptask, priced out
Suptask bills each agent who opens the inbox. BotFerry bills the workspace once and stops counting. For a five-person rotation that is $90 a month against 9€, and the difference is a queue you may or may not use.
Prices checked 28 July 2026. Written by the BotFerry team, so read the Suptask column as a competitor's account of a competitor and follow the source link before you decide.
The short version
Pick Suptask if your requests need a status, an owner and a form. Approvals, SLA management on the Growth plan, dashboards, multi-source intake: that is a ticketing product and it works like one.
Pick BotFerry if the only Suptask feature you would touch is the one where a Slack mention reaches your team and the answer comes back to the thread. Same mechanism, 9€ a month for the workspace, no per-agent line.
BotFerry vs Suptask, side by side
Swipe the table sideways for the other columns.
| BotFerry This is us | Suptask | |
|---|---|---|
| Billing unit | Flat monthly, whole workspace | Per agent, per month |
| Entry price | 9€ / mo Starter: 3 bots, unlimited operators | $18 / agent / mo Starter monthly, $15 on annual billing |
| Five operators, one month | 9€ / mo | $90 / mo |
| Volume on the entry plan | 5,000 messages | No cap published |
| Operator replies land back in the original thread | Yes | Yes |
| Flat price, operators not billed per seat | Yes | No |
| You create the Slack app and hold the token | Yes | No |
| Relay vendor keeps no message content | Yes | No |
| Several separate front doors on one plan | Yes | Professional and up |
| One private thread per request | Yes | Yes |
| Attachments relay both directions | Yes | Yes |
| Internal notes the requester never sees | Yes | Yes |
| Ticket statuses, assignment, queues | No | Yes |
| SLA timers and escalation | No | Growth plan |
| Reporting and analytics | Activity log only | Yes |
| AI drafting or AI agents | No | Growth plan |
| Email or web chat intake | No | Professional and up |
| One-click install, no app to build | No | Yes |
Prices read 28 July 2026 from each vendor's own pricing page, linked below. BotFerry bills in euro, the others list dollars, so treat the two currencies as separate numbers rather than a converted total.
The volume row does not compare like with like. One BotFerry message is a single hop across the ferry, either a mention carried into your ops channel or a reply carried back. A ticket, conversation, or credit elsewhere covers a whole exchange. Seat prices in the rows above are directly comparable.
Sources: Suptask
The arithmetic
Suptask lists $18 per agent a month on Starter, dropping to $15 if you commit for the year. Professional is $29 monthly, Growth is $45. An agent is anyone with access to the Suptask inbox, and requesters cost nothing, which is the right way round for a company where a hundred people ask and four people answer.
Where it bites is the four. Two operators on Starter is $36 a month. Five is $90. Ten, once you have rolled the bot out to the office channels and put the whole IT rotation in the inbox, is $180. Every person you add to the rota adds to the invoice, even the one who answers twice a week.
BotFerry Starter is 9€ a month with unlimited operators and 5,000 relayed messages pooled across up to three bots. Team is 19€ for ten bots and 20,000 messages. What grows the bill is traffic through the ferry, so a busy channel costs more and a bigger rota does not.
What Suptask gives you that we do not
Suptask turns a Slack message into a ticket with a lifecycle. It has statuses you configure, assignment so two agents stop answering the same person, custom forms that collect the fields you always end up asking for, ad-hoc approvals on Professional, and SLA management with AI assistants on Growth. Multiple inboxes let you split IT from HR from finance under one account.
If you have read that paragraph and recognised your team, stop here and buy Suptask. BotFerry has no statuses, no assignment, no forms, no approvals and no SLA timers, and we are not building them. Our activity log records a type, a reason and a timestamp for each relay attempt, which tells you whether a message crossed and nothing about how long it took your team to answer.
What we give you that Suptask does not
You build the Slack app. The setup wizard generates a manifest, you paste it into api.slack.com in your own workspace, install it, and the bot token belongs to you from that moment. Revoking BotFerry is a button in Slack rather than a support ticket with us. Suptask installs from its own marketplace app in one click, which is faster on day one and puts the token on their side.
We also keep no message content. BotFerry reads a mention, writes it into your operator channel, and holds on to the thread mapping and a log row. There is no ticket store, which means no support history to export, breach, or hand to a subpoena. That is a security property and a missing feature at the same time, depending on which auditor is asking.
One more shape difference: several front doors on one plan. @Support in the customer channels, @IT Help in the office channels, @Feedback wherever product hangs out, three separate Slack apps drawing from one message pool. Suptask splits that across inboxes on Professional and up.
Switching, and how long it takes
An afternoon on the Slack side. Create the app from the wizard manifest, add it to whichever channels Suptask was watching, pick the private channel your operators will work in, and send a test mention. The wizard checks the round trip before anything goes live.
Your Suptask ticket history stays in Suptask. We have nowhere to put it. Teams that care about the archive keep the Suptask account on its cheapest tier for a month while the relay runs in parallel, then export what they need and cancel.