Zoho Campaigns now lets AI agents plan, build and launch WhatsApp, email and SMS campaigns from one plain-language instruction, running on the Model Context Protocol (MCP). That shipped on 13 November 2026 as part of a full rebuild of the platform. It's the first time a mainstream SMB marketing tool has put all three channels and an agent in one workflow, and the agent still needs your sign-off before anything actually sends.
What do Zoho Campaigns AI agents actually do?#
Three things, bundled into one release. WhatsApp is now native: bulk sends on approved templates, trigger-based messages, and WhatsApp steps sitting inside the same automated workflow as email and SMS, not bolted on separately.
The AI agent layer runs on MCP, the same open protocol we've been testing in client chatbot builds. Zoho's own examples are mundane in a good way:
- Rebuild a seasonal campaign from scratch
- Re-run your best-performing send after analysing your last ten campaigns
- Launch a win-back flow for contacts quiet for 90 days
And a frequency cap now runs across WhatsApp, email and SMS together, so one contact can't get hit twice in the same window from two different channels.
Zoho says internal testing showed sending 100,000 emails up to four times faster and importing 100,000 contacts up to five times faster. Those are its own numbers, with no outside audit attached. Paid plans still start at $4 a month. WhatsApp and SMS sending needs purchased credits on top. It's live now, in every region. (IT Brief Australia; official background on Zoho's MCP rollout)
Who should actually care about this#
If you're sending a few thousand WhatsApp messages a month through a chatbot setup that already works, this changes nothing for you today. Swapping platforms to chase an agent you haven't tested is a bad trade.
If you're running WhatsApp, email and SMS through three separate logins and reconciling send limits by hand, it's worth a real look. At WebEpex we build WhatsApp automation for GCC and Indian SMB clients on n8n and Voiceflow rather than inside one marketing suite. That's mostly so the WhatsApp step, the lead logic and the CRM write all happen in one pipeline we control end to end. This release doesn't change that approach. It does mean fewer of our clients' other tools need a bolt-on WhatsApp workaround now that one of the big ones ships it natively.
What's genuinely good here, and what isn't#
The shared frequency cap is the quietly useful part. Contact fatigue across channels is boring and almost nobody fixes it properly. Most platforms cap one channel and ignore the other two.
The MCP agent layer is more interesting in theory than in practice right now. Zoho names no specific compatible agents, and "marketers remain responsible for campaign decisions" is doing a lot of work in that sentence.
We've hit this exact wall ourselves. Building a Voiceflow concierge bot for a retail client earlier this year, MCP let the agent read our knowledge base cleanly. Writing rich content back wasn't reliable, though. We ended up pasting it in as fixed blocks instead of letting the agent handle it end to end. I'd test any MCP-agent claim against real campaigns before trusting it with real budget. Not dismissing it. Just not taking Zoho's word for it either.
How we're handling it this week#
We checked two client flows that message across WhatsApp and email on separate schedules, because reading about Zoho's shared cap made us wonder if ours had the same gap. Neither flow had one. We added a shared cap to both this week, same logic Zoho just shipped, built directly into the n8n workflow instead of waiting on a platform feature.
That's also where our retry logic lives. On a WhatsApp lead-qualification bot we shipped for a Dubai real estate agent this quarter, the retry sits before the lead-categorisation step, not after. A timeout there drops a warm lead silently. That's the invisible failure, not the loud one, and it costs more than the obvious mistakes a client actually notices. WhatsApp's own pricing shifts get the attention; the quiet failure modes rarely do.
What I'd tell a client this week#
If you're already on Zoho, turn on native WhatsApp and the frequency cap. Low risk, clear upside. Hold off handing real campaign decisions to the MCP agent until you've watched it build two or three campaigns you'd have built yourself and compared the output.
If you're not on Zoho, don't switch for this. Ask whatever tool you're on now whether it caps message frequency across channels, the way Klaviyo's recent AI push and now Zoho both do. That part costs nothing to copy today.
If you want a second pair of eyes on whether your WhatsApp and email are stepping on each other, send me what you're running. cal.com/webepex/growth-review. Takes two minutes, no pitch attached.