This week, well into the Chicago summer heat, we introduce three main topics. These include Zoho CRM receiving some of its most substantive power-user upgrades in months, Zoho Bookings 2.0 getting a documentation refresh that signals a maturing platform, and several persistent developer pain points — from hardcoded webhook secrets to broken Zia Agent deployments — which reminds us that the gap between Zoho’s feature announcements and reliable production use remains real.
Zoho CRM Gets Serious About Power Users
Three meaningful CRM enhancements landed this week, and together they point at the same thing: Zoho is pushing CRM toward a tool that can handle complex, role-differentiated teams without requiring workarounds. The Related List Expanded View breaks the long-standing 10-record limit on related lists, letting reps view up to 100 records per page, filter by field, and take mass actions — all without leaving the detail page. Separately, Layout Rules gained nine new actions, profile-based execution, and an interactive preview (currently JP and SA data centers, rolling out broadly soon), meaning admins can now build genuinely role-specific form experiences rather than one-size-fits-all layouts. And Kaizen #250 introduced write-enabled Queries — REST API sources in the Query Workbench now support POST, PUT, PATCH, and DELETE, enabling end-to-end automation of lookup assignments inside Blueprint-driven Kiosk flows. If your team builds heavily on Blueprints and Kiosks, the write-enabled Queries capability is worth prototyping now; it eliminates a whole category of custom function workarounds.
A Security Gap in CRM Webhooks That Deserves Attention
A well-articulated feature request this week exposed a real security problem: native CRM webhooks store authentication secrets — API keys, bearer tokens — in plaintext, visible to anyone who can read the webhook configuration, including sandbox developers, agencies, and anything connected via the CRM MCP server. The ask is to let webhooks authenticate via the existing Connections framework instead. Until that ships, any team sharing sandbox access with external developers should audit their webhook configurations and consider rotating secrets or routing sensitive calls through custom functions with Connections, where credentials are not exposed in the configuration UI.
Zoho Bookings 2.0 Documentation Is Now Comprehensive — Time to Migrate
The volume of updated Bookings 2.0 KB articles this week — covering workflows, copy/move for event types, booking forms, calendar invites, email and SMS alerts, and booking page settings — signals that the 2.0 platform is being treated as production-ready. The workflow trigger list is notably rich, covering everything from booking and rescheduling to payment failure and no-show, with support for email, SMS, and custom functions. If your team is still on Bookings 1.0, the documentation is now mature enough to plan a migration with confidence; the copy/move event type feature alone removes a major friction point when reorganizing workspaces.
Zoho Creator Grows Up: Hotfix Support and MCP Integrations
Zoho Creator quietly shipped a capability that enterprise app builders needed for a while: production hotfixes in the Environments framework, allowing critical fixes to be applied directly to production without waiting for a full dev-to-stage-to-prod cycle, with automatic reverse-merging back to lower environments. This applies to apps published through the standard pipeline after June 27, 2026. Separately, Zoho Notebook published new guides for connecting its MCP server to Claude Desktop and Cursor, a sign that Zoho’s MCP layer is expanding beyond CRM into the broader productivity suite. Teams building Creator apps in production environments should review the hotfix eligibility criteria — only apps published post-June 27 qualify, so pipeline timing matters.
Zia Agents and Desk Extensions: Promising Features, Rough Edges
Two developer threads this week illustrate the gap between Zoho’s AI ambitions and day-to-day reliability. A user who has spent weeks trying to deploy a Zia Agent with WhatsApp integration reports persistent “Agent Deployment Failed” errors and unresolved channel connection issues — a cautionary note for teams planning production AI agent rollouts. Similarly, a developer building a Zoho Desk widget hit a wall where Sigma function calls hang indefinitely because app_install_id and encapiKey resolve as null in the merge field context. Both issues remain open. If your team is evaluating Zia Agents for customer-facing workflows, treat it as early access in practice — budget for support escalation time alongside development time.
Long-Standing Feature Gaps Resurface
Two ideas threads worth watching bubbled back up this week. The Zoho Desk request for dynamic date filters in views — “today,” “this week,” “this month” — is still marked “under review” after nearly five years; the community frustration clear and the use case is basic. And a four-year-old CRM/Campaigns thread asking for per-link click data to be surfaced in CRM remains unresolved, with nine upvotes and no delivery date. Both gaps represent real friction for sales and support teams — if your workflows depend on either, plan around them with Campaigns reporting or custom dashboards rather than waiting for native delivery.
Next week, as many watch the FIFA World Cup come to an end, also make sure to watch for the Layout Rules rollout to reach additional data centers beyond JP and SA, and keep an eye on whether Zoho acknowledges the webhook secrets security thread — it’s the kind of issue that tends to get a quiet fix rather than a public announcement.