Skip to main content
An email send is irreversible. Once it leaves, every typo, dead link, and broken Outlook layout sits in thousands of inboxes. Your name is on all of it. The fix is a short routine you run every time, in the same order. Nothing depends on you remembering to check. This recipe is that routine. For a small internal send you might run only the first step. Before a launch announcement to your whole list, run all six.
Before you start. You need a finished email and your own inbox for test sends. Every step is also available over MCP, the API, and the API catalog in the dashboard. The table at the end lists the tool and route for each step.

1. Send a Test to Yourself

Open the email and click Test in the toolbar to send it to your own address (add a teammate too). Then read it as a recipient, in a real inbox:
  • Do the from name and address look right?
  • Do the subject line and preview text read well together in the inbox list?
  • Click every link and button. Watch for placeholder URLs left over from drafting.
  • Check merge tags: a test doesn’t read contact data, so fill firstName under Variables to see a name, and leave it blank to check that the fallback in {{ firstName | there }} reads naturally.
A test email uses no credits, though it counts toward your plan’s monthly email sends. It catches most problems. See Credits and Plans and Limits for how sends are counted.

2. Preview It Across Real Inboxes

Your inbox is one client. Your audience reads in dozens. Open the Inboxes tab in the Preview panel and run a preview across real inboxes. Brew renders the design in Gmail, Outlook, Apple Mail, and iOS by default, and returns a screenshot per client. Add Yahoo Mail by selecting it. Read the results in this order:
  • Outlook on Windows first. It uses its own rendering engine and is where layouts break most often.
  • The dark-mode variants. Look for logos that vanish and text that loses contrast.
  • The mobile clients. Confirm the layout stacks cleanly on a narrow screen.
Each preview run costs 10 credits, charged only when at least one client renders.

3. Run an Email Audit

Open the send dialog and click Audit · 5 credits, or ask Brew in chat:
“Audit this email before we send it.”
The audit checks the exact HTML, subject, preview text, and sending purpose, and returns readiness with a list of findings. Fix the blocker and error findings first, then review warnings. Understand the Result explains each part of the result. The same audit runs from any MCP-connected client via audit_email. The CLI command is brew-cli emails audit --email-id <emailId> for a saved design, or --file email.html. API callers use POST /v1/emails/audit with emailId, emailHtml, or emailJsx. A complete audit costs 5 credits. A partial audit costs 0 and must be retried before you claim that the email is ready.

4. Check Where It Lands

A design can be flawless and still arrive in spam. An inbox placement test reports where your email lands with each provider. It needs a verified sending domain, and results aren’t instant. The table below has the agent and API paths. To learn the most from one test, change only the subject line between two runs. Worth the credits before a launch. Skip it for routine sends to an engaged list.

5. Validate the List

Everything so far has been about the email. This step is about who receives it. Invalid addresses bounce, and bounce rate is one of the two metrics that decide your sending reputation. A stale list does lasting damage on exactly the kind of send this recipe is for. Open the audience you’re about to send to. Click the three-dot menu in the top right (next to Download CSV) and choose Validate contacts. Each address comes back valid, risky, or invalid, and the verdict saves onto the contact. If a check is unavailable, the contact keeps its earlier verdict. See Validate contacts. Validate the audience you’re sending to rather than your whole list. At 2 credits per address the difference adds up, and bulk validation reuses checks from the last 30 days.

6. Final Checks at the Send Screen

You’ve verified the email itself. The last mistakes happen at the send step:
  • Audience. Is the recipient count what you expect? A count that’s way off usually means the wrong saved audience or a stale filter.
  • Subject and preview text. These are set at send time, so a perfect design can still ship with a placeholder subject.
  • Schedule. Confirm the time zone if you’re scheduling in advance.
  • Footer. Brew signs the unsubscribe link at send time, so in a test email it stays a placeholder. Check that the footer shows the unsubscribe text and your mailing address.
Then send it, and read the analytics the next day rather than refreshing them all evening.

From an Agent or Code

Every step above has an agent path. They run from any MCP-connected client or from code: The final checks at the send screen are the arguments to send_email or POST /v1/sends. Those are audienceId, subject, previewText, domainId, and scheduledAt. When a confirmation request appears, read its recipient count before approving it. Repeat the call with confirmed: true and the returned confirmation_id after you approve. See Confirmation.

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

Search Documentation

Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.

Ask ChatGPT or Claude

Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.