Niches · Lifecycle marketing & customer engagement

Send or trigger a message with a person's approval first

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
10companies, fit with a limit
13companies carry the tag
17share of the category's work
5first-hand accounts

What counts as done

A test reaches the named inbox and is confirmed delivered; the real send waits until an approval or a separately scoped call, and no message goes to an opted-out profile.

How agents ask for it: send this campaign once I've approved it, send me a test first, trigger the onboarding message for this user

Does the job, with a limit 10

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Braze B
Braze, Inc.
Launch happens only in the dashboard, which holds the real send for a person, but neither the MCP list nor REST has a test send that confirms delivery to a named inbox. source
CleverTap D
WizRocket Inc.
draft=true and estimate_only hold a campaign for review and unsubscribed users are skipped by default, but no test-send call was found and passcodes carry no scopes, so the same credential can send. source
Customer.io A
Peaberry Software, Inc. d/b/a Customer.io
Sending needs write:live, granted separately from write at consent, and Design Studio test_send goes to a real inbox, but its 200 reads 'Test accepted for delivery', not delivered. source
Dreamlit C
Notika AI (d/b/a Dreamlit AI)
send_workflow_test returns confirmation_required before sending and publishing needs prepare_publish then confirm_publish under a separate workflows:publish scope, but test delivery is not confirmed back and unsubscribe can be switched off per workflow. source
Iterable C
Iterable, Inc.
templates/email/proof sends a proof to a named user and MCP sends sit behind ITERABLE_ENABLE_SENDS, but there is no approval step, proof returns only a generic success, global suppression lists must be passed by hand, and tools carry no annotations (acc-01, acc-02). source
Mailchimp Marketing API C
The Rocket Science Group LLC d/b/a Mailchimp
actions/test sends to named test_emails before actions/send, but it answers 204 with an empty body, not a delivery confirmation, and the same full-access key can send; no approval step exists. source
MoEngage B
MoEngage, Inc.
The MCP cannot publish, so a person launches from the dashboard, and test_campaign_by_draft_id sends a test, but the docs don't say the test reports delivery, and only Push and Email can be tested. source
Nitrosend BB
Nitrosend Pty Ltd
nitro_send_test_message sends one real test and never approves, and audience delivery needs a separate nitro_control_delivery call, but the test's success only confirms the provider accepted it, and one OAuth scope covers both. source
Omnisend B
Omnisend, UAB
test-email renders the draft to up to 5 recipients and the consent screen has a read-only preset, but the test answers 'queued for delivery', not delivered, and send runs through the same omnisend_update tool as edits with no hold. source
Sequenzy B
Nic Tech Solutions, LLC
Presets enforced on every request keep drafting keys from sending, and the test endpoint now returns a durable send ID to check delivery, but acc-05 found test sends answering success without queueing, and a company key with api_keys:manage can widen itself. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
ActiveCampaign E
ActiveCampaign, LLC
Not read: hosts paused under the terms question. The 8 October notes say one API key per user with no scopes, and schedule failures return 200 with succeeded=0.

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
Klaviyo API + MCP BB
Klaviyo, Inc.
No test-send operation is in the spec or the MCP tool list, and send_campaign or campaign-send-jobs sends under the same campaigns:write scope as drafting, with no hold; acc-19 built its own approval gate. source

What stops agents finishing

  • no approval step before the send call (Klaviyo, Omnisend, Mailchimp)
  • one key with full account access including sends
  • test endpoint answers success without sending
  • terms that bar automated agents without written permission

Around it

Before: lifecycle-marketing.campaign-draft. After: lifecycle-marketing.campaign-report, human-in-the-loop.approval.

Where this comes from

Weight 17 of 100 in Lifecycle marketing & customer engagement: 5 of 30 counted mentions (acc-01, 02, 05, 16, 19); acc-28 is speculation and not counted

The same as data: /api/v1/use-cases/lifecycle-marketing.send-with-approval.json, or the MCP tool get_use_case with id lifecycle-marketing.send-with-approval. Other jobs in this category: /api/v1/niches?category=lifecycle-marketing.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.