It books the visit, takes the whole order, hands off to your team when it should. It serves on WhatsApp, on your website chat or inside your own system. Before anything irreversible it asks you first, it never makes up a price, and it records every step.
Table for 4 on Friday at 9pm?
party: 4 · day: Friday · time: 21:00
"booking" flow → check availability
availability(fri 21:00) → table free
booking is irreversible: asks for a yes first
I have a table for 4 on Friday at 9pm. Shall I book it under your name?
What it does
Five things your team does by hand today, every day of the week and at any hour.
It answers what your customers ask with your prices, your opening hours and your documents. If the answer is not there, it says so and hands off: it does not make it up.
It books visits and appointments against your calendar or your system, and confirms with the customer before reserving.
It builds the order step by step, reads it back in full, and closes it only on an explicit yes.
When the case calls for it, or when the customer gets upset, it passes the conversation to a person with the full context.
It speaks on the phone: the concierge of a building talks to whoever rings the door and transfers the call to the right apartment.
Where it serves
You choose where it serves: in your channels, ready to use, or inside your own system. It is the same agent with the same rules.
In your channels
For businesses that want to serve customers now, without coding.
Your agent serves on WhatsApp, Telegram and your website chat. From the dashboard you set its rules, its information, and when it hands over to a person.
Same agent · same rules · same trace
In your system
For teams with their own app, website or CRM.
Your application talks to the agent through an API and the interface stays yours. If you already use OpenAI, you change the address and the key: the rest of the code stays as it is.
Not looking for customer service, but for something that operates your systems? Same engine, your tools. Operating systems →
For developers: the API, the SDKs, the models and the standards we adopt are on core.iamagnus.com. Read the docs
The engine that decides, Magnus Zero, will be released as open source (Apache-2.0).
How it decides
A chatbot ships in two days, but it invents prices, confirms things nobody authorized, and when something goes wrong there is no way to know why. Custom software does not fail that way, but it takes months and a team. Magnus is the middle path: the model is used where it is good — understanding what a person writes and drafting the reply — and what to do is decided by an engine with declared rules anyone can read.
Your business rules are declared per industry. Nothing irreversible without a confirmation. Handoff to a person when it is called for.
What it understood, what it decided and by which rule, what it queried and what your system returned. When someone asks why the agent did something, there is an answer.
If the AI provider does not answer, the turn continues on another. Under pressure the system degrades in a controlled way instead of breaking.
Magnus is not a chatbot that improvises, nor a layer on top of a model: it is what decides what the AI does, and what keeps the record.
Your data: every organization is isolated from the others, and data handling follows the European GDPR framework and United States regulation. If your case does not allow anything to leave your network, Magnus is installed on your own infrastructure. Where your data lives →
What already runs
0%*
invented tools: the agent never called one that did not exist
See all 18 industries →
100%*
turns with a trace: for every one of them you can reconstruct why
18
business domains already configured
The first two numbers come from our own test bench: 120 conversations across 7 industries, 30 of them written to make it fail. Ask us for the report. As of October 24, 2026. "Pilot" = tested on real cases and still being trialled. "In development" = not available yet.
Answers the building intercom through its phone system, talks to whoever is at the door and transfers the call to the right apartment. It does not decide to open the door: it decides who to route to, and logs it.
See the industry →
A management system for the administration and an agent for residents, working on the same data.
See the industry →
Property search, visit scheduling and lead capture, using the listings and time slots the system returns.
See the industry →
Step-by-step order taking, explicit confirmation before closing it, and handoff when a sensitive question comes up.
See the industry →
Support that detects urgency and frustration, and hands off to a person with the conversation context.
See the industry →
Financial projections for banks and credit unions, with each user’s data kept isolated.
Is it for you?
We would rather say it before the demo. If your case is in the right-hand column, we will tell you so in the first meeting.
If you are not sure which side you are on, that is exactly the half-hour conversation worth having.
Pricing
The API comes with every plan, the free one too. The native channels — WhatsApp, Telegram and your website chat — come with Pro.
Free
Free
The API with your own agent. By invitation, no card.
Starter and Growth
US$ 19–59 /month
The API in production, in your app or your backend.
Pro
US$ 149 /month
Volume, and the native channels ready to serve.
Enterprise
Custom
Dedicated capacity, SLA and support.
A conversation is one customer served in a day. At the cap the plan pauses until next month: no overage, no automatic upgrade.
Contact
You tell us the process you want to automate and we show you your own case running on Magnus: what the agent can do, by which rules, and what gets recorded.
