In this edition, we’re highlighting a few more product enhancements, along with some helpful community discussions that explore everyday CRM scenarios from automating reminders and managing lead outreach to making the most of APIs and client scripts.

This is Part 2 of our deep dive into the most important announcements and discussions from the Zoho CRM Community in February. Let’s take a look at what surfaced in the community.

Product Updates:

Developers can now trigger Client Scripts during load, change, and save events within Quick Create forms, ensuring consistent business logic across all record creation entry points. This update introduces the '$Client.rootContext' variable, which allows scripts to access data from the parent page where the Quick Create form was initiated. Leverage this context to auto-populate fields and fetch parent record details without additional manual input, streamlining the user experience and maintaining data integrity.

Zia-powered dashboards can now be fully customized to match your specific business needs. This update allows you to modify metrics, adjust filter criteria, and add or edit dashboard components, to fine-tune how anomalies and sales trends are calculated. Leverage these new capabilities to ensure your AI-driven insights remain relevant and actionable for your unique sales process.

Testing email automation in Sandbox just got easier with the introduction of the Email Outbox. View and verify every email triggered through workflows, approvals, or other automation before deploying changes to production. The Outbox organizes emails by category and trigger type, showing key details like subject, source record, and module for quick review. Utilize this capability to validate your email content and automation logic before going live.

@joe.siart recently highlighted a common setup hurdle: a new Agent user could only see the records they owned. Ever wondered why that happens? @Sunderjan Siddharth explained that modules are set to “Private” by default in Data Sharing Settings, which limits users to their own records. Changing the sharing level to Public Read Only or Public Read/Write can expand record visibility across your team.

@Tony Dickmeyer recently asked if tasks without a reminder would still trigger an email notification on the due date. @Ishwarya SG clarified that no email is sent by default unless a reminder is set. Handle this by creating a Workflow rule to send an email to the task owner on the due date if the task remains open.

@Tysean Jackson wanted to stop multiple sales reps from contacting the same leads while prospecting. @Ishwarya SG suggested using Assignment Rules to distribute leads via a round-robin system, ensuring each record has a single owner from the start. To prevent reps from accidentally working on their colleagues' records, one can adjust Roles to disable “Share Data with Peers”. This ensures each rep focuses strictly on their assigned leads.

While reviewing COQL documentation, @David wondered how API credits are calculated when using aggregate functions like COUNT or SUM. @Jeganprabhu S clarified that these queries consume just 1 API credit, since they don’t require a LIMIT parameter.

And with that, we wrap up this January's Zoho CRM Community Digest. Caught something cool we missed, or have a favorite from this edition? Drop it in the comments! We’d love to hear from you.

If you haven’t already, don’t forget to check out Part 1 of the February Digest to explore the earlier updates and discussions from the month and complete the roundup. We’ll be back with more updates and community gems. Until then, stay tuned!