What Rufio does

Rufio works across everything a service business runs day to day — the customer, the job, the paperwork, and the money — as one connected place rather than separate tools you keep in sync yourself. This section is for an owner deciding whether Rufio fits how their business already runs, and for anyone already using it who wants a plain answer to "what actually happens when I ask for this."

The pages are organized around the work itself rather than around the way business software is usually divided up — getting back to people who called, getting a quote out, checking whether a finished job was invoiced. Each page covers one of those stretches of work start to finish, including the parts that cross what software normally treats as separate systems.

Each page answers the same two questions in the same order: what happens when you ask Rufio for the thing, and where Rufio stops and hands it back to you. Every one carries a real request worked through end to end, including the point where it stops. That second question is the one that matters more, and it's answered whether or not you asked — a page here that only described what works would be telling you half the truth.

What's in this section

• Customers and sales — customer and contact information, the history behind each one, leads, quotes, and the follow-up that keeps a deal moving
• Phone and messages — calls in and out, message drafts, conversation history, and support requests
• Work and scheduling — availability, booking, the calendar, recurring work, jobs and tasks, and who they're assigned to
• Money — quotes and invoices prepared for you, online payment routing, financial records, and purchasing and stock where your business carries them
• Paperwork and documents — documents and forms from your own templates, signature routing, customer portals, file organization, and marketing
• Automation and reports — work that runs on a schedule or a trigger without being asked each time, the approval gates that hold it, and the reports that show what happened
• Team and systems — who on your team can do what, connections to services you already use, and the builders that shape Rufio around how you work

Before you read these

A couple of things on these pages won't make sense without the Understanding Rufio section, and each of them changes what the capability pages mean.

The first is the autonomy level. Every kind of work described here sits at a level you control, and Autonomy levels owns that fact in full. Each page names the level its work starts at and what moving that level would change, but none of them re-explains the system.

The second is the set of things Rufio won't do regardless of level, which Limits and boundaries owns. When a page here says Rufio stops at a particular point, that stop is usually one of those lines rather than a gap waiting to be filled in later.

What isn't here

These pages explain the work. They don't list it. For the complete inventory — every capability, and whether each one is available to you today — see Every capability, which is generated from the same data the product itself runs on and therefore can't quietly drift away from what's true.

Every page states which of its work is available to any business, which depends on your business type, and which needs something connected before it runs at all. Where something needs setting up first, the page says so plainly rather than describing it as though it works on day one.