Who approved that email? Keep the record.
When an automated email goes out under your company’s name, someone should be able to say who asked for it, who built it and who said yes. Most teams cannot.
· Automations · 3 min read
Three months after a campaign launched, someone asks why the prospects from one region got an email about a price that has since changed. You search the tool. The sequence is there. Nobody knows who built it, who read it first or whether anyone did.
This is not a technology problem. It is a record problem, and it gets worse the more you automate.
What you want to know about every automation
- What it does, in a sentence a colleague could read.
- Who asked for it.
- Who set it up.
- Who approved it, and when.
- How many people have gone through it and how many emails it has sent.
- Whether it is on or off right now.
If those six facts sit next to the automation itself, an audit takes a minute instead of an afternoon. If they live in someone’s memory or a chat thread from March, they are gone.
Approval is where accountability starts
An email that goes to a hundred people is a public statement. It should be read by a person before it goes. That is not a slowdown, it is the step that makes the rest safe to speed up. Whoever approves should be able to see the actual emails, not a summary of them.
How Levric does it
Every automation in Levric lists what it does, who asked for it, who set it up, who approved it and when. Next to that you see how many people entered and how many emails were sent, with an On badge so the state is never a guess.
New work waits in a "Waiting for your approval" area. Chief writes the email, and you choose Approve and send, Edit or Don’t send. Chief never sends anything on its own, so the name in the approval column is always a person on your team.
See it in the app: the Automations tour