WATI vs Zoho Mail

The crawled feed is Zoho's mail blog rather than a release log, so most entries are thought-leadership and PR — deliverability explainers, an admin-reports series, a security award — rather than shipped changes. Cutting through that, the substantive product signals are a Zoho Mail MCP server that exposes the inbox to AI agents and Client Scripting for client-side automation. Those two point to a real product direction; the rest is content marketing.

Where there is product signal, it leans toward programmability and agent access: Client Scripting lets teams encode rules and automation into the mail client, and the MCP server lets external AI agents read and act on mail. Zoho appears to be positioning Mail as something other software and assistants drive, not just a human-operated web client. The volume of security and admin-reporting content also suggests continued emphasis on the IT-admin buyer.

Hard to forecast cadence from a marketing feed, but the MCP and scripting threads suggest the next concrete moves will deepen automation hooks and agent permissions rather than redesign the end-user inbox. The crawl source should be pointed at a true release/changelog feed before reading much into shipping velocity.