Human approval queue
Flozari teams can request approval for inbox drafts, while reviewer-only roles can be required to place outgoing replies into the approval queue.
The problem
Why this safeguard is needed
Not every reply should be sent without review. Pricing exceptions, complaints, legal questions, sensitive claims, and high-value conversations can create avoidable risk when the first draft goes directly to the customer.
What this safeguard helps protect
- Sensitive customer conversations
- Teams with reviewer-only permissions
- Brand, policy, or commercial claims that need a second look
How it works in Flozari
- 1
A teammate drafts the response and requests approval.
- 2
The conversation and draft appear in the pending approvals view.
- 3
An authorised reviewer approves and sends, adds context, or rejects the draft.
Good operating practices
- • Define which topics always require approval.
- • Use review notes to explain changes.
- • Keep role permissions aligned with team responsibilities.
Keep human responsibility in the loop
This control supports safer operations but does not guarantee Meta-policy or legal compliance. Your team remains responsible for consent, content, audience selection, review, and applicable requirements.
Use this safeguard as part of a responsible workflow.
Explore the related feature or return to all AI and safety controls.