Automations

Forty-six things that happen with nobody pressing anything.

Every built-in behaviour is listed, with a switch where a switch is allowed and the reason where it is not. Beside the list, a workshop where you build your own from tiles that clip together.

The manager

Every automation the product runs, in one list, pointing at the line of code where it happens. They cannot be deleted, because the behaviour is the product — but each one can be switched or configured.

One setting, two windows

A switch here moves the same setting the Settings page uses. Never two settings for one thing.

A reason where the switch would be

A STOP text, a written unsubscribe, a bounce becoming a suppression — no toggle is offered for these. The page shows why instead.

Tiles that clip

A dotted board and tiles that snap together instead of wires. What you can see is exactly the program; nothing to drag out of alignment.

Starts, joints, if, for each, wait, stop

Nine ways to start; “any of these” fans several triggers into one chain; “back together” rejoins branches; conditions, loops, delays and a full stop.

Ask AIRIS in the middle

Two AI tiles carry their own prompt and answer in a shape — yes/no, one of, a number, a list, text — so the tiles beneath can branch on what she said.

Autopilot

One tile per tool

Every assistant tool is a tile, marked with whether it asks a person first. An automation runs exactly as trusted as her own turn — a tool that asks still asks.

What this page may claim. Built automations run with the assistant's own permissions and nothing more. There is no outbound-call tile, because there is no outbound calling.

More of the desk

Start free. Upgrade when the calls roll in.

Put it on a real call today — no card, no commitment.