Why chat earns its bar
The visitor on your site is the most expensive lead you have.
You spent real money to get that visit. The buyer lands, looks around, has a question — and the only way to ask is a contact form that kicks them out of context. They abandon.
The chat widget exists to fill that gap. Most chat widgets don’t. They either stay silent until a human picks up, or they deflect with FAQ-bot patterns that frustrate buyers who want a real answer. MagicBlocks runs the chat widget like a senior rep would — instantly, with context, with real qualification, with the right handoff at the right moment.
What real chat sounds like
The first 90 seconds of an inbound rate-quote — on chat.
Same lead. Same form-page question. Watch MagicBlocks reply, qualify, and book the rate review — without making a single carrier-specific commitment the LO has to walk back.
Illustrative web-chat conversation. Rates and availability vary by borrower profile, credit, and market conditions. Lending decisions are made by licensed loan officers.
Privacy + consent
The chat widget is your website. Treat it that way.
Web chat sits below the regulatory load of SMS — but it carries its own. PII collection lives where the visitor is. GDPR for EU visitors. Session memory tied to anonymous IDs until the visitor identifies themselves.
MagicBlocks runs consent flows per your privacy policy, can redact PII from logs once you turn that setting on, and persists memory only inside the visitor’s consent window. Your chat policy, enforced before every message.
- SOC 2 Type II
- ISO 27001
- GDPR-aligned
- EU data residency
- CCPA-aware
- Visitor-level retention controls
- Full audit logs
Infrastructure · the embed
Two lines of code. Yours from there.
A <script> tag and a <div data-magicblocks>
placeholder. That’s the install. The widget is branded with your colors, your
tone, and your knowledge base, and loads in the background so it doesn’t hold up
your page.
Use cases
What teams actually run on chat.
Three primary patterns across mortgage, insurance, solar, fintech, and home- services operators with paid web traffic.
Visitors who would have abandoned a form, qualify in chat instead.
A buyer on your pricing page has a question. The form-only path gets them to a thank-you page and a follow-up email three days later. The chat path qualifies them in 90 seconds and books the call.
FAQ-grade questions answered. Real questions escalated.
Most chat traffic is FAQ-level ("what time do you open," "do you serve my state"). MagicBlocks handles those completely and only escalates the conversations with real buyer intent — your team stops drowning in same-question traffic.
A buyer who came back Thursday picks up where they left off Monday.
Memory is tied to the visitor, not the page or session. Same conversation across pages, across visits, across devices when they identify. No "let me get you caught up" awkwardness.
FAQ · Chat Widget
Questions about MagicBlocks on web chat.
Is this a chatbot?
No. MagicBlocks runs specialised playbooks for every stage of the conversation — opening, qualifying, handling objections, handoff. Real two-way exchange that knows where the conversation is and what comes next. Chatbots branch on keywords. MagicBlocks reads the conversation.
Will it slow my site?
No. The widget loads in the background after your page is up, so it doesn’t hold up anything your visitor sees.
Can I brand it?
Yes. Your colors, your launcher copy, your tone, your knowledge base. Visitors see your brand, not ours.
What does the visitor see?
A subtle launcher in the corner of your site. Tap to open. It can run as a contained card, a full sidebar, or full-screen on mobile — whatever fits your site. The visitor types their question, MagicBlocks replies in seconds.
Memory across visits?
Yes. Tied to anonymous visitor IDs (cookie + localStorage) until the visitor identifies themselves with email or phone, then promoted to a contact-level memory. A buyer who asks a question Monday and comes back Thursday picks up where they left off.
GDPR for EU visitors?
The widget gives you the tooling to run your own GDPR-aligned process. It can detect EU visitors and run a consent flow before persisting identifiable data, and consent, retention windows, and SAR (subject access request) handling are all configurable. You decide how it’s set up — you stay the data controller.
Multi-language?
Yes. Set the supported languages during onboarding. The widget detects the visitor’s browser locale and opens in the right language; the visitor can switch if they prefer.
Lead handoff to our team?
Pushes to your CRM (HubSpot, GoHighLevel, others via Zapier) with the full transcript, the qualification signals that matched, and a suggested next move attached. Your reps open the call already briefed.
Can a visitor switch from chat to SMS?
Yes. Memory is tied to the lead, not the channel. A visitor who starts on chat and gives their phone number can continue on SMS — same conversation, same context, no restart.