You no longer need an ESP to communicate with your creators. LoudCrowd's Creator Hub now has a native inbox, and every creator-facing message — automatic notifications, broadcasts, and your Welcome message — happens in-platform. You can even message individual creators directly. No ESP integrations, no email-flow design, no list-building in another tool.

Once your Welcome template and email branding are set up, creator communications run on autopilot.

Availability: Hub Messaging is available for Shopify accounts. Your Client Strategist enables it for your account.

Do I still need a Klaviyo or other ESP for creator communications? No. All creator messaging and notifications now happen in LoudCrowd. Keep your ESP for non-creator marketing (customer flows, abandoned cart, post-purchase, etc.) — those are unaffected.

What do I actually need to set up to go live? Two things: your Welcome message template (the message a creator receives when approved) and your email branding (logo, colors, optionally a custom From address).

Can I message a single creator? Yes. From Messages → Create → Inbox, you can add creators individually by username, or send to a program, a program tier, or a saved segment. The same flow handles everything from one-off DMs to program-wide broadcasts.

Do creators receive an email too, or just the in-app inbox message? Both, if you want. Hub messages always land in the creator's in-app Hub inbox; when composing, you can also toggle email delivery so the message goes to both places. That way you reach creators wherever they're most active.

What's the difference between a platform notification and a brand message? - Platform notifications are sent automatically by LoudCrowd when something happens — application received, application declined, reward earned, monthly gift available, milestone reached. You don't write or configure them; the copy is system-managed, and creators see them from "Loudcrowd Creators." - Brand messages are what you compose and send — broadcasts and your Welcome / Invite templates. They go out under your program name with your email branding.

See the two sections below for the full breakdown.

Can I personalize messages? Yes — drop in variables like {{first_name}}, {{programName}}, {{affiliateCode}}, {{shoppableAmbassadorLink}}, or {{viewDashboard}} in subject and body. The token picker is built into the editor.

Do I have to set up a Welcome template? Strongly recommended. If you don't, no welcome message is sent when a creator is approved into the program. (Approved creators with a welcome gift still get the gift; they just won't get a welcome message until you set the template up.)

Will turning off my ESP flows break anything? For creator-facing flows, no — LoudCrowd now covers them in-platform. Keep all of your customer-facing flows running.

LoudCrowd's Creator Hub now has a native inbox — a direct, in-platform line to your creators. The previous flow (set up ESP integration → design email templates → maintain flows in your ESP) was duplicative and brittle. The new model:

The mental model is simple: LoudCrowd handles automatic notifications. You handle Welcome and any messages you want to send. Once those are set, comms run on autopilot.

These are sent by LoudCrowd, automatically, when creator events happen. You don't configure them, and the copy is system-managed (you can't edit it). They're shown to creators as "Loudcrowd Creators." They land in the creator's Hub inbox and are also emailed.

Once Hub Messaging is enabled, these start sending on their own — no setup required.

These are messages you compose and send — they come from your program (your program name as the sender, with your email branding). There are two kinds:

What broadcasts are great for: - Program updates and announcements - Highlighting new products or product launches - Requesting content usage rights from individual creators - Campaign kick-offs and creative direction - Affiliate code or commission reminders

Example: Subject: Hot & Savory Meals Are Back 🔥 Body: Big news — our Hot & Savory meals are back in stock and ready to promote! Head to your storefront and add them to your featured products, then share with your followers. These sell fast, so don't wait!

The Welcome message is the one template every brand should set up. Once configured, it sends automatically the moment a creator is approved into a program — that's the "autopilot" piece.

Welcome gifts are added automatically. If the approved creator's tier includes a welcome gift, LoudCrowd appends a "Claim your welcome gift" link to the message — you don't need to add it yourself.

The same setup applies to the Invite to Program template, used when you invite creators you've discovered through LoudCrowd.

Email branding controls how the emails LoudCrowd sends on your behalf look — your logo, colors, and the From address recipients see. For full setup steps (uploading your logo, picking colors, adding a custom From address, configuring CNAME DNS records), see the dedicated guide:

Brand Settings for Emails Sent from LoudCrowd

In short: - Logo + colors: Messages → Email Branding tab. - Custom From address (optional): Sending Domains → Add Domain → add the CNAME DNS records LoudCrowd generates at your DNS provider.

Until you set a custom domain, your messages go out from [email protected]. These branding settings apply to messages you compose and to your Welcome / Invite template emails. They don't apply to in-app Hub inbox messages (which appear inside the hub) or to the automatic "Loudcrowd Creators" platform notifications.

You no longer need an ESP for creator communications — LoudCrowd handles all of them in-platform. Turn off any creator-facing flows in Klaviyo (or whatever ESP you use) so creators don't get the same message twice.

Common ESP creator flows you may have set up that LoudCrowd now covers:

Your non-creator ESP flows — customer marketing, abandoned cart, browse abandon, post-purchase, etc. — are unaffected. Keep those running.

If you're not sure which of your flows are creator-facing, your Client Strategist can help you audit them as part of the switch.