Playbook · Mail

Migrate your email list to Loopi — without burning your sending domain.

Export your subscribers from Mailchimp, ConvertKit, or a CSV. Import them into Loopi in minutes. Then let the ramp do the work: your most-engaged subscribers get the first email, your domain builds a clean reputation, and your full list gets the welcome by day seven — all scheduled by your AI agent before a single send fires.

What it does for you

Moving your list to a new email platform is the step most business owners skip — or do badly and end up in spam. This play does the whole thing: import, tag, ramp, send. Your agent handles the tedious parts. By the end you'll have:

• Your entire subscriber list inside Loopi — deduped, unsubscribes honored, and your most-engaged subscribers tagged separately so the ramp can start with them.
• A sending domain with a clean reputation — because the ramp starts with your openers and clickers on day one, giving inbox providers the engagement signal they need before the full list sees any email.
• A seven-day warm-up scheduled and approved before it fires — you see the dates and subscriber counts, say yes, and the agent handles the rest.
• No spam folder surprises — the most common reason a migration goes wrong is sending your whole list from a cold domain on day one. This play prevents that.

Four steps, start to finish

Nothing is hidden here. The first two steps are one-time setup. Steps three and four your agent runs from a single prompt.

1. Export your CSV

Pull a subscriber export from your current tool — Mailchimp, ConvertKit, ActiveCampaign, or whatever you use. The only columns the agent needs areemail, subscribed (true/false), and tags (so it can identify your engaged subscribers). Everything else can stay in the export; the agent ignores what it doesn't need. Save the file and keep it open — you'll paste it into the prompt in step four.

2. Connect Loopi to your agent

First, a Loopi account — 60 seconds (email + password at loopi.social). Then wire Loopi to your agent. Loopi is an MCP server — one line in Claude Code does it. Claude Desktop, Cursor, Codex, and Gemini take the same https://api.loopi.social/mcp URL in their connector settings. Authorizing is a one-time browser login.

# Claude Code — add Loopi in one line
claude mcp add --transport http loopi https://api.loopi.social/mcp

# then tell your agent:
> connect to loopi mcp        # opens a browser to authorize, once

3. Set up your sending domain first

A warm-up ramp only works if the emails come from your own domain, not a shared Loopi address. Set up your sending domain — it takes about ten minutes. The agent calls account.getOrCreateSendingDomain to confirm the domain is ready before it starts importing. If you skip this step, your emails send from mail.loopi.social and the reputation you build belongs to Loopi's shared domain, not yours — which defeats the purpose of a ramp.

4. Run one prompt

Paste the prompt below into your agent with your CSV appended at the bottom. The agent creates your list, imports subscribers in batches of 100, tags your engaged subscribers, writes the welcome email, and schedules the two-broadcast ramp. It tells you the plan — dates, counts, broadcast IDs — before anything sends.

Connect to Loopi MCP. I'm migrating my email list.

Step 1 — Create a list.
Call mail.createList with name "main list". If a list already exists on this
profile, use that one.

Step 2 — Import subscribers from my CSV.
My CSV has columns: email, first_name, last_name, subscribed, tags.
Parse it and split into two groups:
  - Engaged: rows where subscribed=true AND tags contains "opener" or "clicker"
  - Everyone else: rows where subscribed=true AND NOT in the engaged group
Skip rows where subscribed=false — those are unsubscribes from my old tool.

Import the engaged group first using mail.bulkListSubscribe with tag="engaged"
(max 100 emails per call — loop as many times as needed).
Then import the everyone-else group using mail.bulkListSubscribe with no tag
(same 100-per-call loop).

Step 3 — Warm-up ramp.
Create content for a short "welcome to the new home" email: personal tone,
first-person, one sentence about why I moved, one CTA link back to my site.
Call mail.createContent with that body.

Then schedule two broadcasts using mail.createBroadcast:
  - Day 1 (tomorrow at 10am): send only to tag="engaged" subscribers
  - Day 7 (seven days from now at 10am): send to all subscribers (no targetTag)

Tell me the scheduled dates, subscriber counts in each group, how many were
skipped as unsubscribed, and the broadcast IDs before you confirm anything.

My CSV:
[paste CSV here]

Connect Loopi to your AI agent and run this migration tonight →

The warm-up ramp

Two broadcasts. Day one goes only to your engaged subscribers — the people most likely to open and click. That engagement signal tells inbox providers your domain is trustworthy. By day seven, the full list gets the welcome email to a domain with a clean reputation behind it.

If your CSV doesn't have engagement tags, import everyone in one batch and skip the ramp — or set day one to a hand-picked list of 20 people you know will open it. The principle is the same: engaged subscribers first.

What the agent sees

What Loopi handles for you

• Deduplication on import. Loopi dedupes by email address. Sending the same address twice in different batches is safe — it lands in the alreadySubscribed bucket, not as a duplicate.
• Unsubscribe suppression. The agent skips rows where subscribed=false before calling Loopi. Addresses that previously bounced or complained are blocked at the Loopi layer and go into the suppressed bucket — they're never resurrected even if they appear in a future import.
• Tag-based ramp targeting. The agent imports your engaged subscribers with tag="engaged" and passes targetTag="engaged" to the day-one broadcast. Day seven sends to all subscribers (no tag). You don't manage segments manually.
• Compliance on every send. Every broadcast Loopi sends carries a compliant unsubscribe link, List-Unsubscribe headers, and a CAN-SPAM-required footer. You write the welcome; Loopi wires the rest.
• Schedule confirmation before send. The agent reports broadcast IDs, scheduled dates, and subscriber counts. Nothing fires until you say so.

What the result looks like

After running the prompt on a 1,200-subscriber Mailchimp export, the agent reported back:

• 1,147 subscribers imported — 53 skipped (48 unsubscribed, 5 invalid addresses)
• 214 tagged "engaged" — subscribers carrying the "opener" or "clicker" tag in the export
• Day 1 broadcast: scheduled for tomorrow at 10 am, targeting the "engaged" tag only — 214 recipients
• Day 7 broadcast: scheduled for seven days from now at 10 am, full list — 1,147 recipients

The agent wrote a two-paragraph welcome email in the owner's voice, linked back to the site, and confirmed both broadcast IDs. The owner approved in one reply. Total time from pasting the prompt to approved plan: under three minutes.