Now
Autonomy Dial — slide to set how much rope Otto gets
Off = Otto never sends this type · Draft = he writes it, you approve it · Auto = he sends it himself. Enforced in his code, not just policy.
Activity
Approval Queue
Approve sends as-is. Edit then approve and Otto studies the diff plus your note to learn your voice. Reject with a reason and he learns what not to do.
Chat with Otto
Quick Start — turn on with one tap
Build Your Own Routine
Saved Routines
How The Tower works — plain English
Home shows what Otto is doing right now, his recent activity, and the Autonomy Dial.
The dial is per-type-of-message: off means Otto never sends that type, draft means he writes it but
it waits for your approval, auto means he sends it himself. Everything starts on draft. The red Pause button
stops all new work instantly.
Approvals is your morning coffee screen. Go down the line: tap Approve to send
as-is. If you change the wording first, Otto studies exactly what you changed and the reason you type in, and he
writes more like you next time. Rejecting with a reason teaches him too. The more you edit early on, the less
you'll need to later.
Chat is a direct line to Otto, same as Telegram, answers usually within a minute.
Tasks is where routines live. Use Quick Start to turn on the standards with one tap,
or build your own: pick days and a time (or a trigger event), then type steps the way you'd explain them to a new
assistant. Otto runs them on schedule and anything client-facing still goes through Approvals.
Files is Otto's brain. Click any file, read it, fix anything that's wrong, hit save.
That's how you correct his knowledge permanently, no coding involved.
P&L tracks money per client: commissions in, costs out, so you always know if Otto
is paying for himself.
Phone tip: open this site in Safari or Chrome on your phone and choose "Add to Home Screen", it installs like an app.