Approval cards

What an approval card is, which actions produce one, and how to configure what needs approval.

What an approval card is

When Heyno is about to act on your behalf in a way that has an effect outside the conversation, like sending an email, delivering a quote, or posting an update, it stops and shows an approval card instead of proceeding.

The card contains exactly what would be sent, to whom, and what triggered it. You approve it, edit it first, or decline it. Nothing goes out on a timer and nothing goes out because the card was ignored.

Which actions require one

Anything that leaves the system and reaches another person. Sending mail, sending a text, delivering a quote, publishing an update, and anything that moves money are all in this category by default.

Reversible internal work does not produce a card. Drafting, filing, tagging a record, adding a calendar hold and preparing a quote that has not been sent are all things anyone can undo in seconds, and stopping for approval on each one turns the assistant into a form to fill in.

The line is drawn at the point where an action becomes visible to somebody outside your business, because that is the point at which it stops being reversible in practice even when it is reversible in principle.

Configuring approvals

The set of actions that require approval is configurable, and high-risk categories are off by default rather than on. Turning an action on is an explicit decision, and it is recorded as one.

Approvals can be scoped by role, so the people who may approve a payment are not necessarily the people who may approve a reply to a customer.

Where cards appear

In the chat where the work happened, and as a notification if you are not there. Approving from the notification is a single tap and does not require opening the app first.

An approval that is never answered stays outstanding rather than expiring into an action. It appears in the day queue until somebody deals with it.