This week, we bring you two Zoho stories: an infrastructure headache affecting anyone sending email through Zoho to Microsoft 365, and a significant leap forward in AI-assisted development tooling for CRM builders. Underneath both ran a theme — teams hitting the edges of what Zoho’s billing and payments layer can automate natively.
Zoho-to-Microsoft 365 Email Delivery: A Shared Infrastructure Problem
Multiple Zoho products are generating the same 451 4.7.500 Server busy bounce from Microsoft Exchange this week, and it’s not isolated to one account or sending domain. The pattern surfaced in Zoho Desk (affecting multiple sending IPs including 165.173.180.51 and 165.173.182.51) and independently in Zoho Mail. Zoho support has attributed the errors to Microsoft-side throttling of external senders rather than a Zoho reputation failure — but that distinction offers little operational comfort when outbound replies are sitting in a queue. If your organization sends support responses, invoices, or any time-sensitive communications to partners or customers on Microsoft 365, treat this as an active risk right now: verify delivery status rather than assuming sent equals received, and ask Zoho support whether your account can be shifted to a different sending pool while Microsoft and Zoho work through the congestion.
Zoho CRM Goes AI-Native for Developers
Zoho made its most developer-forward move in some time this week with the launch of the zoho-crm SKILL.md — an agent skill designed to work inside AI coding environments like Claude Code, Cursor, and VS Code Copilot. Rather than requiring a developer to know which of CRM’s primitives (REST API, Deluge, Client Script, COQL, Widgets, Connections) applies to a given task, the skill acts as an orchestration layer that selects the right tool, loads the relevant reference, and generates a solution. Paired with this, Zoho migrated its public OAS repository from JSON to YAML and restructured it specifically for LLM navigation — each resource now has its own folder with a schema file, an index.md, and per-operation subfolders. The companion Kaizen #258 walks through getting started. For any team doing active CRM development, dropping this skill into your AI coding environment should meaningfully reduce the lookup overhead that slows Deluge and API work — it’s worth testing against a real task this week.
The Payment Surcharge Gap in Zoho Billing and Books
Three separate threads this week converged on the same unmet need: automatically passing payment gateway fees (credit card surcharges, convenience fees) through to customers based on their chosen payment method. The requests appeared in Zoho Billing, Zoho Subscriptions, and Zoho Books. Zoho’s official answer remains consistent: native automation for this doesn’t exist, and the closest workaround is adding a fixed add-on or manual line item — which applies to all invoices regardless of payment method. The legal complexity is real (surcharge rules vary by jurisdiction and card network), but the volume of community asks signals genuine demand. Teams that need this today should build a custom function triggered on payment method selection, with the understanding that the surcharge will be included in the gateway’s fee calculation on the total.
Zoho Desk API: A Reproducible Server Error Worth Knowing
A reproducible HTTP 500 has been confirmed in the Zoho Desk tickets search API when a modifiedTimeRange query hits the specific timestamp 2026-03-08T02:00:00.000Z as a boundary — adjacent ranges succeed, only that exact boundary fails. Zoho support’s current recommendation is to use a minimum one-minute window rather than narrow millisecond-range queries. If you’re running any sync or ETL job that pages through Desk tickets using tight time-window increments, add error handling for HTTP 500 responses and widen your range windows. This is likely a daylight saving time boundary artifact worth watching for in other products that use similar time-range query patterns.
CRM Custom Module Identifier Fields: A Long-Running Gap
A thread with 15 upvotes resurfaced this week around an issue that has frustrated CRM admins for years: once you set a custom module’s primary identifier field to auto-number, you cannot change it back to a name field without rebuilding the entire module and all its integrations from scratch. Zoho acknowledged plans to offer identifier field customization but flagged it as early-stage analysis. The practical advice for anyone configuring a new custom module: default to a name-based identifier unless you have a deliberate reason to use auto-number, because reversing that decision is painful. Teams already stuck with the wrong setup have reported rebuilding full modules including Zoho Flow connections and analytics — factor that cost into any current-state audit.
What to Watch Next Week
Monitor whether the Zoho-to-Microsoft 365 delivery issue resolves or broadens — if the throttling persists beyond this week, it may indicate a longer-term IP reputation problem that warrants escalating directly with both Zoho support and your Microsoft 365 admin. Also worth tracking: whether Zoho CRM’s new address field completes its rollout to remaining US and EU DC editions, where it has been conspicuously absent while other data centers gained access months ago.