Salesforce is positioning its next-generation marketing stack, Marketing Cloud Next, as the platform's exit ramp from "do-not-reply" outbound. A Demand Gen Report headline frames the announcement: the company wants brands to stop broadcasting and start holding conversations.

Why does the "do-not-reply" label matter?

"Do-not-reply" has long described one-way brand communications where the customer has no reply path. No-reply@ sender domains, 5-digit short-code SMS, programmatic display, and call-center outbound scripts all fit that label. Customers see them. They cannot answer them.

Two-way engagement reroutes replies into structured workflows where human agents, AI assistants, or both can respond in real time. The marketing cloud historically sits on the send side. Ending the do-not-reply posture means adding a structured receive side without handing the conversation off to a separate service cloud. That is not customer service rebranded. Service runs inbound. This is outbound with a reply path attached.

What changes for marketing operations?

For practitioners, the practical shift is the routing layer. Two-way programs demand:

• Reply-handling SLAs — who picks up a customer reply and in what window.
• Channel-agnostic conversation state — a single thread across SMS, WhatsApp, email, and web chat rather than a fresh message each time.
• Consent guardrails — opt-out requests on a conversational thread have to be honored in real time, including any SMS short-code TCPA and CTIA obligations.
• CDP integration — replies carry intent signals (purchase, complaint, unsubscribe) that must land in the same customer profile record the original send came from.

What does ending "do-not-reply" actually require of brands?

Brand teams that walk away from the do-not-reply posture commit to staffing real-time reply paths. That means loops into sales, service, or AI agents, plus governance over what an automated assistant can say and when it must hand off to a human. Compliance teams need a seat at the design table because conversational outreach carries different consent rules than broadcast outreach in markets with strict privacy regimes, including the EU's GDPR, California's CCPA/CPRA, and Brazil's LGPD.

Procurement matters too. Marketing and service clouds that have lived in different cost centers now need a shared budget conversation about who pays for the reply-side seats, AI agent minutes, and SMS throughput a two-way campaign consumes.

The underlying bet looks straightforward: as inbox and SMS fatigue push response rates lower, marketers that retain a reply path collect cleaner intent data and stronger lifetime-value signals than competitors who don't.

What should practitioners watch for in Marketing Cloud Next?

Three specifics to track on the rollout:

1. Pricing and packaging — whether conversational reply handling sits in the existing Marketing Cloud tiers, an add-on, or a new SKU.
2. Agentforce integration — whether AI agent hand-offs ship bundled or bill separately.
3. Data Cloud hooks — whether the new stack ships with the unified profile schema natively or still needs a separate layer to tie replies back to a customer record.

The Demand Gen Report headline foregrounds conversation over channel. Until specific features, prices, and GA dates land, practitioners shopping for two-way engagement should treat Marketing Cloud Next as a directional bet rather than a SKU they can quote inside 2025 budgets.