Happy Fourth of July! Despite the foggy weather in Chicago, America’s 250th anniversary was truly special. Amid the fireworks and weekend celebrations, we bring you this week’s Zoho digest. This week, our news is split into two: a wave of deliberate product investment — AI scaffolding, compliance tooling, and workspace unification — and a persistent undercurrent of gaps that teams keep hitting in Desk, Books, and CRM. The signal worth watching is how often the workaround to a Zoho limitation is another Zoho product, which is both the platform’s greatest strength and its most honest design admission.
Zoho Creator Is Becoming the AI Development Platform
Zoho quietly shipped a cluster of interconnected Creator documentation this week that, taken together, reframes the product as a serious low-code AI runtime. Updated KB articles covering Zia features in Creator, LLM configuration (supporting Zoho GenAI, OpenAI, Google, and Anthropic), and Zia App Builder all landed together, alongside refreshed fundamentals on Connections, Integration Forms, and Workflows. The practical demo arrived in the form of Kaizen 249, which walks through building a Zia Agent-powered room recommendation assistant using CRM Widgets, Catalyst Functions, and Catalyst Connections. If your team builds on Creator (like we do), now is the time to evaluate whether your existing automations should be rebuilt with AI agents rather than scripted logic — the infrastructure is clearly being hardened for production use.
CRM Gets a Privacy Layer and Workspace Depth
Two meaningful CRM additions landed this week on opposite ends of the maturity curve. On the new side, Cookie Consent Management for CRM webforms gives teams a native opt-in/opt-out banner with privacy-policy linking — a long-overdue compliance feature for anyone running GDPR-governed markets. On the other side, Zoho Projects can now be embedded directly into CRM Teamspaces, so marketing or delivery teams no longer have to context-switch between the CRM record and the project tracker. Also, the email composer now supports custom fonts and a default reply-to address: small but welcome for teams with strict brand or routing requirements. Teams managing cross-functional work inside CRM should revisit their Teamspace setup; the Projects integration materially closes the gap between CRM and project execution.
Zoho Desk Has Persistent UI and Workflow Gaps
Three separate Desk threads this week all point to the same underlying issue: the product’s customization model has hard ceilings that frustrate mature support operations. Status colors are locked to category (Open = black, On Hold = orange, Closed = green) with no per-value overrides — the workaround is a separate coloured picklist field running alongside the real status field. The ScreenPop integration confirmed it can surface open tickets on inbound calls but cannot let agents populate and create a new ticket directly from the pop — a real friction point for call-center workflows. And a seven-year-old idea requesting the ability to delete individual ticket thread replies (auto-replies, duplicates) is still marked “Maybe later” with 26 votes. Teams hitting these walls should document their exact use cases and vote on open ideas — Zoho has previously used vote counts as a prioritization signal.
Analytics Reporting Has a WhatsApp Blind Spot
A user discovered this week that WhatsApp Campaign data from Zoho Marketing Automation is completely absent from the Analytics sync connector — despite WhatsApp being a fully supported sending channel. The gap means unified channel reporting requires manual CSV exports or custom API work. The user immediately filed a feature request for native sync support. If WhatsApp is part of your marketing mix and you rely on Zoho Analytics dashboards, budget for a manual export workflow or a custom connector until this is resolved — there’s no native path today.
Zoho Books Has Real Financial Compliance Friction
Two separate Books issues this week point to gaps that carry actual financial risk for specific customer profiles. One user reported that Level 2 payment data fields required by Authorize.net (PO Number, Tax Exempt) cannot be passed through Books — and confirmed the gap had already cost them nearly $5,000 in excess processing fees. Zoho’s response acknowledged the pipeline item but offered no timeline. Separately, a user flagged that Books doesn’t enforce or report against Indian cash receipt limits (₹10,000/day, ₹2 lakh/year) or differentiate cash vs. bank receipts in statements. If either scenario applies to your operation, we reccomend to reach out to Zoho support with documented financial impact.
The “Build It in Creator” Pattern Is Everywhere
A quieter but important meta-theme this week: the recommended answer to product limitations increasingly points back to Creator. CRM Canvas can’t embed a dynamic calendar? Build it in Creator and embed as a widget. ScreenPop can’t create tickets inline? Custom widget. Calls module too rigid to customize? Zoho says extended customization is planned but not started. This pattern has two readings: Creator is genuinely powerful glue, but relying on it for core product gaps adds maintenance surface area that many teams underestimate. Before building a Creator workaround, assess whether the gap is on Zoho’s roadmap — the GarantíaYa case study published this week is a useful reference for what deep platform commitment looks like when it works.
Read on next week for any movement on the Calls module customization roadmap — Zoho confirmed it’s planned but unstarted, and community pressure is building. Also, we’ll see whether the WhatsApp Analytics connector gap draws an official response now that a feature request has been formally filed. Once again, Happy 4th!🎆