As August begins and summer starts coming to a close, we present this week’s Zoho Intelligence release! This week’s activity can be divided into two categories: a wave of new developer tooling (server-side A/B testing SDKs, CRM scripting power-ups, and sandbox parity for integrations) and persistent UX gaps that the community continues to surface. Teams that pay attention to both will ship better and frustrate users less.
PageSense Goes Server-Side: Full SDK Launches for iOS and Node.js
The biggest documentation push of the week was a complete FullStack A/B testing SDK rollout for PageSense, covering both iOS and Node.js. Both SDKs enable code-level experimentation, which is testing backend logic, pricing models, or feature behaviour without a new App Store release or a UI editor. The core pattern across both platforms is the same: initialize once at startup, use stable user identifiers for deterministic MurmurHash bucketing, and rely on webhook-based or polling-based sync to keep experiment configurations fresh. If your team runs any mobile or Node.js backend that could benefit from controlled rollouts or algorithm experiments, this is worth evaluating now — the SDKs are lightweight, have no third-party dependencies beyond bundled utilities, and the documentation is thorough enough to get to a working integration in an afternoon.
Zoho CRM Gets Serious About Developer Flexibility
Two significant CRM capability features landed this week. First, Client Script support for Custom Buttons is now available across all data centers — meaning you can attach JavaScript logic directly to button actions to auto-fill fields, run guided multi-step flows, prompt for confirmation before destructive actions, or dynamically toggle field visibility, all without a page reload. Second, the CRM Sandbox now supports integrations with Campaigns, Analytics, Finance, Forms, Flow, Creator, Circuits, and Backstage — so you can validate end-to-end automation behavior before it touches production data. Teams that have been reluctant to test complex cross-product workflows (for good reason) now have a safe environment to do so. The practical action here is to move any pending integration QA work into the sandbox before deploying, since the cost of a misconfigured Zoho Flow trigger or Finance field mapping in production is real.
Structured Data Gets a Push Across CRM and Recruit
Zoho is nudging teams toward more structured, contextual record data on multiple fronts. The new Address Field in CRM — now available in all DCs except a few Zoho One configurations in US/EU — replaces the old patchwork of separate street/city/state fields with a single structured input that handles country-dependent state dropdowns natively. Separately, Zoho Recruit’s new Reviews sub-module centralizes candidate evaluations from all stakeholders into a structured, sourced record rather than scattered email threads and interview notes. Both changes reflect the same principle: unstructured text fields create reporting and filtering debt that compounds over time. If your CRM still uses legacy address fields, plan a migration, and if your recruiting team is tracking assessments in email, the Reviews sub-module is now available on all Recruit plans.
Zoho Commerce Embraces AI-Assisted Store Management
A marketing post on Zoho Commerce MCP this week outlined what’s becoming a useful pattern: using the Model Context Protocol to connect an AI assistant (Claude, ChatGPT) directly to your Commerce store, enabling plain-language bulk operations across 150+ store actions — bulk SEO updates, coupon creation and management, shipping configuration. For store operators dealing with a lot of repetitive admin work, this is worth testing. Separately, a community post seeking a complete Commerce theme ZIP and safe staging workflow went unanswered, which signals that custom theme development and rollback workflows are still poorly documented territory, so proceed carefully if you’re building custom storefronts.
Persistent UX Friction: The Gaps the Community Keeps Hitting
Several threads this week highlight workflow pain points that have been open for months or longer with no committed timeline. CRM users still cannot filter Task notes to show only task-specific entries rather than all related-record notes — Zoho has confirmed it’s on the long-term roadmap. Sending ad-hoc batch emails in CRM without a template remains impossible by design. In Zoho Books, printing an invoice without a “Draft” stamp requires a clunky manual workaround, and bank transaction rules have been moved to a global overview screen in a way users find confusing and risky. These aren’t new problems — they’re recurring frustrations. If any of these affect your team, document the workaround now and submit explicit feature requests; community visibility is the clearest signal that moves these up the queue.
What to Watch Next Week
Client Script support for the new CRM Address Field is still listed as “underway” — watch for that to drop, as it will unlock validation and auto-fill logic for the new structured address input. Also, keep an eye on whether Zoho Commerce responds to the unresolved theme staging question; it’s a gap that blocks custom development work.