platform / review & qa
Review is the product, not a screenshot in a thread.
Every MAP claims approvals. What they mean is: export a preview, paste it in an email, wait. In veloquent every workflow carries its own review status — so the platform knows whether a send is drafted, waiting, approved, or sent back — they all queue in one place, and the decision can happen without leaving Slack.
Ready for review is a state, not a vibe
Any workflow — batch send or evergreen journey — can be marked ready for review. Status rolls up to the campaign, so a campaign home shows what's waiting at a glance. Reviewers work one unified queue; approving a batch send sends it, approving an evergreen unlocks enrollment. A rejection is relabeled what it actually is: changes requested.
veloquent app 2:47 PM
Fall Product Launch is ready for review
Basic Batch · Enterprise Trial Accounts · 5 recipients
Decisions land back in veloquent with a full audit trail.
The same decision, in the thread where it gets discussed.
QA runs before a reviewer ever looks
Checks run ahead of the review gate, so reviewers judge substance, not typos: links resolve, UTM parameters are present and correct, required fields are filled. And the roadmap goes past the technical — configurable quality checks (“does this email match our brand voice and guidelines?”) that you define in the app, judged by AI, surfaced in the review.
Approve where you already are
The review notification lands in Slack with the same two buttons the queue has: approve & send, or request changes. Decisions carry an audit trail either way. Nothing about the approval loosens because it happened in a chat window — approving in Slack and approving in the app are the same action, recorded the same way.
Questions operators ask
- Can marketing emails be approved from Slack?
- Yes. When a workflow is marked ready for review, veloquent posts a Slack notification with Approve & send and Request changes buttons. Deciding there is the same action as deciding in the app — same status change, same audit trail, no weaker for having happened in a chat window.
- What QA checks does veloquent run?
- Technical checks run before anything reaches review — links resolve, UTM parameters are correct, required content is present. Configurable quality checks (brand voice, style guidelines) that you define in-app are on the roadmap.
- Can something send without approval?
- No. Batch sends go out only when approved; evergreen journeys can only enroll after approval. The gate applies to everything, including work the AI assistant builds.
Follow the build.
One email when something ships. Or better: bring us the thing your MAP won't fix.