Don't reinvent the wheel, why building your own support system doesn't pay off

When a product starts getting users, the temptation appears: "For support, I'll just build something simple." A form, a database table, an admin screen to read the messages. With an AI assistant, it's done in an afternoon.

The afternoon isn't the problem. Everything that comes after is.

What it looks like and what it is

A form that saves messages isn't a support system. For it to really work, before long you need:

• email notices to the user when you reply, because nobody sits on your website waiting;
• their replies to that email going back into the conversation, not getting lost in your inbox;
• statuses, to know what's pending and what's solved;
• attachments: screenshots, PDFs, sometimes a video;
• history per user, so you don't ask the same thing twice;
• access for your team without handing over the keys to your admin panel;
• a help center with FAQs, so people stop asking the same thing.

Each item is small. Together they're a whole product, and it isn't yours.

The costs you don't see

Your focus. Every hour spent on the support inbox is an hour not spent on what makes your product different, the only thing your users can't get elsewhere.

Maintenance. What you build, you maintain: dependencies that update, migrations, the day you switch email providers. It never ends.

Security. A messaging system built in a hurry is a good place for a permissions bug, the one that lets one user read another user's conversations. That's personal data, with everything it implies.

Email. Getting your replies into the inbox and not into spam is a craft of its own.

Complexity. Tables, screens and endpoints that have nothing to do with what you sell, and that anyone touching the code, person or AI, has to understand.

Lack of experience. Support tools have spent years learning what a team that looks after users needs. Building it yourself, you learn it from complaints.

When it does make sense to build it

If support is your product. Or if your needs are so particular that no tool comes close. For everyone else, which is almost everyone, the maths is clear.

What Helpeen does instead

Helpeen is the inbox, the help center and the notices, already solved. You choose how to integrate it:

• a widget with one line of HTML: a floating chat and a help center, without writing server code;
• React components, if your site is built with React;
• or the API, if you want your own design. It gives you the content as JSON, with the Markdown already turned into safe HTML.

If an AI is doing the integration, we have a guide written for it, with the security rules and code ready to adapt. You hand it over and review what it does.

Starting costs €0: the Free plan covers one project, with 100 messages a month. When you grow, Basic removes the team and message limits for €9 a month plus VAT. That's less than an afternoon of your time.