This week’s Zoho community brings a wave of meaningful new capabilities: Workqueue, Record Summary, Radar updates, Notebook’s MCP bridge, but running in parallel with persistent issues, particularly around cross-product data integrity and search gaps that quietly erode daily trust in the platform. Teams that only track changelogs will miss the second half of that story.
Zoho CRM Gets a Productivity Overhaul, and the Timing Is Deliberate
Three significant CRM releases landed in close succession, and together they form a coherent push toward reducing the context-switching tax on sales teams. Workqueue consolidates tasks, approvals, blueprint actions, and Zia Vision validations into a single customizable dashboard, the kind of feature that sounds incremental until you realize how much time reps lose jumping between Activities, workflow inboxes, and module views. Alongside it, Record Summary uses Zia to surface a consolidated snapshot of deal status, recent interactions, and related tasks without requiring the user to scroll through the full detail page. The August digest also confirms bulk approval actions and saved portal filters are now live. If your team hasn’t audited their Blueprint and approval workflows recently, now is the right moment: these tools are only valuable if the underlying process logic is clean.
Notebook Is Becoming a Serious Product
The volume of Notebook KB updates this week is unusual and worth paying attention to. Zoho published or refreshed documentation covering MCP (Model Context Protocol) support — which lets AI assistants like Claude and ChatGPT read, create, and organize notes directly inside Notebook via OAuth — alongside articles on PDF annotation, passcode/biometric locking, Pro plan details, and its inclusion in the Projects Plus bundle. The MCP integration is the one to watch: it positions Notebook as an AI-accessible knowledge layer rather than just a note-taking app. For teams building on Zoho One or Projects Plus, Notebook is now a more credible alternative to external PKM tools — worth evaluating before renewing third-party subscriptions.
The CRM–Books Data Boundary Remains a Real Problem
Two community posts this week independently surface the same structural tension: business logic defined in CRM doesn’t survive the handoff to Books. One detailed idea submission argues that CPQ pricing rules, discount matrices, and bundle dependencies should travel with a quote when it becomes a Books invoice — today, Books receives flat line-item totals with no knowledge of the CRM rules that generated them, meaning a manual price edit in Books can silently bypass discount policies. Separately, a Books user found that there is no client-script equivalent in Books for real-time validation during quote or invoice creation — the workaround is building a Sigma extension, which isn’t available in all data centers. Teams that use CRM’s CPQ features and sync to Books should document exactly where their pricing governance breaks down at the boundary; these gaps are unlikely to close soon and need compensating controls in the meantime.
Zoho Books Friction Points Are Stacking Up
Beyond the CRM–Books boundary issue, several discrete Books pain points resurfaced this week that individually seem minor but collectively signal an admin experience that hasn’t kept pace with the product’s feature growth. A three-year-old idea requesting per-invoice control over Stripe CC vs. ACH payment methods remains marked “Maybe later” despite growing votes. A user discovered that eTIMS integration in Kenya forces inventory tracking on all goods items, breaking expense categorization for non-inventory purchases with no override. Custom fields added to Customers bleed into the Vendor module with no hide option. And the Draft stamp on printed invoices requires a manual workaround to suppress before printing. None of these are showstoppers alone — but if your team is hitting multiple items on this list, it’s worth logging them with Zoho support explicitly rather than working around them silently.
CRM Search and Custom Module Gaps Creating Workflow Failures
Two CRM usability issues this week deserve more attention than they’re getting. Global Search’s failure to match substrings after punctuation — meaning a search for “Connor” won’t surface “O’Connor” — is confirmed expected behavior, not a bug. In practice this means reps may tell callers their record doesn’t exist and create duplicates. The fix requires a product-level change to move from starts-with to contains matching, but teams can mitigate now by training reps to always search with the full surname including prefix. Separately, email addresses pulled in via the Duplication component on custom modules aren’t recognized as native email fields, so the Send Email button won’t use them — a quiet blocker for teams building complex custom module architectures.
Zoho Desk Doubles Down on Automation Accessibility
Desk published a cluster of automation-focused documentation this week — covering custom functions, the Custom Actions Gallery, macros, and schedules — alongside a meaningful product update: Radar now surfaces Contacts, Accounts, Activities, and custom modules for mobile managers. The documentation push suggests Zoho is trying to lower the barrier to Desk automation for admins who aren’t Deluge-fluent — the Custom Actions Gallery in particular offers pre-built workflow actions that require no coding. If your Desk setup still relies heavily on manual agent actions for repetitive ticket patterns, this week’s docs are a practical starting point for closing those gaps.
Watch next week for any movement on CRM’s new Address Field reaching full US and EU DC rollout — it’s been in a prolonged staged release and Client Script support is still pending — and whether the Workqueue and Record Summary features prompt follow-on announcements around Zia permissions and summary customization.