AI News

How to Use Brew to Create an Email Campaign

Brew is an AI email marketing platform built around a simple workflow: describe the email you want, review the generated campaign, edit it, test it, then send or schedule it. Brew now calls these one-off sends Emails; the original Campaigns documentation link redirects to its Emails guide. Newsletters, product announcements, promotions, and event invites fit this workflow. Event-triggered Automations are a different workflow.

Public documentation checked: October 4, 2026 (UTC). The original article was published in May 2026. This workflow follows current official documentation; Kingy.ai did not connect a Brew account, change DNS, import contacts, generate an email, or send a test or campaign for this update.

Before starting, sign in and add your brand. Check your account’s AI-credit, email-send, and domain allowances in Billing. Brew’s public product page and Plans and Limits guide currently disagree on domain allowances; the guide also carries its own August 17 verification label. Confirm your account limits before committing to a campaign. Generation and optional validation can consume credits.

You decide who should receive the campaign, what it offers, and whether its claims, links, and unsubscribe details are ready to send.

1. Set Up Your Sending Domain First

Before you send to a saved audience, verify a sending domain you own and select its Marketing sending purpose. Brew’s domain verification guide says audience emails require that purpose; transactional domains are for a different automation workflow. A personal test can use Brew’s default sender before domain verification, so you can try the design first.

Brew recommends using a subdomain such as mail.yourdomain.com, updates.yourdomain.com, or news.yourdomain.com instead of your root domain. This helps keep your main domain more isolated if deliverability problems appear later.

You will also need to add the DNS records provided by Brew. Its domain guide requires DKIM and SPF and describes DMARC as optional but recommended. That setup note does not override mailbox-provider requirements. Google’s email sender guidelines for personal Gmail require SPF or DKIM for all senders; its section for sending 5,000 or more messages per day to personal Gmail accounts requires SPF, DKIM, and DMARC, From-domain alignment, and one-click unsubscribe plus a visible body link for marketing/subscribed messages. Google also requires TLS, valid forward/reverse DNS, and spam rates below 0.3%. Check the applicable sender requirements before sending.

2. Build or Import the Right Audience

A campaign is only useful if it goes to the right people. Brew’s Create Audiences guide describes saved filters as dynamic segments. Properties such as trial status, demo booking, or purchase date must already exist on your contacts before you can filter on them. Saved filters can check whether a contact opened or clicked, but not when it happened. Date-bounded engagement cohorts use event snapshots through the documented API/MCP path; these are frozen and need rebuilding when you need a current cohort. Review the matching contacts before saving or sending.

For example, you might create an audience for:

  • Trial users who have not booked a demo
  • Customers who clicked a previous launch email
  • A date-bounded engagement cohort built from event history, rather than an ordinary saved open/click filter
  • Recent buyers who should receive a product update

If you are moving from another email platform, Brew supports CSV contact uploads. The original CSV Upload documentation link now opens Add Contacts. Email is required; first and last names are recommended. Review column mappings and carry over opt-outs with Subscribed=false or a supported exported status. New contacts default to subscribed if that column is omitted; the documented importer does not re-subscribe prior opt-outs. Uploading data is not permission to email it. Optional address validation consumes credits.

Do not use purchased lists. Brew’s Audience Hygiene guide says contacts should have explicitly opted in, and list quality directly affects deliverability.

3. Write a Specific Campaign Prompt

Brew works best when the prompt is clear. Its Prompt Guide recommends naming the goal, audience, tone, structure, and any brand assets you want used.

A weak prompt would be:

Create an email campaign for our product.

A stronger prompt would be:

Create a one-off product announcement email for existing customers. We are launching a new analytics dashboard. The audience is SaaS founders and marketing leads. Use a clear, practical tone. Include one CTA to try the dashboard. Keep the email concise, with a subject line, preview text, short intro, three feature bullets, and a final CTA.

That brief specifies the audience, offer, structure, and action you want. It is an example prompt, not a campaign Kingy.ai generated or evaluated.

4. Review the Generated Email on the Canvas

After you submit the prompt, Brew’s Emails documentation says the email appears on the canvas. Select it to edit manually or through chat, create variants, or send a test. For another email service provider, use Send → Export template; the destination must be a supported ESP integration you have already connected. Exporting a design does not perform the send or verify its recipient settings in the other service.

Do not treat the first draft as finished. Check:

  • Subject line accuracy
  • Preview text
  • CTA destination
  • Product claims
  • Pricing or offer details
  • Spelling and formatting
  • Mobile readability
  • Footer and unsubscribe details
  • Whether the message matches the audience’s actual stage

This is especially important if your campaign mentions dates, pricing, availability, integrations, or legal/compliance claims.

5. Create Variants Before You Decide

Brew can generate variants without deleting the original version. For example, you can ask for three subject line options, a shorter version, or a version aimed at a different segment.

Useful follow-up prompts include:

Create three subject line variations: one direct, one curiosity-driven, and one benefit-led.

Make this email shorter and more executive-friendly.

Create a second version for enterprise buyers, with less emphasis on speed and more emphasis on control, reporting, and adoption.

Compare a few realistic variants, then choose the one that fits the audience and offer.

6. Send a Test Email

Before sending to your audience, select the email on the canvas and click Test. Brew’s first-email guide documents entering your own address and choosing Send test; that test uses Brew’s default sender and does not need a verified sending domain. The Emails guide also recommends testing with yourself or a teammate. This preview does not verify authentication or deliverability from your eventual campaign domain.

Open the test email on desktop and mobile. Click every link. Read the email like a subscriber, not like the person who wrote it.

A good campaign should make the next step obvious. If the reader has to work to understand the offer, the email is not ready.

7. Send Now or Schedule

When the campaign is ready, click Send, choose a saved audience and verified Marketing-purpose domain, and review sender details and the actual recipients. Brew’s Send Options guide says unsubscribed, suppressed, and undeliverable contacts are skipped. Choose Send now or Schedule for the basic workflow; the current app also offers Intelligent and Gradual send. A schedule can be saved even if nobody currently qualifies, so recheck the audience and timing before it runs.

This is the moment to slow down. Make sure the audience is correct. Make sure the sender name is recognizable. Make sure replies go to a real monitored inbox, not a dead address. Brew’s domain guide specifically recommends using a real reply address instead of no-reply.

8. Stay Compliant

For commercial email in the United States, the FTC’s CAN-SPAM compliance guide requires accurate sender/header information, honest subject lines, clear advertising identification, a valid physical postal address, and an easy opt-out. It covers business-to-business commercial email too. Keep the opt-out mechanism available for at least 30 days and honor requests within 10 business days. Hiring an email platform does not remove the sender’s responsibility. These are core U.S. requirements, not a complete statement of every law that may apply to your recipients.

Brew can help with the email workflow, but compliance is still your responsibility. If your campaign is promotional, make sure it is honest, easy to unsubscribe from, and sent only to people you are allowed to contact.

Before Sending

A personal preview using Brew’s default sender can come before domain verification. Before an audience campaign, verify your owned Marketing-purpose domain, check authentication, and confirm your account limits.

Import or segment opted-in contacts and preserve opt-outs. Write a specific prompt, review the email, compare a few variants, then test its links and layout on desktop and mobile.

Before choosing Send now or Schedule, recheck the actual recipients, sender and reply-to details, timing, unsubscribe controls, postal address, and applicable sender requirements.