Skip to content
WeZend
Let the team draft — require a second pair of eyes before it sends.

Campaign approval

Members can build and submit campaigns, but a send goes to pending approval for an owner or admin to release. Governance for teams and agencies, built into roles — no accidental sends to the whole list.

The bigger the list, the scarier the send button. Campaign approval turns a solo action into a controlled one: team members can create and submit campaigns, but they can't self-approve their own sends. A submitted campaign moves to pending approval, where an owner or admin reviews and releases it. It's enforced by the role system's approve capability, so it's real governance — not a checklist people can skip.

That's exactly what teams and agencies running WeZend for clients need: junior staff and freelancers can do the work, while sign-off stays with whoever's accountable for the brand. Fewer 2 a.m. "we sent the wrong thing to everyone" moments, without slowing the team down.

Benefits

Why it matters

No accidental sends

A send needs a reviewer's release, so a mistake is caught before it reaches the audience, not after.

Delegate the work, keep the sign-off

Members and freelancers build; owners and admins approve. Accountability stays where it belongs.

Capabilities

What you can do

Role-enforced

The `approve` capability is part of the RBAC model — members can submit, only owners/admins release.

Pending-approval queue

Submitted campaigns sit in a clear pending state until a reviewer approves or rejects.

Frequently asked questions

Who can approve a campaign?

Owners and admins — anyone with the `approve` capability. Members can create and submit but not release their own sends.

One platform. Every customer interaction.

Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.

No credit card required · EU data residency · 99.99% uptime SLA