Why every send should wait for a yes

Anything your company sends is signed with your company’s name. An email to a customer list, a post on the company page, a new landing page. Once it is out, you cannot take it back. People have seen it, forwarded it, and screenshotted it.

That is why the cost of a mistake in a send is so different from the cost of a mistake in a draft. A draft can be wrong and nobody minds. A send that is wrong becomes a story.

The case against full automation

Automating the sending is tempting, because the sending is the visible step. But the sending is also the cheapest step to do by hand. Pressing a button takes a second. The expensive work is the writing, the checking and the preparation, and that is where an assistant helps most.

• Drafting is slow and benefits from help.
• Judging is quick and benefits from a person who knows the customer.
• Sending is instant and cannot be undone.

So give the slow part to the machine and keep the judging with a person. You lose almost no time, and you keep the one control that matters.

What a good approval step looks like

• It shows the real thing that will go out, not a summary of it.
• It shows the details that make a send risky, such as the audience, the sender and the time.
• It is quick to say yes and easy to say not now.
• It leaves a record of who approved what.

How Levric does it

In Levric, Chief never sends, posts or publishes on its own. Every email, post and page waits for a person to say yes. On Home, each one shows up as a card under "Waiting on you" with the content and the details to decide, such as who it goes to, from which address, and when. You can approve it, choose Not now, or open Details first.

Chief can do all the work up to that point, so the yes is the only step left for you.