Approval Workflow

Approval workflows are a core safety mechanism in Sarudo. Any action that has real-world consequences — sending an email to a client, making a phone call, processing a payment, or publishing a social media post — requires your explicit approval before execution. This prevents accidental sends, ensures you have reviewed all content, and keeps you firmly in control. The approval system is not optional and cannot be bypassed.

The following actions always require your approval: sending emails (both new and replies), making outbound phone calls, processing payments or refunds through Stripe, publishing or scheduling social media posts, sending invoices, and executing any action that involves external communication or financial transactions. Actions that do not require approval include searching the web, checking your calendar, looking up CRM data, creating document drafts, and storing knowledge — these are internal operations with no external impact.

When your AI employee is ready to execute an approval-required action, it presents a detailed preview of what it is about to do. For emails, you see the full draft including subject, recipients, and body. For calls, you see the number and the conversation script. For payments, you see the amount and recipient. You then respond with /approve to proceed or /deny to cancel. You can also ask for modifications before approving — the AI will revise and present the updated action for approval.

If you do not respond to an approval request, the action simply does not execute. There is no timeout that auto-approves actions. Your AI employee will wait indefinitely for your response. If you start a new conversation or move to a different topic, the pending approval remains available — you can come back to it later. However, for time-sensitive actions, the AI may remind you that an action is pending approval.