AGENTRA

Smith

A platform for building and running assistants with agentic capabilities: they answer on web, WhatsApp and Telegram, they know the business, and they get things done rather than just replying.

An assistant factory, not one more chatbot

The problem

The average chatbot answers frequently asked questions and little else: the moment a customer asks for something real, it hands off to a human. And every new channel ends up being a different bot, with its own content ageing separately. The result is three assistants that contradict each other and none that resolves anything.

How it solves it

Smith puts a single agent loop behind every channel: the same head serves the web, WhatsApp and Telegram. You teach it the business once and it searches by meaning, not by exact wording; whatever it could not answer is logged so you can teach it afterwards. For work that needs expertise it delegates to specialist roles, and with connected tools it executes instead of forwarding. Each organisation runs isolated, in its own container, and all model traffic goes out through routerPlex.

The real screen

Screenshot of the Smith interface
Smith's sign-in screen in production. Assistants are built and operated from the panel, behind each organisation's access.

How it solves it

Isolation is not a configuration promise: each organisation runs in its own container, with its own knowledge. And all model traffic goes out through routerPlex, so the assistant's spend is governed from day one.

What it does

Assistants built to order

You define what it does, in what tone and with which permissions. Specialist roles split the work when the request calls for it.

One assistant, three channels

Web, WhatsApp and Telegram converge on the same agent loop. Not one bot per channel: the same one, with the same memory.

It learns the business

You teach it with your own documents and answers. It searches by meaning rather than literal matches, and keeps a log of what it could not answer.

It acts, not just answers

Tools wired into the assistant — including those of other systems via MCP — so it carries out the action instead of passing it on.

Isolation per organisation

Each organisation gets its own space, its own knowledge and its own container. One tenant's data never surfaces in another's conversation.

Real operation

Business hours, scheduled recurring work, and controlled publishing of changes before they reach a customer.

Who it is for

Small, mid-sized and large companies already receiving more enquiries than their team can handle, that need the assistant to resolve — not to hand out tickets.

Built with

TypeScriptNext.jsFastifyPostgreSQLRedisDocker

Let's talk about your operation

Tell us which decision your business still makes by gut feel. If we can help, we'll tell you how — and if we can't, we'll tell you that too.