Limits and boundaries

What it is

This page is mostly a list of things Rufio doesn't do. That's deliberate — an AI you can trust isn't one that can do everything, it's one that's clear about what it won't, and a page that only describes what Rufio can do would leave out the half of the answer you actually need before trusting it with real customers and real money.

Some actions require your explicit approval even when other routines are automated. Other actions, such as signing a contract, stay with a person. These boundaries help you choose what to delegate and what to keep under direct review.

How it works

Always requires you, no matter the level:

• It never moves money on its own. You can choose to automate sending invoices. Paying anything, refunding anything, or changing your prices always requires you — that never becomes automatic, at any level.
• It never commits you to work without your OK. It can hold a time slot for a caller, but confirming the booking follows the rules you've set, and defaults to asking you first.
• It never invents new behavior on its own. If a new automation or a new way of handling something would be useful, Rufio proposes it to you in plain language before it exists, rather than quietly starting to do something new because it decided that would help.

Doesn't do at all, regardless of approval:

• It never signs anything. Contracts and agreements are drafted for you to review and send. Rufio itself never executes a signature — that isn't a setting you can turn on.

Needs setup before it can run at all:

Separately from those hard lines, some capabilities aren't switched on for your business until something specific gets connected — a phone number, a merchant account, a domain. Until that setup happens, the capability doesn't run, and Rufio says so rather than failing silently or pretending it worked. You won't send a text message into a void or discover a missed call weeks later; if the piece it needs isn't connected yet, it tells you that's the reason, at the moment you ask for it.

This is a different kind of limit from the hard lines above. It isn't a rule about what Rufio is allowed to decide on its own — it's about what's actually connected yet, the same way a phone line has to be installed before a business can answer calls on it. Once the missing piece is connected, the capability behaves like everything else on this page: it works, and it's still subject to whichever autonomy level you've set for it. Every capability lists which ones need this kind of setup, one by one — this page states the shape of the rule, not the list.

Boundaries

This page doesn't cover how much of the remaining, unrestricted work Rufio does on its own versus waiting for you — that's set per task and explained in Autonomy levels. A task can sit at Automate and still be subject to everything on this page.

It also doesn't cover where your data lives or who can reach it, including the fact that Rufio never shares your business with anyone else — see Your data for that. And it doesn't restate what Rufio actually is or the line between AI judgment and exact software operations — see What Rufio is.

Related

• Autonomy levels — how much of everything else Rufio does without asking, and how that changes over time
• Your data — where your information lives and who can reach it
• Every capability — the full list, including exactly which ones need setup before they'll run
• What Rufio is — what Rufio actually is, in plain terms