We make software in this category — disclosed at the end, where it comes up. Most of this page is about a problem you have whether or not you ever buy anything.

Ask an owner where the business actually runs and you rarely hear the name of a system. You hear “my phone.”

Not the CRM. Not the dashboard somebody built in 2019. The messaging app in their pocket, where the supplier confirms the delivery slipped a day, where the warehouse gets told what to load, where a customer’s complaint arrives at 9pm on a Sunday.

Now look at what the automation industry sells that owner. Every demo opens the same way: first, log into the dashboard.

That is the whole problem, and it is not a software problem.

The thing that fails is almost never the automation

Here is the pattern that repeats across small businesses that have bought automation and quietly stopped using it.

The tool works. It did everything it promised in the demo. Six weeks later, two people use it — usually the person who chose it and one other. Everyone else has gone back to the group chat, because the group chat is where they already are, and the new system is one more place to check on a day that has no room for another place to check.

Nothing was broken. The software just lost a competition against a habit.

This is worth being precise about, because it changes what you should be shopping for. Your team is not resisting automation. They are resisting a context switch — leaving the app they live in, remembering a password, finding the right screen, and coming back. For someone in a van, on a shop floor, or between two customers, that round trip costs more than the task saves. So the round trip doesn’t happen.

Which means the useful question is not what can this tool do? It is: where does the work have to happen for it to actually get done?

For a lot of businesses, the honest answer is: in the thread that’s already open.

What “run it from the thread” actually means

Let me be exact about this, because there are two very different things sold under similar language, and only one of them is what this page is about.

This is not a public chatbot, on purpose. A number that answers anyone who texts it is a different product with different risks, and we made the opposite choice deliberately: no anonymous senders, ever. Not because the plumbing can’t do it — because a channel that can move real work through real systems should refuse to act for a sender it can’t name.

This is your people, running your systems, from the app they already have open. Your warehouse manager, your bookkeeper, your two field techs, you. Each of them connects their own messaging account to their own account on the system, once. From then on, a message from that person is a message from a known person — with whatever permissions that person already has, and no more.

That distinction is the entire safety story, and it is why the design starts with identity rather than with clever parsing. A message that can move real work through real systems has to know who is asking. Anonymous convenience and real authority are not things you want in the same channel.

In practice the connection is a six-digit code, sent from inside the app, that expires and works once. After that the person’s own WhatsApp number is their credential. No new password, because there is no new account.

One thing worth setting expectations on honestly: for WhatsApp specifically, the business does a one-time setup first — WhatsApp Business number, credentials from Meta — the same paperwork any company does to send WhatsApp messages at all. That part is not thirty seconds. The per-person connection after it is. On Telegram and Slack, there’s no equivalent first step.

The handoff you already do, without the retelling

The moment this stops being a channel feature and starts being useful is the handoff.

Your warehouse manager asks about a shipment from WhatsApp. He’s on the floor; that’s the app in his hand. Your ops lead picks it up from Slack, because she’s at a desk and Slack is where she lives. It is the same conversation, holding the same context — the shipment already identified, the question already asked. She doesn’t ask him to repeat the order number.

Anyone who has watched work fragment across three apps knows what that retelling costs, and it isn’t only time. It’s the customer hearing “let me check with the warehouse” for the second time in a day.

Here is the precise shape of it, because a claim like this deserves one. While a conversation is live, the thread hops channels automatically — a message from either of them, from either app, lands in the same conversation. After roughly half an hour of quiet, the automatic matching stops guessing: the next WhatsApp message starts a fresh thread rather than silently attaching to something from this morning, which is the behavior you want from a system that acts on what it’s told. The conversation itself is not gone. It stays on the platform with its full context, and picking it up Monday from the web app, exactly where Friday left it, is a normal thing to do — sessions end when someone ends them, not when a timer runs out.

What decides whether it gets used

Three things, in the order they’ll bite you:

Does the work start where your people already are — or does it start with a login? Everything else is downstream of this.

Is the person on the other end of the message actually known to the system? If the answer is “we match on phone number and hope,” you have built a way for anyone who knows the number to spend your money.

Can someone pick up a thread from a different app without the retelling? This is the difference between a messaging gimmick and a team actually working in one place.

None of the three are about how clever the AI is. That’s the point. The clever part has been commodity for a while now; the reason automation fails in a fifteen-person company is almost never the model.

Where we fit

We build this. HitLai runs six channels — WhatsApp, Telegram, SMS, Slack, Discord and email — into one engine, and it is genuinely one engine rather than six integrations wearing a trench coat: same workflows, same permissions, same record, whichever app the message came from. Every inbound message is signature-verified at the door. Every sender is a person you’ve linked, not a phone number we’re guessing about. Threads carry across channels while they’re live, and conversations persist until someone ends them — walk away Friday, pick it up Monday from the web app with the context intact. Files work as a starting point too — forward a supplier’s PDF invoice and that’s the trigger, not a chore you do afterwards.

And because this is the question a sensible person asks next: none of it changes who is allowed to do what. The same dial that decides which actions run on their own and which ones wait for a person applies identically to a message sent from a warehouse floor, and the record of what ran and who approved it is the same tamper-evident record either way. The channel is the front door. It is not a way around the house rules.

That’s the pitch, and it’s smaller than it sounds: your team already coordinates your business in a group chat. The work can happen there too.

Bodaty builds HitLai, an AI orchestration platform for small and mid-sized businesses. The Community Edition is open source.