Quick Answer: Email marketing with a built-in CRM means your outbound campaigns read from and write to the exact same contact database as your deals, projects, and support history, instead of a separate email tool with its own list you have to sync. MiOpsAI's version of this is Dispatch, a $125 a month flat add-on on top of any base plan, running on the same contacts, tags, and suppression list as the MiOpsAI CRM. It is the right move for teams juggling multiple clients or a CRM that already governs their relationships. It is the wrong move for teams with deep, already-working martech stacks built around a specialist like ActiveCampaign or HubSpot.
"Built-in CRM email marketing" gets thrown around as a feature bullet, but it rarely gets defined. Most people assume it means the email tool and the CRM happen to be made by the same company, with an integration connecting them behind the scenes. That is not what it means, or at least not what it should mean. A true built-in model means there is no second contact database at all: one list, one suppression rule, one source of truth, and the email tool is a view into that same data rather than a separate destination for it. This piece walks through what that actually looks like, what it changes operationally, and, just as importantly, who should not bother switching.
What Built-In CRM Email Actually Means
Strip away the marketing language and there are really only two architectures for email plus CRM:
- Two databases, connected. Your CRM has a contacts table. Your email tool has its own contacts table. An integration, native or via Zapier, pushes records back and forth on a schedule or a trigger. This is how most "CRM integrations" work, including many that get marketed as seamless.
- One database, two views. Your CRM and your email sender query the same underlying contact table. There is no sync job, no field mapping, no delay, and no risk of the two systems disagreeing about who is subscribed.
The second model is what "built-in" should mean, and it is the model MiOpsAI Dispatch uses. Every contact you email through Dispatch is a CRM contact. Every unsubscribe, hard bounce, or spam complaint updates the same suppression flag the CRM sees, so a contact who opts out of email in one context is honored everywhere, not just inside that one campaign tool. We wrote a longer breakdown of why the two-database version of this problem is so common and so quietly expensive in The Two-Database Problem, if you want the deeper operational case.
How Dispatch Works Inside the CRM
Dispatch is not a separate product with its own login and its own pricing page. It is an add-on that activates inside a MiOpsAI plan you already have, and it inherits the CRM's contact records rather than asking you to import them. In practical terms:
- Smart lists and static lists. Dynamic, self-updating lists (an "Active Clients" list is the common example) stay current automatically as CRM records change. You can also build static lists, apply bulk filters, or import a CSV or a HubSpot export with deduplication when you are bringing a client's existing list over.
- A drag-and-drop designer. Built on GrapesJS, it compiles to responsive, Outlook-safe table HTML, ships with a starter template gallery, and accepts custom HTML if your team already has templates worth keeping.
- SallyAI drafting. SallyAI can propose full campaign concepts and generate on-brand templates from a brand kit, a marketing profile, and real send performance data. Sally drafts. A human always reviews and clicks send. Sally never auto-sends a campaign on its own.
- A real preference center. Recipients see friendly subscription categories, never your internal list names, with an always-present one-click unsubscribe that keeps sends CAN-SPAM compliant.
- Analytics that tie back to the contact record. Delivered, unique and total opens, clicks, click-to-open rate, hard and soft bounces, per-link click data, and recipient-level status, all exportable to CSV and all visible against the same contact you already track deals and support threads for.
- Your own sending domain. Campaigns send from your verified domain, not a shared or agency-branded address.
Pricing is flat: $125 a month on any MiOpsAI plan tier, including 10,000 outbound emails a month. It is not metered per contact, and the fair way to compare it against a standalone tool is base plan plus $125, never $125 alone, since Dispatch does not exist without a base MiOpsAI plan underneath it.
Who Should Consolidate Email Into Their CRM
This model earns its keep for specific kinds of teams, not everyone:
- Agencies and consultancies managing multiple client accounts. Every client is a separate contact segment inside one database instead of a separate email tool subscription and a separate suppression list to maintain per client.
- Teams whose CRM already governs the relationship. If deals, projects, and support tickets already live in your CRM, adding email to that same record means your list, your recency data, and your engagement history are one thing, not three things you cross-reference manually.
- Teams tired of sync jobs and duplicate suppression lists. If someone unsubscribes and still shows up in a campaign three weeks later because two systems disagreed, that is a built-in-email problem waiting to be solved.
- Teams that want one predictable bill. A flat $125 add-on is easier to budget against than a per-contact tier that climbs as your list grows across multiple clients.
If any of that describes your team, see how to choose email software when you manage multiple clients for a fuller decision framework, and what a smart list actually is if dynamic segmentation is the piece you are trying to understand.
Who Genuinely Should Not Switch
This is the part most vendor content skips, and it is worth being direct about it. Consolidation is not automatically the right call.
- Teams with deep, working martech already in place. If your marketing team has years of automation logic built in ActiveCampaign or HubSpot, with branching journeys, lead scoring, and attribution reporting tuned over time, ripping that out to save money on a flat add-on is a bad trade. The migration cost and the feature gap both cut against you.
- Teams whose core need is complex, branching automation. Dispatch's drip and nurture sending lives inside the CRM's email sequences, not as a standalone visual journey builder with conditional branching. According to ActiveCampaign's published pricing page, its automation engine is built specifically around that kind of branching logic, and per HubSpot's published pricing page, Marketing Hub's automation and attribution tooling is similarly deep. If that depth is the actual job to be done, a specialist tool still wins.
- Teams that need SMS or paid-ads management in the same tool. Dispatch does not include either today.
- Teams that weight deliverability history heavily. Dispatch is newer to email sending than Mailchimp or Constant Contact, both of which carry over a decade of sender reputation and deliverability tooling. If your list is large and deliverability is your single biggest risk, that track record has real value.
- Teams whose event marketing is a core channel. Constant Contact's bundled RSVP and event tooling covers a use case Dispatch does not attempt to replicate.
None of these are edge cases. They are common, legitimate reasons to stay put, and a vendor that will not say so plainly is not being honest with you.
Feature Comparison: Built-In vs Standalone
The table below compares the built-in model (Dispatch, on top of a MiOpsAI base plan) against the general shape of standalone email tools that connect to a CRM through an integration rather than sharing its database. Specific competitor pricing is attributed to each vendor's own published pricing page and should be confirmed there, since contact-based tiers move as lists grow.
| Capability | MiOpsAI Dispatch (built-in) | Typical standalone email tool |
|---|---|---|
| Contact database | Same database as the CRM, no export or import | Separate database, synced via native integration or Zapier |
| Suppression list | Shared platform-wide (unsubscribes, bounces, spam flags) | Local to the email tool unless sync runs cleanly on schedule |
| Pricing model | Flat $125 a month add-on, any plan tier, 10,000 sends included | Usually tiered per contact, per ActiveCampaign's, Mailchimp's, and Constant Contact's published pricing pages |
| Automation depth | Email sequences inside the CRM, no standalone branching journey builder | Often deeper, with visual branching journeys, especially ActiveCampaign and HubSpot |
| AI campaign drafting | SallyAI drafts templates and concepts from brand kit and performance data, human sends | Varies by vendor, ranges from none to AI subject line suggestions |
| SMS and paid ads | Not included | Some vendors bundle SMS or ads, notably Brevo for SMS |
| Deliverability track record | Newer entrant to email sending | Mailchimp and Constant Contact have over a decade of sender history |
| Sending domain | Customer's own verified domain | Customer's own verified domain, standard across most vendors |
The Fair Cost Comparison
Comparing Dispatch's $125 sticker price directly against a standalone tool's list price is not a fair comparison, because Dispatch does not run without a base MiOpsAI plan underneath it. The honest comparison is base plan plus $125 against whatever a standalone email tool costs at a similar contact volume, plus the ongoing cost of keeping that tool synced with your CRM.
For a team on MiOpsAI's Growth tier (from $449 a month, per MiOpsAI's pricing page) adding Dispatch, the combined cost is $449 plus $125, a flat number that does not move as contacts grow. A comparable standalone tool priced per contact, per that vendor's own pricing page, will climb as the list grows and does not include the CRM itself, meaning you are paying for the CRM separately either way. The gap widens further for agencies aggregating several clients' contacts into one list, since a per-contact tier counts every client's contacts against the same bill.
What Dispatch Does Not Do Yet
To repeat it plainly, since this matters more than another feature bullet: Dispatch has no standalone visual automation or journey builder, no SMS channel, no paid-ads management, and a shorter deliverability history than Mailchimp or Constant Contact. If your team's actual bottleneck is branching automation complexity, event marketing, or SMS, a specialist tool solves that problem better today. Dispatch's advantage is the shared database and the flat, predictable price, not feature-for-feature parity with tools that have specialized in email marketing for much longer. For a deeper look at how AI is changing what "good enough" automation looks like without a dedicated journey builder, see AI email marketing explained, and for a head-to-head against the automation leader specifically, read Dispatch versus ActiveCampaign.
How to Decide
- If your CRM already governs the relationship and email syncing is a recurring headache, consolidating into a built-in model like Dispatch removes that headache entirely.
- If you manage multiple client accounts and pay for a separate email tool per client, a shared database and one flat add-on price is usually a meaningful savings, both in dollars and in hours spent reconciling lists.
- If your team relies on deep branching automation, SMS, paid-ads management, or a proven decade-long deliverability record, stay with the specialist tool that already does those things well. Do not switch just to save money on an add-on if it costs you the features your program depends on.
For agencies specifically weighing every option, not just this one, our ranked guide to email marketing software for agencies compares Dispatch against five other tools side by side.
Frequently Asked Questions
What does built-in CRM email marketing actually mean?
It means the email tool and the CRM share one contact database rather than two separate databases connected by an integration. Every unsubscribe, tag, and engagement event updates the same record the CRM uses, with no export, import, or sync job in between.
How much does MiOpsAI Dispatch cost?
Dispatch is a flat $125 a month add-on on top of any MiOpsAI base plan, and it includes 10,000 outbound emails a month. It is not priced per contact. See MiOpsAI's pricing page for current base plan tiers.
Does Dispatch replace a dedicated marketing automation platform?
Not fully. Dispatch handles drip and nurture sending through the CRM's email sequences, but it does not include a standalone visual journey builder with branching logic the way ActiveCampaign or HubSpot Marketing Hub do. Teams whose core need is complex branching automation should still evaluate those tools directly.
Who should not consolidate email into their CRM?
Teams with deep, already-working automation built in a specialist tool, teams that need SMS or paid-ads management in the same platform, and teams that weight a long deliverability track record heavily should generally stay with their current setup rather than switch for the sake of consolidation.
Can SallyAI send campaigns without a human reviewing them first?
No. SallyAI can draft full campaign concepts and on-brand templates from a brand kit, marketing profile, and past performance data, but a human always reviews and sends. SallyAI never sends a campaign on its own.
How does shared suppression actually work in practice?
If a contact unsubscribes, hard bounces, or marks a message as spam anywhere in the platform, that suppression status is honored across every future send to that contact, since there is only one contact record and one suppression flag, not a separate list per campaign tool.
If keeping your contact list and your campaign tool in sync has become its own part-time job, request access to see Dispatch running on your own CRM data, alongside the rest of the MiOpsAI CRM.