Welcome to this week’s Zoho Community Intelligence Release! As everyone was on the edge of their seats today while watching Argentina vs. Spain in the FIFA World Cup Final, we were cheering right alongside them when Spain finally won! To conclude this exciting Sunday, we have brought you the latest updates on Zoho Bookings, Zoho CRM, Zia, and questions that persist when users attempt to sync their info across Zoho products.
Zoho Bookings 2.0 Is Getting a Full Documentation Overhaul — Signals Broader GA Readiness
The single biggest pattern this week is the sheer volume of Bookings 2.0 knowledge base articles updated in a single sweep: Workspaces, Customers, Resources, Routing Forms, Booking Pages, In-product Notifications, Reports, and more were all touched this week. When Zoho does a coordinated doc refresh at this scale, it almost always precedes broader rollout or a push to migrate users off the legacy version. If your team runs Bookings 1.0, this is the week to map your current setup against the 2.0 architecture — every updated article includes a direct link to its 1.0 equivalent, making change easy. Pay close attention to the Zia-powered booking page customization, which auto-applies your website’s branding palette — a meaningful time saver for teams managing multiple workspaces.
Zoho CRM Is Getting More Intelligent Forms and Tighter Automation, but Gaps Remain
Two significant CRM capability updates landed this week. The Layout Rules expansion adds nine new actions, profile-based execution, and an interactive preview — meaning Enterprise and Ultimate admins can now build forms that dynamically adapt based on a user’s role, not just field values. This closes a long-standing gap between CRM’s flexibility and its usability. Separately, WorkDrive-powered file storage is now rolling out to all existing CRM accounts across all editions, bringing modern file management and cheaper storage to everyone — not just new signups. The catch: the rollout requires admins to proactively schedule the migration by choosing a WorkDrive account and picking a slot, so this won’t happen automatically. Check your account now and get it on the calendar before it becomes an urgent item. Meanwhile, the five-year-old subform automation request (131 votes, still “working on it”) continues to surface — teams relying on subforms for field service or equipment tracking should plan around this limitation with Deluge rather than waiting on native workflow triggers.
Zia Is Expanding Everywhere
Zoho is pushing Zia deeper across the suite: Zoho Desk’s full AI feature set: which includes sentiment analysis, anomaly detection, generative reply assistance and more, is now available across all paid editions, not just Enterprise. Zoho Sign’s Ask Zia now lets signers interrogate contract content before signing. On paper, the AI story is compelling. In practice, one detailed community post documents weeks of failed Zia Agent deployments and an inability to connect WhatsApp, with support unable to resolve it. The gap between Zoho’s AI announcements and production reliability is real. Teams evaluating Zia Agents for customer-facing automation should build in significant buffer time for setup, avoid committing to hard go-live dates, and test channel connections (especially WhatsApp via Business Messaging) in isolation before wiring them to CRM workflows.
Integration Seams Keep Causing Data Problems
Three separate community threads this week point to the same underlying risk: data syncing between Zoho products. A user switching their CRM-to-Books sync from Contacts to Accounts has no clear answer on whether existing customer records will merge, duplicate, or break — after years of transactional history. Reconnecting a WhatsApp channel in Zoho Desk silently created a new channel ID, orphaning all prior conversation threads. And Zoho Books pricelists simply don’t appear in Zoho Commerce, with no substantive support response after several days. The pattern: Zoho’s cross-product integrations frequently lack safeguards around destructive changes, and support response on integration edge cases is inconsistent. Before making any sync configuration changes that touch financial or customer history data, document your current state, run a sandbox test, and open a support ticket proactively — don’t assume the UI will warn you.
Persistent Blind Spots: Reporting and Browser Compatibility
Two quality-of-life issues resurfaced this week that are worth flagging for any team running Zoho at scale. Zoho Desk’s Community module has no Analytics reporting at all — confirmed by Zoho support — meaning teams using Community for customer self-service have zero visibility into its performance. If you’re measuring support deflection, you’ll need to instrument this externally. Separately, a Chromium browser bug in Zoho Desk causes PDF attachments to open and save as “content.pdf” instead of the original filename, affecting anyone on Chrome or Edge, which is most support teams. The download icon preserves the correct name, so it’s a workable workaround, but it’s the kind of friction that erodes agent trust in a tool over time.
Watch next week: Whether the CRM Layout Rules expansion and Zia Desk AI rollout reach non-JP/SA data centers on schedule, and whether any resolution emerges on the Zia Agents deployment failures that have left at least some early adopters blocked for weeks.