Most small businesses handle customer support in a way that looks less like a diagram than a tangle: scattered emails, messages across various platforms, phone calls that ring exactly while you’re busy and then quietly disappear before you’re free. There’s no central point where a request comes in, gets recorded, routed and tracked until it’s resolved. There’s your memory, which is excellent right up until the moment three requests arrive at once. Am I wrong?

You’ll tell me ready-made systems exist. They do, and they cost. And someone always asks why on earth I’d build it myself. Because I wanted to show this can be done properly, without expensive off-the-shelf systems. So I built a complete support system from scratch. That’s just how I work.

What I actually wanted out of it

The goal was a system combining three things that are usually separate and expensive: a smart first-line assistant, an organized request management system (ticketing), and a space where the customer sees the progress of their requests. Three pieces, three interfaces, three passwords, three accounts nobody ever remembers. Ideally, one.

All of this had to work together, in Greek and English, and be simple enough for a small business without a technical team to use. The test was strict and I kept to it: if you need training before you can open it, something has gone wrong. Because a tool that needs a manual isn’t a tool. It’s a second job.

How I ended up building it

I built a three-layer system that works as a single flow:

  • First-line smart assistant. Instantly answers common questions, day and night, drawing from an organized knowledge base. When a human is needed, it turns the conversation into a ticket with the full history.
  • Ticketing system. Every request is recorded, categorized and tracked. Nothing gets lost, nothing is forgotten.
  • Client portal. The customer logs in and sees the status of their requests, without having to ask “what happened with what I sent you?”.

Three layers on the inside, one single flow on the outside. The customer never has to know which layer they’re standing in, the same way nobody counts a building’s doors before walking through the open one.

So what does the artificial intelligence actually do here

Artificial intelligence isn’t decorative. I didn’t add it so I could say somewhere that I have it. It’s the first line that carries the weight of repetitive questions, so the human only deals with what genuinely needs judgment.

In practice, the assistant receives the customer’s question and prepares the answer. From there, there are two paths: in the simpler, clear-cut cases it handles it on its own and replies instantly. In the more complex ones, it prepares a suggested answer and waits for my approval before it’s sent. Yes, I read them. This way the customer gets fast service, but human control stays where it’s needed.

The result is an experience where the customer gets an instant answer most of the time, and the owner isn’t drowning in repetitive messages, without ever losing control of what’s said on their behalf. That last part isn’t a detail. It’s your name doing the talking.

Why it matters

This system didn’t exist. I designed and implemented it as real infrastructure. It’s live and works every day, not in a demo, in the actual daily grind. It proves that a small business can have enterprise-level support, without the corresponding cost or complexity.

So the tangle from the opening comes undone. Not by magic, but because requests finally got a door and a road.

If you want to organize your own business’s support this way, chatbot, ticketing, portal, let’s talk.