How approval works
When AI proposes a write action, Flowforce should show a confirmation card. The user can approve, reject, or edit before the action is saved or sent.


Common action types
- Create a task with owner and due date.
- Draft an email or SMS for review.
- Log a note or call summary.
- Recommend cadence enrollment.
- Suggest a stage change or next step.
Review before approving
- Open the source evidence.
- Check recipient, record, and owner.
- Edit tone and facts.
- Confirm consent and opt-out status for outbound actions.
- Approve only when the action matches your workflow.

Audit trail
- Approved actions should record who approved them.
- Edited actions should preserve the final text or task state.
- Rejected actions should remain visible in history when supported.
- Agent proposals should also appear in AI Agent run history.
