Control
Nothing reaches a customer without you
The actions that leave your workspace or move money stop and wait for a person — by default, in the channel you already watch, with what was proposed and what you decided kept on the record.
The request arrives where you already are, with what triggered the run, the draft as written and the account it would use. Approve it, change one line, or stop it. The run holds until you do, and the record keeps all three: what was proposed, what you decided, what was carried out.
On by default · Approve, edit or reject · In WhatsApp, Slack, Telegram or Awish · Kept on the record
Which actions wait
Not a setting you have to remember to switch on. This is how a workflow behaves before you configure anything.
Anything that reaches a person outside your workspace
An email, a message, a reply to a customer. The draft is written and then held, with the recipient and the text in front of you.
Anything that moves money
Refunds, payouts, credits and payment changes hold for a person regardless of the amount, unless you have set a threshold that says otherwise.
Anything published
Posts, listings and public status updates wait, because a published mistake cannot be recalled by the workflow that made it.
Anything the plan marked
The approval points are shown in the plan before you agree to it, so the gates are never a surprise at run time.
Where you approve
In WhatsApp, Slack or Telegram, or in Awish itself. The request arrives with the context it needs — what triggered the run, what the workflow proposes to do, and which account it would use — so the decision does not require opening another tab.
You can approve it, edit it before it goes, or reject it. Editing is the option that matters most in practice: the workflow is usually right about the shape of the action and wrong about a detail, and rewriting one line is faster than describing the whole thing again.
What the record keeps
What was proposed
The action as the workflow drafted it, before anyone touched it.
What you decided
Approved, edited or rejected — with the edit, if you made one.
What was carried out
The action as it actually ran, which is not always the same as what was proposed.
Common questions
Can I turn the approval gate off?
You can raise a threshold so that routine actions below it run without asking — a refund under a limit you set, for example. What you cannot do is remove the gate from a category by accident: it is the default, and lowering it is a deliberate change you make per workflow.
What happens while an action is waiting?
The run holds at that step. It does not time out into sending, and it does not skip ahead to the steps after it — a workflow that could continue past an unanswered gate would not be an approval gate.
Who is allowed to approve?
The person or channel the workflow was set up to ask. An approval arriving from anywhere else is not accepted, which is what stops the gate from being bypassed by a message that merely looks official.
See the gate before you trust it
Describe a workflow that touches a customer. The plan will show you where it stops, before anything connects.
Free plan · No credit card required