Why every AI-written customer message should wait for a person

An AI agent that writes a good reply ninety-five times out of a hundred is useful. The same agent sending all hundred unchecked is a liability: the five bad ones quote the wrong price, promise a delivery date nobody agreed, or answer a message that was really a complaint.

What an approval queue should show

A person deciding in five seconds needs four things in one place: who it goes to, which account it goes from, the full text, and the conversation it answers. Apavin's queue shows all four, plus which connected client asked for it.

Approve, decline or let it expire

Approving sends the message once. Declining means it never leaves Apavin, and the agent sees that it was declined. Scheduled follow-ups wait in the same queue and can be cancelled at any time before they send, by you or by the agent with cancel_scheduled_message.

Sent exactly once

Agents retry. Networks drop. Every send request carries an idempotency key, and Apavin claims the message before sending it, so a retried request returns the original result instead of a second email.

When is auto-send reasonable?

When the reply is narrow and the rule is written down. On Growth, an admin can allow auto-send for replies only, with a daily cap and one switch that turns it off. Everything sent this way is in the audit log with the rule that allowed it.

Is approval available on the Free plan?

Yes. The Free plan sends email after approval. Standard adds WhatsApp. See pricing.