MCP

Writing the email

What goes in the subject and body. The mechanical sequence — create, add steps, enrol, start — is sending-a-campaign; the exact names you may personalize with are personalization-variables. Everything below is what Manyreach itself teaches about cold email. For the craft beyond these rules — the named, referenced approaches to subject lines, body structure, calls to action, and length — open the playbook's writing module.

Format

  • body is always HTML — wrap paragraphs in <p>, whatever textOnlyEmails says. That flag chooses the MIME type at send time, not the format you supply.
  • textOnlyEmails: true strips HTML formatting and embedded images at send. It is a deliverability setting: fewer HTML elements, fewer spam-filter triggers. Three consequences before you turn it on:
    • Open tracking stops working, even with trackOpens: true — opens are counted by a hidden image, and a text-only email has none.
    • An HTML signature loses its images and styling, so keep the signature plain.
    • With trackClicks: true, links are rewritten into long redirect URLs that read less personally.
  • Plain text is the platform's own recommendation for staying out of spam filters.

Copy

  • Personalize. Identical mail sent to hundreds of people is exactly what filters look for; use variables for the name, the company, or something specific you noticed about the prospect.
  • Drop the sales register. Overly promotional or purchase-heavy words and excessive capitals hurt you; write for clarity instead.
  • Write for a reply: a subject line that invites a genuine response, a clear question at the end, and a call to action that needs no link.
  • When a campaign underperforms, ineffective messaging is a more common cause than technical deliverability.
  • Send yourself a test before launching, to see how the message actually renders.
  • Two optional mechanisms: trackOpens (invisible pixel) and trackClicks (links rewritten through a redirect). Both can trigger spam filters and make a message look like marketing rather than personal mail.
  • Turn them off when deliverability outranks analytics: high-value prospects, strictly filtered domains, or a new sending domain or mailbox (why).
  • Avoid links pointing anywhere irrelevant or suspicious.
  • Reply rate is the measure that survives having no tracking: replies ÷ delivered × 100. 5–10 % is typical and 15 %+ is a strong campaign. The counters are on the campaign itself — replyCount, sentCount, bounceCount (schemas/campaign).
  • If click tracking must stay on, a custom tracking domain (a CNAME configured in the web app) keeps the rewritten links on your own domain.

Unsubscribe

  • {{UNSUBSCRIBE_LINK}} inserts a ready-made link whose text is "Unsubscribe"; {{UNSUBSCRIBE_URL}} gives you the bare URL so you can write your own wording around it.
  • sendUnsubscribeListHeader adds the List-Unsubscribe header, which email clients surface as their own unsubscribe control.
  • A prospect who unsubscribes — by the link or by that header — moves to sendingStatus: Unsub and stops receiving the campaign.

Signature

  • A signature belongs to the sender, not the campaign — it is the sender's signature field (sender/patch_by_id, HTML), documented as appended to the bottom of outgoing messages. {{SENDER_SIGNATURE}} also exists as a variable, for placing it somewhere other than the bottom. Use one or the other: writing the variable into copy whose signature is already appended would print it twice.
  • Set the sender's firstName, lastName and fromName on the same operation, so the sender variables have something to fill in.

Images and files

  • Images must be hosted externally and embedded as HTML in the body — there is no upload path.
  • Keep images under 600 px wide.
  • For a per-prospect image, put its URL in a custom field and reference the variable in the tag: <img src="{{CUSTOM_1}}" width="400" alt="">.
  • There are no attachments. Upload the file to a drive, make the link public, and insert it as a link — the major providers treat a drive link much like an attachment. Video works the same way.

Deliverability the platform expects

  • SPF, DKIM and DMARC on the sending domain are prerequisites, not options (tips).
  • Volume: no more than 30–50 emails a day. On a new account follow the 40/40/40 rule — at most 40 a day, at least 40 minutes apart, for the first 40 days.
  • Keep the sender delay (delayMinMinutes, in minutes) at 10 minutes or more; going below that costs domain reputation. Delays are applied with random jitter so sends do not look mechanical, and more volume is bought with more senders rather than shorter delays.
  • The sender's own daily limit is the ceiling. A campaign dailyLimit above it changes nothing, and senders shared between campaigns share that limit (sender/get).
  • Vary the copy per recipient with spintax — {|Hi|Hello|Hey|} — so a campaign does not send many byte-identical messages. Subject and body both support it, nesting included; see spintax, which also covers the trap that makes literal { / } disappear.
  • Validate addresses before the first send to a list — validating-emails.
  • A campaign auto-pauses when its bounce rate passes 10 %. Recovery means returning it to Draft in the web app (no operation here does that), cleaning the list and fixing the cause — and it is allowed once; a second breach blocks the campaign permanently. Add bounced addresses to the blacklist so later campaigns never retry them.