Managing Campaigns

Campaign management in Dispatch Pro is identical to Core — draft, send, pause, resume, and review history. Pro adds one editor mode: the Visual Builder.

Editor modes

Visual Builder (Pro) — drag-and-drop email design; click “Open Visual Builder” to launch the GrapesJS editor in a modal, design your email, save and return. Best for designed, image-rich campaigns.
Template Mode (Core) — write content in a structured form; Dispatch wraps it in your saved HTML template. Best for consistent branding with minimal effort.
Raw HTML (Core) — paste or write complete HTML. Full control; you are responsible for inline styles and email-client compatibility.

When to use which mode

Use Visual Builder when you want a designed, multi-column layout with images, buttons, and custom styling — no HTML needed
Use Template Mode for simple text-and-link newsletters where consistent branding matters more than design flexibility
Use Raw HTML when you want to bring in a design from Figma, an email tool, or a hand-crafted template

Merge tags in Visual Builder

Merge tags work in Visual Builder the same way they do in Raw HTML — type them directly into any text element in the canvas:

{{first_name}} — subscriber’s first name
{{email}} — subscriber’s email address
{{unsubscribe_url}} — unique one-click unsubscribe link
{{site_name}} — your WordPress site name
{{site_url}} — your WordPress site URL

Everything else

Sending, pause/resume, test sends, and campaign history all work identically to Core. See Dispatch Core — Managing Campaigns for the full workflow, or Visual Builder for a detailed guide to the drag-and-drop editor.

Next: Subscriber Management

Dispatch Pro

Premium self-hosted email marketing for WordPress. Everything in Core, plus the Visual Builder, customizable transactional emails, and CSV import/export.

Quick Links

Need support?

Dispatch Pro Support →

// real.developer.js

                        const approach = {
                    
                        investors: false,
                    
                        buzzwords: false,
                    
                        actualUse: true,
                    
                        problems: ['real', 'solved']
                    
};
// Ship it.

Built by People Who Actually Use the Software

M Media software isn't venture-funded, trend-chasing, or built to look good in pitch decks. It's built by developers who run their own servers, ship their own products, and rely on these tools every day.

That means fewer abstractions, fewer dependencies, and fewer "coming soon" promises. Our software exists because we needed it to exist — to automate real work, solve real problems, and keep systems running without babysitting.

We build software the way it used to be built: practical, durable, and accountable. If a feature doesn't save time, reduce friction, or make something more reliable, it doesn't ship.

✓ Every feature solves a problem we actually had

✓ No investor timelines forcing half-baked releases

✓ Updates add value, not just version numbers

✓ Documentation written by people who got stuck first

This is software designed to stay installed — not be replaced next quarter.

🤖

Support Bot

"Have you tried restarting your computer? Please check our knowledge base. Your ticket has been escalated. Estimated response: 5-7 business days."

❌ Corporate Script Theater

👨‍💻

Developer (M Media)

"Checked your logs. Line 247 in config.php — the timeout value needs to be increased. Here's the exact fix + why it happened. Pushed a patch in v2.1.3."

✓ Real Technical Support

Support From People Who Understand the Code

Ever contact support and immediately know you're talking to someone reading a script? Someone who's never actually used the product? Yeah, we hate that too.

M Media support means talking to developers who wrote the code, understand the edge cases, and have probably hit the same problem you're dealing with. No ticket escalation theatrics. No "have you tried restarting?" when your question is clearly technical.

Documentation written by people who got stuck first. Support from people who fixed it.

We don't outsource support to the lowest bidder or train AI on canned responses. When you ask a question, you get an answer from someone who can actually read the logs, check the source code, and explain what's happening under the hood.

✓ Real troubleshooting, not corporate scripts

✓ Documentation that assumes you're competent

✓ Email support that doesn't auto-close tickets

✓ Updates based on actual user feedback

Managing Campaigns