Examples
An entire company, programmed
Three illustrative companies, shown through their inner workings: a coordinator that splits the work among agents by area, workflows that wait, call each other and run in parallel, scheduled tasks, people who approve and the company's own systems, connected.
Illustrative example: none of these companies is a customer or a published solution. Each piece carries the label of what runs today.
How to read the labelsRuns todayPartialAvailable on requestComing soonVision
- Runs today
- Implemented and tested; if it ships turned off, the limit says how to turn it on. If the statement is not a capability, such as the license, the trademarks or a design principle, it means the statement is true today.
- Partial
- Runs, with gaps in the implementation: the limit says which ones.
- Available on request
- Does not run today: Omniatix™ implements it if a customer asks for it, with no timeline.
- Coming soon
- Omniatix has announced it and it is not available yet. No date.
- Vision
- The purpose GrailAOS™ is designed for. It is not a current capability: what already runs carries its own label.
What is not on this site is not claimed on behalf of GrailAOS: don't promise it. For other capabilities, ask Omniatix.
Examples · 1 of 3
My Store
It sells through its online store and on Mercado Libre, takes payments with Mercado Pago, keeps its stock in its ERP and its customers in a CRM.
The systems it connects
Its online store, on Shopify or Tiendanube
Runs todayThrough its or an server
Mercado Libre
Runs todayThrough its API
Mercado Pago
Runs todayThrough its API
Limit Off by default, and turned on tool by tool.
Its ERP, with stock and sales
Runs todayThrough its API or an MCP server
Its CRM, with its customers
Runs todayThrough its API or an MCP server
A custom connector for any of those systems
Available on requestCustom connector, on request
Coordinator
Runs todayThe chief of staff
Serves each customer on WhatsApp and in the store chat, and hands each matter to the agent for the right area.
People who decide
Runs todayThe manager
Approves refunds over $100,000: the notification reaches their phone and they decide from the console.
Alongside the person in charge
Runs todayThe manager's assistant
An agent of the same solution that talks to the manager in web chat and schedules what they ask it to remind them of.
Runs todayThe warehouse
Resolves what the agent cannot, such as a delayed shipment: the conversation is handed off to them in the console.
Agents by area
Runs todaySales and customer service
- Answers questions about products, prices and shipping
- Takes the orders that come in through the conversation
Runs todayAfter-sales and complaints
- Handles complaints, exchanges and returns
- Starts the workflow for each refund
Runs todayStock and replenishment
- Reserves each sale in the ERP
- Leaves a notice on the account when a product drops below its minimum
Runs todayBilling and reconciliation
- Reconciles Mercado Pago payments with sales
- Prepares the list for each campaign
A day
On a schedule
Before opening, yesterday's payments are reconciled with sales. If something does not add up, a notice is left for the manager.
By a person
The manager writes to their assistant: “on Mondays I'm at the warehouse all morning, so send things my way after noon.” The following Monday, the assistant still remembers; and if the manager says “forget that,” it deletes it.
Limit Off by default; turned on in the 's configuration.
On a schedule
Two sales came in through Mercado Libre. The chief of staff passes them to the stock agent, which reserves the goods in the ERP.
Through a channel
A customer asks on WhatsApp for a $180,000 refund. Since it is over $100,000, it waits for the manager: a notification reaches their phone, they approve it and the money is returned.
Through a channel
A customer asks on WhatsApp whether their size is in stock for an exchange. The after-sales agent asks the warehouse without handing over the conversation and, when they answer, tells the customer in the same thread.
Limit Turned on by configuration; the person replies from the console.
On a schedule
The seasonal campaign is put together with the CRM's 3,000 customers, each with the last thing they bought. At five, the campaign messages them on WhatsApp.
Limit The collection tools are enabled by the deployment's startup code.
By a person
At closing time, the manager asks their assistant: “remind me to call the supplier on Thursday at ten.” On Thursday at ten, the reminder shows up in their chat.
On a schedule
The owner gets the day's summary by email: how many orders came in, how many complaints there were and how many refunds were approved.
Limit The collection tools are enabled by the deployment's startup code.
If something fails
While the refund is being processed, the machine handling it goes down. Another one picks it up where it left off, and the refund is not made twice.
Limit Off by default, and turned on tool by tool.
In the middle of the afternoon, a new version of customer service is published. The refunds waiting for the manager continue with the version they started with.
If the manager does not answer in time, the request expires: at My Store, an unapproved refund is not made.
If something was left halfway, you can see where: each refund and each campaign can be followed step by step.
How it is tested
Before publishing, each agent is tested with Mercado Pago, Mercado Libre and the ERP simulated: in a test, not a single peso moves.
If someone builds a workflow that tries to message customers or to use something that does not work yet, it cannot be published.
A new version of customer service goes first to the owner's test contact; customers stay on the one they had.
Does your company look like this? Tell us at omniatix.com or request more information
Examples · 2 of 3
My Lender
It makes personal loans: applications arrive by chat, it checks the credit bureaus, builds the loan file, a committee decides and it collects in installments.
The systems it connects
The credit bureaus
Runs todayThrough its API
The lender's system, with loan files, disbursements and installments
Runs todayThrough its API
Limit Off by default, and turned on tool by tool.
Coordinator
Runs todayThe chief of staff
Handles each inquiry on WhatsApp or on the web and distributes it among origination, risk and collections.
People who decide
Runs todayThe credit analyst
Reviews the loan file and approves or rejects it, with a comment: hers is the committee's first signature.
Runs todayThe risk manager
Gives the second signature on large loans, in their own approval step.
Runs todayThe collections officer
Negotiates the overdue cases handed off to them in the console.
Agents by area
Runs todayOrigination
- Takes the application and the person's details
- Starts the evaluation of each application
Runs todayRisk
- Checks the credit bureaus
- Builds the loan file in the lender's system
Runs todayCollections
- Serves whoever replies to an installment notice
- Hands overdue cases to a person
The risk manager also has an assistant on the same platform, like the manager at My Store.
A day
On a schedule
Notices go out for the installments due today, along with reminders for those that fell due five and fifteen days ago.
Limit The collection tools are enabled by the deployment's startup code.
Through a channel
A person applies for a loan on WhatsApp. The chief of staff passes them to origination, which takes their details and starts the evaluation.
Through a workflow
Both bureaus are checked at the same time, and the loan file is built with what they return.
By a person
The committee decides: the analyst approves the loan file and, since the amount is over $2,000,000, the risk manager gives the second signature.
Through a workflow
With both signatures, the lender's system makes the disbursement.
Limit Off by default, and turned on tool by tool.
Through a channel
Someone with an overdue installment replies to the reminder: they want to refinance. The collections agent hands the conversation to the collections officer.
If something fails
The machine that was waiting for the second signature restarts. The wait goes on, and the loan is still decided when the risk manager signs, even if it is the next day.
If the disbursement request is cut off without knowing whether it arrived, it is not blindly repeated.
Limit Off by default, and turned on tool by tool.
How it is tested
Each agent is tested with the bureaus and the lender's system simulated, with applications that are approved and others that are rejected.
A workflow that tries to message the loan applicant on its own cannot be published: notices go out through the campaigns.
Does your company look like this? Tell us at omniatix.com or request more information
Examples · 3 of 3
My Distributor
It sells to the shops in its area: it takes orders on WhatsApp, keeps each customer's credit account and delivers every day.
The systems it connects
Its ERP, with customer accounts, stock and deliveries
Runs todayThrough its API or an MCP server
The day's price list
Runs todayAs tabular data
Limit The collection tools are enabled by the deployment's startup code.
Coordinator
Runs todayThe chief of staff
Receives orders and questions from the shops on WhatsApp and passes each one to the right area.
People who decide
Runs todayThe credit manager
Approves or rejects the orders that go over the shop's credit limit.
Runs todayThe warehouse manager
Confirms the delivery route before it goes out.
Agents by area
Runs todayOrders
- Takes the order and enters it in the ERP
- Answers price questions with the day's list
Runs todayCustomer accounts
- Checks each shop's balance and credit limit
- Starts the approval when an order goes over the limit
Runs todayDelivery
- Plans the next day's deliveries
- Answers when each order will arrive
The distributor's owner also has an assistant on the same platform, like the manager at My Store.
A day
On a schedule
The day's price list comes in.
Limit The collection tools are enabled by the deployment's startup code.
Through a channel
A grocery store orders twenty cases of cooking oil and ten of yerba mate on WhatsApp. The orders agent confirms the day's prices and enters the order; the total comes from the ERP.
Limit The collection tools are enabled by the deployment's startup code.
Through a workflow
The order goes over the grocery store's credit limit: it waits for the credit manager, who gets the notification.
By a person
The credit manager approves it with a comment, and the order goes into the delivery route.
On a schedule
Tomorrow's delivery route is planned, zone by zone, and the warehouse manager confirms it.
If something fails
If the ERP does not respond when an order is being entered, it is tried again without repeating what was already done.
If the credit manager does not answer in time, the order expires and does not go into the delivery route.
How it is tested
Each agent is tested with the price list and the ERP simulated, with orders within the limit and others over it.
A new version of customer service is seen first only by the owner's test contact.
Does your company look like this? Tell us at omniatix.com or request more information
More information
Is your company evaluating GrailAOS? Request more information
What you've read is less than half. There are more than 180 capabilities that already run, with their details.
Small businesses
For a small business
There are ready-made solutions at omniatix.chat.