Root AI

It doesn't just answer. It acts.

It reads the same live database your sales, inventory, schedule, and books run on, so it can answer with the real number and then do the next step: reorder the stock, draft the schedule, send the win-back.

Root
Ask Root anything
$48,210▲ 6% vs last week
“How did we do this week, and what needs my attention?”
RevenueUp across all locations, led by the bar on Friday
PaymentsOne card declined twice · retry scheduled
StaffingSaturday dinner is short one server · candidate found
CustomersA regular hasn't returned in 6 weeks · message drafted

The difference

Most platforms bolted a chatbot
onto software it can't reach.

A chat window bolted onto four tools that sync overnight can only repeat last night's export. Root AI queries the same live database, so it reads today's sales, today's stock count, and today's open invoices, then acts on them: adjusts a reorder, drafts a schedule, queues a payment retry.

Ask the business anything

One question.
The whole picture.

Ask in plain language and get an answer drawn from billing, staff, scheduling, and revenue together, in one context, instead of opening one siloed report at a time.

Because it reads the live operational database, the answer is always now, not whenever the last export ran.

Root AI
Who's about to churn?
84 regulars have gone quiet this month.
→Drafted a win-back text for each, ready for one-tap approval.

Then it acts

It closes the loop
in the background.

An answer is the start. Within the limits you set, Root does the work, retries the failed card, drafts the leaner roster, queues the reminder, and brings you the result or the one approval left to tap.

Root AI· Weekly reportAI
Why was Tuesday slower than usual?
Root AI

Covers were down 14% on Tuesday, driven by a 22% drop at the bar after 8pm. Two bartenders were scheduled where three is typical. I drafted a leaner Wed–Thu roster and flagged it for approval.

Approve rosterSee detail

A declined card is retried on its own

When a payment fails, Root retries it on an optimized schedule rather than letting it lapse, and tells you only if it still can't collect.

An uncovered shift gets filled

Root finds the best available person for an open shift, by role, hours, and availability, then reaches out to confirm them.

A customer drifting toward churn is caught

When a regular's pattern starts to fade, Root flags it and drafts a personal message for one-tap approval, before they're gone for good.

An unusual pattern is surfaced early

A dip in revenue or a spike in voids is brought to your attention before you would have thought to look for it.

Built right, not bolted on

AI-native
by architecture.

The AI isn't a separate app calling Root over an API. It runs inside the same system, behind one model layer, a per-business spend cap, and an off switch you hold.

One model layer, any model

Every model call goes through a single vendor-agnostic layer, so the best model can be used for each job and swapped without a rewrite.

Metered, with a real budget

Usage is metered against a per-business spend budget, so the cost of intelligence is known and bounded, never a surprise.

Gaps are recorded, not hidden

When the AI lacks a tool to do something, that gap is written down, so the product keeps improving toward what people actually ask of it.

Off with a single switch

One toggle in Settings turns Root AI off for the whole business. When it's off, no model call is made and no data leaves the database.

Private by default

It reads your data.
It doesn't take it.

Root AI reads your live records to do its work. It never trains a model on your data, it obeys the same per-business isolation and permissions as the rest of Root, and it can only see and do what the signed-in user can.

Never used to train models

It reads your live data to do its work, but your data is never used to train models, yours or anyone else's.

Retained, then deleted

Conversations are kept on a fixed schedule and then deleted. Nothing lingers indefinitely.

Bound by your permissions

It respects the same per-business isolation and permissions as everything else. It can only see and do what the signed-in user can.