Glossary
What every Rufio-specific word on this site means
What it is
The definition of every word this documentation uses in a specific way — Suggest, Review, and Automate; the names for the things in your business; and what Available, Where relevant, and Needs setup first actually mean. Every other page on this site links here instead of explaining a term again, so if a word feels unfamiliar or you're not sure it means what you think, this is where to check it.
How it works
| Term | What it means |
|---|---|
| Shadow | A draft-only mode for observing a workflow before authorizing real actions. |
| Suggest | Rufio prepares work and waits for your approval before acting. Keep a task here for as long as you want. |
| Review | You authorize a task to act within your rules, then Rufio shows you the result afterward. Use Suggest if you want to approve each action first. |
| Automate | Routines you enable run within your rules. Their activity remains available to inspect, and you can adjust or pause them. |
| Business foundation | A published starting point with records and workflows for your kind of business, ready for you to shape around your own process. |
| Business type | The kind of business you run, read from the category your business is published under. |
| Approval | Your explicit OK before an action proceeds. Reviewing the result after an authorized action is a separate step. |
| Job | The piece of work being done for a customer — what gets scheduled, dispatched, and closed out. |
| Customer | The business or household you do work for. |
| Contact | A person at a customer — not the customer itself. |
| Quote | The price you offer a customer before the work starts. |
| Invoice | The bill you send once the work is done. |
| Appointment | A scheduled time for work with a customer. |
| Available | Works for every business on Rufio. |
| Where relevant | Works where your kind of business actually has this to do. A business that holds stock has stock to track; one that does not, has nothing to track. |
| Needs setup first | Needs something connected before it can run — a phone number, a payment account, a domain. It will not work on day one, and Rufio says so rather than failing quietly. |
These spellings are fixed the same way everywhere on this site: Rufio, business type, job, customer, contact, approval, Suggest, Review, Automate, and appointment are never swapped for a synonym, even one that would read a little more naturally in a given sentence. If another page uses a different word for the same thing, that's a mistake in that page, not a second term worth learning.
Boundaries
This page defines terms; it doesn't explain the mechanics behind the bigger ones. How a task actually moves between Suggest, Review, and Automate, and who decides when it's ready to move, is covered in full on the autonomy levels — this page only tells you what those names mean. Likewise, which specific capabilities carry which availability state is covered on every capability; this page defines what "Available", "Where relevant", and "Needs setup first" mean in general, not which one applies to which task.
It also doesn't define words that are ordinary English used the ordinary way. Only the terms Rufio uses in a specific sense, or where the correct word actually matters — a contact is not a customer, a job is not a ticket — are here.
Related
- Autonomy levels — how a task actually moves between Suggest, Review, and Automate
- Every capability — the availability state for each specific capability
- Business types — how a business type gets supported
- Reference — the rest of the reference section