"Automated approval" means two different things, and the difference is the whole question.
The first meaning is approval software: a request is routed to the right person, who clicks approve, and the system records the click. The second meaning is the one owners actually worry about when they let software do their work: which changes may happen without me, and which must wait until I have looked?
This post is about the second meaning. It is how Tensor Autonomous is built, and it is a useful way to think about any tool that writes to your calendar, your sheet, your inbox or your customers.
Start with the change, not the task
Every piece of office work ends in a change somewhere: an event on a calendar, a row in a sheet, an email in someone's inbox, a document edited. Reading is harmless. Writing is where trust is spent.
So the rule to set is not "may the software do this task?" but "may it make this change without me?" Sorted that way, most work falls into three piles:
- Routine changes you would approve every time. Logging a request in your tracker. Drafting the acknowledgement of an inquiry. Adding a booking at a time you have said is free. Drafting the day-5 check-in on an open quote.
- Changes that depend on judgment. A price. A date you have not offered. A reply to a complaint. Anything to a customer you have not heard of before.
- Changes that should never be automatic. Payments and refunds. Contract terms. Anything legal, medical or to do with staff.
Pile 3 is easy: it stays with people. Pile 2 should always wait for you. Pile 1 is where automation pays, and where most tools get the control wrong: they either ask about everything, which trains you to click approve without reading, or nothing, which is how a bad email reaches forty customers.
How Tensor handles it
Tensor is one agent doing your office work inside limits you set. Three things make the limits real.
It asks before it writes or sends. When a task reaches a change, Tensor shows you exactly what it will change and where: the calendar event with its time and attendee, the sheet row with every cell, the draft with its recipient and text. You approve it, edit it or decline it. Nothing is written until you do, and nothing it drafts is sent until you send it. This is the default for every new responsibility.
You set limits for routine work. Once you have approved the same kind of change a few times and trust it, you tell Tensor which changes may run by themselves: which kinds of change may run without asking (adding a row, creating a draft, adding an event), a daily cap, a days-and-hours window, and for each write an amount ceiling and a limit on recipients. Within those limits it works without asking. Outside them it stops and asks. Sending email, payments and refunds, and moving or cancelling a calendar event always ask; limits can't cover them. You can tighten or widen the limits any time, and a responsibility you are unsure about can stay on ask-every-time for good.
Every run leaves a receipt. After it writes, Tensor reads the record back from where it was written and compares it with what it sent: the event, the row, the sent message. The receipt shows what it read, what it changed, who approved it and when, and whether the read-back matched. If something looks wrong a week later, the receipt is where you look, and Undo removes what a bad run created after you confirm what will be removed.
That is automated approval in the second sense: the routine runs by itself within your limits, the judgment calls wait for you, and you can always see which was which.
What this looks like on a Tuesday
You hand Tensor a showing request at 9:41. It checks the showings calendar and proposes the booking: Thursday 11:00–11:30, within your showing hours. The proposal sits in front of you with one button. You approve it at 9:44. The event lands on the calendar, Tensor reads it back, and the receipt shows it matched.
Next month, after a dozen of those, you set a limit: Tensor may book without asking on weekday mornings, up to three a day. You hand it the requests; the bookings appear; the receipts pile up; you read them on Friday. The one request that asks for a Sunday evening, outside your showing hours, books nothing, and Tensor tells you why. Sending email, and moving or cancelling an event, always ask.
Choosing software by this rule
Whatever you are evaluating, ask three questions:
- Does it show me the exact change before it happens, in my own systems, not a summary?
- Can I set limits for the routine changes, and does it stop at the edge of them rather than guess?
- Does it read the result back and keep a receipt I can check later?
Approval-routing software answers the first question for human requests. Most automation tools answer none of them for their own writes. Tensor is built to answer all three, for the work of a small business: inquiries, bookings, logs, follow-ups, documents.
Where to start
- Product: how responsibilities, approvals and receipts fit together.
- Try it live: a real task on sample data, and you approve the change before it happens.
- Security: where credentials live and what Tensor can and cannot reach.
- Plans from $149 a month: Starter, Operator and Operations Team.
Related reading
See it in a demo
Watch Tensor propose a change, wait for your approval, make it, and hand you the receipt.