Skip to main content
Outcome: sequences that measurably improve every cycle — data-picked copy on every step, losers paused, winners promoted to templates.

​
Best interface

CLI for ops loops — reply api against the stats and lifecycle endpoints composes with jq and cron for continuous optimization. MCP interactively — inspect steps and variants, compare sequences, pause/start conversationally.

​
Steps

1

Create A/B variants on the steps that matter

Openers and first follow-ups move the numbers hardest. Add message variants via the Sequences API (see API Reference); inspect existing ones via MCP: reply_get_sequence_steps → reply_get_sequence_step_variants.
2

Let traffic split

Run the sequence; the platform distributes contacts across enabled variants automatically.
3

Read per-variant and per-sequence performance

MCP: reply_get_sequence_stats for one, reply_compare_sequence_performance for up to 25 side by side.
4

Pause the losers — no need to stop the sequence

The list endpoint accepts only lastWeek or lastMonth. Disable underperforming variants mid-flight via the API; pause whole sequences as above or via MCP.
5

Promote the winners

Save winning messages as email templates so every future sequence starts from proven copy — Templates via the API.
6

Verify the lift

Confirm the aggregate effect over time with POST /v3/reporting/emails/overview, or the analyze-performance skill.

​
Availability notes

  • Everything here is available today. Per-contact status changes inside a sequence (pause one person, mark finished) are richest via MCP: reply_change_status_in_sequence.