Why email earns its bar

Email opens at 22%. Most of those opens go nowhere.

Email open rates are well-known. The number nobody talks about: of those opens, what share become a real reply, then a multi-touch thread, then a qualified handoff. Most teams send email blasts and get a single-digit reply rate that’s a fraction of the open rate.

The gap is the conversation that runs after the open — the threading, the reply context, the follow-up that adapts to what the lead actually wrote. MagicBlocks runs email as a real conversation. Replies thread. Subjects don’t repeat. Cadence backs off when the lead engages. Channel switches to SMS or chat when email goes quiet. The lead’s actual words shape the next touch.

Typical email blast
MagicBlocks email
Open rate
20–25%
20–25% — same channel reality
Single-touch reply rate
1–3%
8–14% on warm pipeline
Threading on replies
Often broken (bad Message-ID handling)
RFC 5322 compliant — replies thread cleanly
Subject-line variation per touch
Rare
Different per cadence stage
Channel-switch on silence
Doesn’t happen
SMS or chat after configurable threshold

What real email sounds like

A 14-day refi-quote cadence — thread that closes.

Same lead. Three messages across 14 days. Watch how the cadence threads, the subject stays consistent, the case study lands at Day 7 — and the lead replies on Day 14 with "let’s do Thursday."

MagicBlocks · on behalf of Apex Refi to [email protected]
Day 0 · 9:48 AM

Subject: Saw you searched 30-yr fixed refi rates — quick read

Hi Andrew,

Noticed you searched "30-year fixed refi rates Texas" yesterday and spent a few minutes on our rate quote page — figured I'd save you the comparison legwork and send a couple of concrete numbers.

30-yr fixed for strong-credit profiles is sitting around 6.75–7.0% this week. For a $420K refi at mid-700s credit your exact rate depends on LTV, DTI, and a full credit pull. Sarah Chen, one of our senior LOs, can walk through the precise numbers in 15 minutes.

Two slots open this week: Thursday 10:30 AM or Friday 2:00 PM. Either work?

— Apex Refi

MagicBlocks · on behalf of Apex Refi to [email protected]
Day 7 · 4:30 PM

Subject: Re: Quick follow-up on your refi quote inquiry

Hi Andrew,

Quick check-in. Sarah's calendar still has Thursday 10:30 if it works on your end. If timing isn't right, totally fine — happy to wait on rate movement and circle back next month.

Attached: a 2-min case study from a borrower with a similar profile (30-yr refi, mid-700s, ~$400K). They closed at 6.625% with us last month — sharing in case the comparison is helpful.

— Apex Refi

Andrew K. <[email protected]>
Day 14 · 8:12 AM

Subject: Re: Quick follow-up on your refi quote inquiry

Sorry for the slow reply — busy quarter. Yes, let's do Thursday 10:30. Sarah has my number from the original inquiry.

Illustrative email thread. Rates and availability vary by borrower profile, credit, and market conditions.

Email deliverability + compliance

Email lives or dies on deliverability.

Sending volume runs into spam filters before it runs into regulators. Frameworks like CAN-SPAM (US) and GDPR (EU) apply — physical address, opt-out, accurate header, lawful basis. DMARC, SPF, DKIM authentication. List hygiene. Engagement-based throttling.

You own the policy; we give you tools to apply it. MagicBlocks brings the deliverability-first plumbing — warm-up, sender reputation, throttling on engagement, automatic suppression on bounce or complaint — and runs your configured consent + opt-out checks on every send. If a check fails, the message doesn’t go.

  • SOC 2 Type II
  • ISO 27001
  • Built for CAN-SPAM workflows
  • GDPR-aligned
  • RFC 8058 one-click unsubscribe
  • BIMI-ready
  • Full audit logs

Infrastructure · sending

Send through your provider. Or ours.

SendGrid, Postmark, AWS SES, Mailgun — bring your own. Or run on our managed sending infrastructure during onboarding. Either way, MagicBlocks runs the conversation on top. Your domain, your sender reputation, your audit trail.

Use cases

What teams actually run on email.

Three primary patterns across mortgage, fintech, B2B SaaS, and enterprise sales operators with mature CRM data.

01 · Cold pipeline reactivation

Old leads that went silent — recovered with subject-line testing.

Multi-touch reactivation across 14–30 days. Each touch composed against the lead’s original stated priority, not a calendar drip. Subject lines tested per cadence, different at touch #3 vs touch #1.

02 · Abandoned-application recovery

Half-completed applications, pulled back into the flow.

A lead drops off at the income-verification step. MagicBlocks emails 15 minutes later with a "want to pick up where you left off?" message and the resume link. Recovery rates vary by application stage and product — see our customer stories for production numbers.

03 · Post-meeting follow-up

Handoff prep, decision support, CRM-logged.

After a discovery call, the rep gets a draft follow-up email pre-loaded with the right case study, the sized loan options, and the next-step ask. Send as-is or edit. Either way, the activity logs to your CRM.

FAQ · Email Agent

Questions about MagicBlocks on email.

Does it thread properly?

Yes. Replies thread by Message-ID, In-Reply-To, and References headers — full RFC 5322 compliance. Subject lines stay consistent across the thread, the visitor’s mail client renders the conversation correctly.

Subject-line testing?

Yes. Different subjects per touch in long sequences. Tested for open rate at the cadence level, not message level — we look at full-cadence engagement, not single-message metrics.

How do you handle deliverability?

DMARC, SPF, DKIM authentication on every send. Domain warm-up during onboarding. Engagement-based throttling — sending volume scales with reply rate, not against it. Automatic suppression on bounce, complaint, or hard fail.

Can it reply when the lead emails first?

Yes. Inbound email handoff to your reps with full context, or AI reply for FAQ-grade questions — your choice, configurable by inbound type.

BIMI?

BIMI-ready when your domain is set up (verified mark certificate + DMARC enforcement at "p=quarantine" or "p=reject"). The brand logo renders in supporting clients (Gmail, Yahoo, others).

How does it know when to stop?

Same signals as other channels. Stops on opt-out (one-click unsubscribe per CAN-SPAM and RFC 8058), slows on non-engagement, exits the cadence on "stop," "remove me," or "not interested" replies.

Long-form vs short emails?

Both. Tone calibrated to your brand during onboarding. Cold-pipeline emails tend to run shorter (3–5 sentences); post-meeting follow-up tends longer (case studies, attachments, decision support).

Attachments?

Yes. Send case studies, decks, fact sheets, contracts. Track opens, clicks, downloads. Attachments live in your storage (Google Drive, Dropbox, S3) — we don’t hold them for you.

Sending infrastructure — can we use our own?

Yes. SendGrid, Postmark, AWS SES, Mailgun — bring your own. Or run on our managed sending infrastructure during onboarding. Either way, MagicBlocks runs the conversation on top.

Channel-switching to SMS or chat?

Yes. When email goes quiet for the lead’s configured threshold (default 7 days non-engagement), we channel-switch to SMS if you have phone consent, or back to web chat when they return to your site. One memory, multi-channel.

See MagicBlocks on email in action.

See the demo. No sales pitch. Then decide.