About

Why BotFerry exists

One person builds it, runs it, and answers the support inbox. This page says why.

It started as my own problem

I spend my working day in Slack, and two patterns kept repeating. Customers @mentioned a shared support name and expected an answer from whoever was on shift. Colleagues tagged the on-call name and needed it to reach whoever held the pager that week. Behind both names sat a person the requester was never meant to see.

Every tool I tried wanted to be a helpdesk first: ticket queues, per-agent seats, dashboards nobody opened. What I needed was a relay. A mention travels into a private channel, the reply travels back under the bot's name, and the conversation stays in its thread. So I built one, ran it on my own workspaces for months, and turned it into BotFerry.

The two setups I lived with

One person, on purpose

BotFerry is a one-person business. I write the code, keep it running, write these pages, and use the product daily, so I hit the rough edges before you do. Staying small keeps it what it is: a relay that does one job well, priced so a small team can afford it without a procurement meeting.

Feedback lands with me

For feedback, a feature request, or a complaint, write to support@botferry.com. I read and answer every message personally.

Cookie preferences

BotFerry sets only the essential cookies below. There is nothing optional to turn on yet.