See what’s new in MagicBlocks and the improvements we’ve made to make it more powerful, flexible, and reliable. 🚀

🚀 New Features

Agent Follow-Up — Configurable follow-ups with Block switching and controlled Channel routing

Previously, when a conversation went quiet, teams had to rely on manual check-ins or custom workarounds to restart the thread—making it easy for important leads and support requests to slip through. MagicBlocks now supports automatic follow-ups based on configurable timing rules, using the last user message to detect inactivity (and resetting the timer when the user replies). You can route the follow-up back into the same channel/thread, switch the conversation to a different Journey Block, and (when enabled) switch channels in a controlled way—including switching within the same channel type (e.g., SMS → SMS, Chat → Chat) or switching to SMS.

This helps teams reduce dropped conversations while keeping follow-up routing consistent and compliant.

• Follow-ups trigger from the last user message (user messages only) and reset on new user replies
• Deliver follow-ups into the same channel or into a configured destination (escalation)
• Optionally switch the next Journey Block, and enable Switch Channel only when you need it

Templates — Share templates across workspaces

Previously, templates were tied to a single workspace, making it hard to reuse proven setups across environments or accounts. MagicBlocks now supports sharing templates across workspaces so teams can standardize agent configurations, collaborate more easily, and roll out updates faster—especially when moving from staging to production.

• Share a template to one or multiple workspaces you can edit
• Set the Agent name for the new workspace during sharing
• Creates one Agent per selected workspace immediately

Relcu — Callable Hours Enforcement (with automatic queuing)

Previously, outbound SMS could be sent immediately—even when it should have waited for your Relcu callable-hours window—creating avoidable compliance risk and inconsistent customer experience. MagicBlocks now checks callable hours before sending outbound SMS; if it’s outside the allowed window, the message is automatically queued and sent at the next available start time. This helps teams stay compliant by default while still ensuring important outbound messages go out as soon as they’re allowed.

• Outbound messages respect Callable Hours automatically
• Messages queued outside the window are retried when callable hours start
• Replies to inbound/active conversations can still be delivered even outside callable hours when appropriate

Relcu — Human “Barge” Automatically Pauses the AI on Outbound SMS

Previously, a human could start texting a lead in Relcu while the AI agent remained active—risking duplicated replies, mixed messaging, and a confusing handoff experience. With Human Barge, MagicBlocks now automatically disables the agent for that conversation when a Relcu user sends an outbound SMS to a lead that currently has an active agent. The result is a cleaner, safer handoff where customers hear one clear voice at a time.

• Detects human outbound SMS activity on agent-active leads
• Automatically pauses the AI for that lead/conversation
• Prevents accidental double-sending and conflicting responses

SMS — Delivery Failure Reasons Logged & Visible in Conversations

Previously, when an SMS failed (bad number, carrier error, opted out, etc.), it was difficult to understand why—often forcing teams to rely on guesswork or external troubleshooting. MagicBlocks now captures delivery failure reasons for Relcu and Twilio sends and displays them directly in session/message logs. This makes it easier to diagnose issues quickly, reduce repeated failures, and keep outreach lists clean.

• Failure reasons are stored and shown alongside messages
• Enables faster troubleshooting and better operator decisions
• Helps prevent repeated sends to invalid numbers over time

🛠️ Improvements

Agent (Opt-Out) — Optional Opt-Out Reply Message

Previously, opt-out confirmations could be required in a way that blocked publishing or caused unwanted replies during unsubscribe flows. You can now control this with an Opt-Out Message toggle (OFF by default): when off, Agents can publish without opt-out message errors and won’t reply to opt-out messages; when on, you can select or customize the opt-out reply.

Campaigns — Default to “Run Agent AI” for outbound workflows

Outbound campaigns now open to Run Agent AI by default (instead of Upload Contacts), reducing extra clicks and making the next step clearer when launching an AI-driven send.

Templates — Update Existing Templates (instead of recreating them)

Templates can now be updated in place, so teams can keep a single, up-to-date source of truth instead of recreating and re-sharing multiple versions.

Human Takeover (Slack) — Clearer, Safer Slack Disconnect

Disconnecting Slack now includes clearer confirmation and guidance, helping operators avoid accidentally interrupting active Human Takeover sessions.

Human Takeover (Slack) — Clearer “How to find Channel ID” guidance

Human Takeover setup now includes clearer guidance for finding a Slack Channel ID, reducing setup friction and helping teams go live faster.

Worked Leads — More accurate counting when opt-outs happen early

Worked leads are no longer counted when an opt-out happens in the first or second message, using the Agent’s opt-out action (and contact opt-out status) as the source of truth. This makes worked-lead reporting more trustworthy.

🛠️ Fixed

Agent

• Fixed paused/unpublished agents still starting new sessions and responding on channels—so teams can safely pause agents during incidents or maintenance without unexpected customer replies.
• Fixed Save/Publish intermittently failing in the Agent Builder, which previously forced page refreshes and caused lost momentum while editing.
• Fixed cases where Agent Builder changes appeared saved but were lost after reloading the page.
• Fixed Block settings sometimes showing data from a previously selected Block when switching between Blocks, reducing configuration mistakes in multi-block agents.
• Fixed newly created Snippets, Goals, and Tasks not appearing immediately without a page reload, so builders can continue configuring without interruptions.
• Fixed Jobs To Do counts not updating immediately after removing Key Facts.

Human Takeover (Slack)

• Fixed Slack connections auto-disconnecting and breaking Human Takeover flows (message transfer, switch-back to AI, and reliability during live conversations).
• Fixed Slack disconnect being blocked due to incorrectly detected “active sessions,” allowing operators to manage connections without getting stuck.
• Fixed Slack connections dropping due to cross-workspace connection conflicts when the same Slack workspace was used across environments.

SMS & Consent

• Fixed SMS messages displaying raw markdown/checklist formatting, so AI responses render as readable, SMS-friendly text.
• Fixed SMS conversations linking to the wrong contact due to phone-number normalization mismatches (especially with country codes), ensuring conversations attach to the correct contact record.
• Fixed opted-out contacts still being able to receive outbound messages via API in some cases, improving compliance enforcement.
• Fixed chat-provided phone numbers not reliably influencing consent status, preventing contacts from being incorrectly treated as “No Consent.”

Contacts

• Fixed contact session history showing only the first 20 sessions even when more existed, restoring full visibility into customer history.
• Fixed Contact Details “Refresh” not reliably fetching the latest data, reducing the need for full browser reloads.
• Fixed phone search failing when the query included a country code across Contacts/Campaigns/Segments.
• Fixed phone filtering (e.g., “starts with”) returning incorrect results, including contacts without phone numbers.
• Fixed requiring a country code when manually adding or editing phone numbers, preventing invalid/ambiguous contact data.
• Fixed Contact API ignoring emailType/phoneType and defaulting to “other,” improving accuracy for downstream workflows.
• Fixed small mismatches between Contacts counts and “New Contacts” metrics when filters are applied, improving trust in reporting.

Sessions & Forms

• Fixed Sessions export UI not clearly enforcing the 90‑day window (and overlapping modal behavior), making exports more predictable and preventing confusion about missing data.
• Fixed updated Forms not loading correctly in Live Chat in some cases.
• Fixed Agents using an older Form version after a Form was updated and published, so customers always see the latest published fields.

Integrations

• Fixed Calendly links returning internal API URLs instead of customer-friendly public booking links.
• Fixed bulk delete controls missing for Webhooks and API Tokens, restoring expected admin workflows.

Dashboard & UI

• Fixed Dashboard showing incorrect contact subscription status (Subscribed/Unsubscribed).
• Fixed Contact Activity & Notes empty states appearing with incorrect styling, improving UI clarity.
• Fixed onboarding being skipped when re-signing up with a previously removed email.
• Fixed dark mode UI issues on logout/auth screens.

Release Summary

Total New Features: 5

Total Improvements: 6

Total Fixes: 29

Major Themes

• Agent Follow-Up automation
• Template collaboration across workspaces
• Relcu & SMS compliance controls
• Human Takeover reliability (Slack)
• Cleaner contact data and more trustworthy search/filtering

Top 5 Most Impactful Changes

1. Agent Follow-Up automation (timed follow-ups with routing controls) — Helps teams reduce dropped conversations by automatically following up based on inactivity, with clearer control over Block switching and channel routing.
2. Relcu callable hours enforcement with automatic queuing — Reduces compliance risk while ensuring outbound messages still go out at the earliest allowed time, saving teams from manual scheduling.
3. Relcu Human Barge auto-pauses AI on outbound SMS — Prevents mixed messaging and creates a cleaner handoff when humans take over high-stakes conversations.
4. Templates shared across workspaces — Makes it easier to standardize setups and roll out proven agent configurations across environments (especially staging → production).
5. SMS failure reasons visible in message logs — Cuts troubleshooting time by showing exactly why a message failed and what to fix next.