Automation and reports
Choose routines to automate and build reports around the information you care about
What it does
This is where recurring and triggered work lives — tasks that run because a schedule or an event says so, not because you asked in the moment — plus the reports, dashboards, and business summaries that show you what happened.
Choose the level for each task. Suggest prepares work for your approval. Review carries out work you have authorized and shows you the result afterward. Automate runs routines you enable within your rules, with activity available to inspect. You can keep any task at approval, change its permissions, or pause it. See Autonomy levels for the full model.
Some of what happens here is triggered by an event rather than a clock — an invoice going overdue, a job's status changing — and some of it runs through an approval step built into the task itself before it continues. None of this is something Rufio invented on its own: a new automation or a new pattern is proposed to you, in plain language, before it exists.
On the reporting side, dashboards, reports, and business summaries are built from what's actually happened in the business, so you're reading a summary rather than assembling a chart yourself.
The agents area sits alongside this — an overview of what is running on your behalf, the voice tools, their scheduling, and the usage behind them.
When to use it
Use this for work you'd otherwise have to remember to do yourself — an overdue-invoice reminder, a weekly summary of the business, a flag when a job is taking longer than it should — and for the reports and dashboards you check on a regular basis.
Do not use this expecting Rufio to add a new recurring task on its own. Every new automation is proposed to you first, in plain language, not switched on quietly in the background.
How to use it
Example — a weekly summary that arrives without being asked:
Request: "Every Monday, prepare a summary of last week's revenue, completed jobs, and overdue items for me."
What Rufio does: every Monday, Rufio prepares a summary of last week — revenue, work completed, new customers, and anything still overdue — in a few paragraphs rather than a chart to interpret. If a job is taking longer than usual, or an invoice is still unpaid, the summary flags it rather than waiting for you to notice.
Where it stops: the summary tells you what happened and what looks off. It does not chase anyone for payment, send anything on your behalf, or change anything by itself — following up is a separate task, sitting at whatever level you have set it to.
Parameters
What Rufio needs from you for this part of the business:
| What Rufio needs | Why |
|---|---|
| Which level each task should run at | The dial is set per task, not for the whole business at once |
| Your OK before a task moves up a level | Rufio proposes moving a task to Review or Automate; it never does so on its own |
| Nothing extra for reports and dashboards | They're built from what's already tracked elsewhere in the business, not entered separately |
What you get back
At Suggest, you receive a drafted reminder or task waiting for your approval. At Review, you see the result after the authorized task runs. At Automate, the routine follows the schedule or trigger you approved, and its activity remains available for review. You decide how much oversight each task needs.
Every action taken as part of an automated task is logged: what happened, when, why, and what changed. None of this happens invisibly.
A weekly summary can bring together completed work, outstanding invoices, and jobs running longer than planned. Ask for a dashboard showing the numbers you care about — revenue by service, customer activity, or changes in margin — then adjust it with Rufio. The report gives you evidence to interpret with your knowledge of the business.
Limits
Rufio never moves money on its own. Sending a reminder can be automated; paying, refunding, or changing a price always requires you.
Rufio never invents new behavior. A new automation or a new pattern is proposed to you, in plain language, before it exists — Rufio doesn't add tasks to its own schedule.
A report or a flagged anomaly is something to look at, not something Rufio has already acted on. The summary tells you what happened; deciding what to do about it stays with you unless that specific follow-up task is separately set to act on its own.
Related
- Autonomy levels — how Suggest, Review, and Automate work, and how a task moves between them
- Every capability — the full availability table for every capability on this page
- Money — what an overdue invoice and a payment nudge actually touch
- Work and scheduling — the jobs and appointments a recurring task keeps up to date
- What Rufio does — the rest of the business, covered the same way