Skip to main content

Approve Automated Emails Prior to Sending

How to put a guard infront of automated emails prior to them going out

Written by Jarrett White

Email Approval for Automations

Overview

Broki now lets you require manual approval before automated emails are sent to clients. When building an automation that includes a Send Email action, you can enable a new Require Approval Before Sending option. Instead of sending automatically when the trigger fires, the email will be held in a pending queue where you can review, edit, approve, or reject it before it goes out.

This gives you full control over client-facing communication while still benefiting from automated triggers.


How It Works

When you set up an automation with a Send Email action, you configure it as usual:

  1. Choose your trigger (e.g. Pipeline Stage Change — any stage to "Under Review")

  2. Add a Send Email action

  3. Select your email template

  4. Choose the recipient(s) — Client, All Borrowers, Mortgage Advisor, or Admin

  5. The user's email signature will automatically be added to the email before sending

Normally, once the trigger fires, the email sends immediately and automatically. With the new Require Approval Before Sending option enabled, the workflow behaves differently:

  • The automation still triggers as expected when the condition is met (e.g. moving a file to "Under Review")

  • In the Automations tab, the workflow will show that it has run

  • However, the email itself is not sent — it's held for review


Reviewing Pending Emails

Once an automation with approval enabled has triggered, the email is added to your dashboard under Communications Pending Approval.

From here, you can:

  • Approve — sends the email exactly as queued

  • Reject — discards the email; it will not be sent

  • Edit — make changes to the message content before approving and sending

This gives you a final checkpoint to make sure exactly the right message goes out to your client.


Why Use This Feature

💡 Stay in control of automated communication. If you've ever hesitated to fully automate client emails because you wanted final say over what gets sent, this feature solves that — automations still run on schedule, but nothing reaches the client without your sign-off.

💡 Catch mistakes before they're sent. If a file was moved to the wrong stage, or a template needs a small tweak for a specific client, you can edit or reject the email before it goes out.

💡 Combine with existing automation best practices. This pairs well with adding a short Wait step before your Send Email action — giving you a queue of pending approvals to review on your own schedule rather than reacting in real time.


Quick Reference

Setting

Behavior

Require Approval — Off (default)

Email sends automatically as soon as the trigger fires

Require Approval — On

Automation runs (shows in Runs counter), but the email is held in Communications Pending Approval until you approve, reject, or edit it


Have feedback or ideas for how this feature could be expanded? Let your Broki account manager know.

Did this answer your question?