SMS vs the phone
The phone stopped getting answered. SMS still gets read.
Cold calls used to work because people picked up. They don’t anymore. Unknown numbers ring out, and the new wave of AI call-screening on phones sends them to voicemail before they ever ring. A text is different — it lands, it’s seen, and it waits for a reply on the buyer’s schedule.
-
Unknown calls don’t connect
Most people let calls from numbers they don’t recognise ring out. Phones now screen unknown callers straight to voicemail — your call doesn’t even ring.
-
A text always lands
SMS opens at 98%. The message sits in the thread until the buyer is ready to read it — no missed window, no endless phone tag.
-
It moves at the buyer’s pace
A call demands attention right now. A text lets the buyer reply when it suits them — which is usually when they’re actually ready to engage.
Why SMS earns its bar
SMS open rates are 98%. The hard part is what happens after.
SMS opens at 98% (vs ~22% for email). That’s the famous number. The number nobody quotes is what share of those opens turn into a real conversation, then a qualified handoff, then a booked deal.
Most teams send SMS and get a one-touch reply rate that’s nowhere near the open rate. The gap isn’t the channel — it’s the conversation that runs after the open. MagicBlocks is built for that gap. Two-way conversation, threads that go multiple messages deep, branching by what the lead says, follow-up that knows when the lead’s gone quiet. SMS as a real conversation, not a notification channel.
What real SMS sounds like
Watch MagicBlocks run an SMS thread.
Same lead. Real SMS thread. Watch how MagicBlocks replies instantly, qualifies on real fit, and books the next step — with full memory across days of silence and re-engagement.
Illustrative SMS conversation. Industry-specific terms vary.
SMS compliance tooling
SMS lives or dies on consent discipline.
SMS is heavily regulated in many markets. Consent has to be captured, stored, and respected before every send. Opt-outs (STOP, UNSUBSCRIBE, CANCEL) take effect instantly and permanently. Quiet hours have to be enforced. Jurisdiction-specific rules apply on top of frameworks like TCPA.
You own the policy; we give you tools to apply it. Every outbound SMS is checked against your consent policy, the lead’s opt-out state, the time of day, and the jurisdiction rules you’ve configured before it sends. If a check fails, the message doesn’t go.
- SOC 2 Type II
- ISO 27001
- Built for TCPA-aligned workflows
- STOP honoured instantly
- Quiet hours respected
- Jurisdiction rules configurable
- Full audit logs
Infrastructure · running on Twilio
Carrier-grade rails. Conversation-grade AI on top.
SMS runs on Twilio — the same carrier-grade infrastructure behind most of the SMS sent in the United States. You bring your own Twilio account, so you keep your numbers, your A2P 10DLC registration, and your audit trail — that layer stays yours. MagicBlocks runs the conversation on top.
Use cases
What teams actually run on SMS.
Three primary patterns across mortgage, finance, auto, home services, and tourism operators in production today.
Form submit → real SMS reply in seconds.
A form submit triggers an instant SMS reply. The most common setup. Real reply in under 5 seconds, every time.
5–8 touches over 14–30 days, channel-switching.
The follow-up most teams don’t actually run manually. SMS first, channel-switch to email when SMS goes quiet, back to SMS when the lead replies.
Triggered by real signals — not calendar drips.
Rate move, season, renewal window, inventory change. Personal, consent-validated, time-zone-aware. Only sends when the signal is genuinely relevant.
FAQ · SMS Agent
Questions about MagicBlocks on SMS.
Is this just a chatbot for SMS?
No. MagicBlocks runs specialised playbooks for every stage of the conversation, with real two-way exchange across days. Memory persists. Branching follows what the lead says. Cadence adapts to engagement.
Can we use our existing SMS provider?
Yes if you’re on Twilio (BYO Twilio is supported). Other providers depend on the work — talk to us about your specific setup.
TCPA — what's our exposure?
Consent and opt-out checks happen before each send. Your TCPA exposure depends on how you capture consent upstream of MagicBlocks. MagicBlocks respects whatever consent state you tell it to. Your own counsel should confirm your specific consent capture and retention practices.
A2P 10DLC — do we need to register?
Yes — every business sending SMS to US consumers needs A2P 10DLC registration. Since you bring your own Twilio account, your existing registration applies; if you’re registering fresh, we’ll walk your team through it during onboarding.
Can it run WhatsApp / iMessage / RCS?
WhatsApp Business is covered as a separate channel — see /channels/dms. iMessage and RCS aren’t currently supported as standalone channels — they fall back to SMS.
International SMS?
Yes — Twilio supports SMS in 180+ countries. Country-specific rules set up during onboarding.
How fast is "under 5 seconds"?
4.2 seconds in production across mortgage and tourism customers. Driven by Twilio’s delivery time plus MagicBlocks’s reply time.
What does SMS cost on top of MagicBlocks pricing?
Carrier costs (Twilio’s per-message rates) pass through at retail. We don’t mark up. Per-message rates vary by country and route — see /pricing for a current quote scoped to your volume and channels.
Can a lead start on web chat and continue on SMS?
Yes. A lead who starts on web chat and switches to SMS continues the same conversation with full memory. We treat the lead as the unit, not the channel.