Kaizen 185 - Subqueries in COQL API

Kaizen 185 - Subqueries in COQL API


Hello everyone!!

Welcome to another Kaizen week, where we discuss developer centric topics every Friday. This week, we have picked an interesting topic to discuss - Subqueries in COQL API.

Zoho CRM's CRM Object Query Language (COQL) is a powerful way to retrieve data from your CRM in a structured manner. With the release of COQL API version 7, we introduced a suite of enhancements, detailed in our previous Kaizen post. Today, we will cover one enhancement in detail—Subqueries.

Before the introduction of subqueries, filtering data dynamically across related modules required multiple API calls and additional code handling. Subqueries have fundamentally changed this, offering increased flexibility, reduced API consumption, and improved query performance. In today's Kaizen, we will explore what subqueries are, where and when to use them, their advantages, and a few practical use cases. We will also go through a few examples with different operators to help you understand COQL subqueries better.

What are Subqueries?

At its core, a subquery is a query nested within another query. This technique allows you to retrieve data from one module based on conditions derived from another related module. Think of it as a way to ask more sophisticated, multi-layered questions of your CRM data.
Imagine you're working on a CRM integration and need to find all Contacts associated with Accounts that have at least one Deal created in the last 30 days.

Before Subqueries:

Before subqueries, achieving this required multiple steps:
  1. Retrieve Account IDs from the Deals module where a Deal was created in the last 30 days - {"select_query": "SELECT Account_Name, Created_Time FROM Deals WHERE Created_Time >= '2025-01-01T00:00:00+05:30'"}
  2. Use these Account IDs in a second query to fetch associated Contacts - {"select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in ('4876876000007481116', '4876876000007420031')"}
This requires writing extra code to store and use the Account IDs from the first query in the second query. This also means making multiple API calls, and handling responses separately. However, with Subqueries in COQL, this can now be achieved in a single query.

Using Subqueries:

With subqueries, you can achieve the same result in one single query!
{
  "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT Account_Name FROM Deals WHERE Created_Time >= '2025-01-01T00:00:00+05:30')"
}
The Subquery (SELECT Account_Name FROM Deals WHERE Created_Time >= ...) retrieves Account IDs where a Deal was created in the last 30 days. The main query (SELECT Full_Name, Email FROM Contacts WHERE Account_Name IN (...)) fetches Contacts linked to those Accounts, all in one API call!
But there is a catch. Subqueries return only up to 100 records per query. If more than 100 matching records exist (e.g., over 100 Accounts with recent Deals in this case), the extra records are silently ignored. This can lead to incomplete results, so subqueries are best used when the filtered dataset is known to be small. Please head over to the Limitations section to learn about other limitations. 

Where to use Subqueries?

Subqueries in COQL are useful when there is a need to filter data dynamically based on conditions from other modules. Instead of fetching records separately and processing them, subqueries allow you to retrieve the required data in a single query.
Here are some common use cases where subqueries come in handy:

  • Segment accounts based on high-value Deal history: For instance, you can use subqueries to fetch accounts that have at least one high-value closed Deal. 
    { "select_query": "SELECT Account_Name FROM Accounts WHERE id in (SELECT Account_Name FROM Deals WHERE Amount > 100000 AND Stage = 'Closed Won')"}

  • Find Contacts whose Accounts have NEVER closed a deal: You can use subqueries in COQL to fetch Contacts that have no associated Deals. 
    {"select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name not in (SELECT Account_Name FROM Deals WHERE Stage != 'Closed Won')"}

  • Identify new Leads who haven’t been marketed to yet: For instance, if need to find all leads who were NOT part of a specific campaign, you can use Subqueries in COQL.
    {"select_query": "SELECT Full_Name, Email FROM Leads WHERE id not in (SELECT Leads FROM Campaigns WHERE Campaign_Name = 'T01')"}
    where Leads is a lookup up field in the Campaigns module.

  • Identify Deals Closed Outside a Specific Campaign: Similarly, to find all Deals that closed outside the “Q1 Marketing Blitz” campaign window, you can use the NOT BETWEEN operator with subqueries.
    { "select_query": "SELECT Deal_Name, Created_Time FROM Deals WHERE Closing_Date not between (SELECT Start_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz') and (SELECT End_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz')"}

Key Benefits of Using Subqueries

  • Reduces API calls and Credit consumption – Instead of fetching related data in multiple queries, subqueries fetch it in one go.
  • Less Data Processing – No need to store and process results from one query before making another.
  • Improved Query Efficiency – Filters and retrieves only relevant records dynamically.
  • Simplifies Integration Code – Removes extra loops and logic required to handle multiple queries.

Limitations of Subqueries in COQL

While subqueries improve performance and efficiency, they come with certain limitations:

  • Subqueries can only be used in the WHERE clause. You cannot use subqueries in SELECT or FROM.
  • There can be a maximum of 5 subqueries per query.
  • Only one column can be selected in a subquery. You cannot fetch multiple fields from the subquery.
  • Limited to 100 records per subquery. If more records are needed, or there could be more than 100 possible records in the subquery, consider using JOINs.

Credit Consumption Considerations

Please note that using subqueries does not introduce any change in credit consumption compared to regular COQL queries. Credit usage is determined by the number of records retrieved in the main query.
The following table outlines the credit consumption based on the number of records retrieved:

LIMIT (No: of records)
API credits consumed
1 - 200
1
201 - 1000
2
1001 - 2000
3

Subqueries vs. JOINs

A JOIN clause in COQL lets you retrieve fields from two (or more) related modules in a single query by linking them on a lookup field—no nested queries needed. It’s ideal when you need columns from both modules, ie., the parent module and the related modules, in the same response.

For example, consider a scenario where it's necessary to query all accounts that have associated Deal records created within the past month.
—without getting duplicate Account rows if an Account closed multiple Deals.

Subquery Approach:

{  "select_query": "SELECT Account_Name FROM Accounts WHERE id in (SELECT Account_Name FROM Deals WHERE Created_Time >= '2025-03-01T00:00:00+05:30')"}

The subquery first selects Account_Name from Deals where the Created_Time is within the past month. Then the main query fetches the Account_Name from Accounts, once per matching account.

JOINs Approach:

{ "select_query": "SELECT 'Account_Name.Account_Name', 'Account_Name.id' FROM Deals WHERE Created_Time >= '2025-03-01T00:00:00+05:30'"}

This JOIN COQL query queries the Deals module and pulls related fields from the Account_Name lookup (Account name and ID) for each Deal created in the last month. As a result, it returns duplicate rows for accounts that have multiple matching deals.

Sample Response:

Subquery
JOIN
 {
    "data": [
        {
            "Account_Name": "Chapmans",
            "id": "4876876000004946070"
        },
        {
            "Account_Name": "Customer Daily",
            "id": "4876876000005030168"
        },
        {
            "Account_Name": "Luma Infotech",
            "id": "4876876000007420031"
        },
        {
            "Account_Name": "Luma Biotech",
            "id": "4876876000007481116"
        }
    ],
    "info": {
        "count": 4,
        "more_records": false
    }
}




{
    "data": [
        {
            "Account_Name.id": "4876876000007481116",
            "Account_Name.Account_Name": "Luma Biotech",
            "id": "4876876000010128001"
        },
        {
            "Account_Name.id": "4876876000007481116",
            "Account_Name.Account_Name": "Luma Biotech",
            "id": "4876876000010128016"
        },
        {
            "Account_Name.id": "4876876000007420031",
            "Account_Name.Account_Name": "Luma Infotech",
            "id": "4876876000010128047"
        },
        {
            "Account_Name.id": "4876876000005030168",
            "Account_Name.Account_Name": "Customer Daily",
            "id": "4876876000010193006"
        },
        {
            "Account_Name.id": "4876876000004946070",
            "Account_Name.Account_Name": "Chapmans",
            "id": "4876876000010213010"
        }
    ],
    "info": {
        "count": 5,
        "more_records": false
    }
}

Why Subqueries Are Better in This Case:

  • No Duplicates: Subqueries ensure that each matching parent (Account) appears only once, even if multiple child records (Deals) match. This is perfect for deduplicated reporting or dropdown lists.
  • Cleaner Result: Easier to parse and use directly in UIs or aggregations where duplicates are not useful.
  • Lower Payload Size: Especially useful if you just want the Account info and don’t need Deal-level detail.
Both subqueries and JOINs allow you to retrieve related data, but when should you use one over the other?

Use Subqueries When:

  • You need to filter data based on related module conditions.
  • You do not need to fetch fields from multiple modules. ie., you want to query the inner lookup fields only in the WHERE clause, and not in any other clause.
  • You need deduplicated parent records.
  • The subquery has 100 or less records.

Use JOINs When:

  • You need to retrieve fields from multiple related modules in the same response. ie., you want to query the inner lookup fields in any clause other than the WHERE clause.
  • You are dealing with large datasets exceeding the subquery limit of 100 records.
  • You need detail per child record, even if it leads to duplicate parent values.

Operator support for Subqueries in COQL

When using subqueries in COQL, make sure to use the correct operators depending on whether the subquery returns multiple values or a single value.

Multi-Value Operators

These operators are to be used with the subqueries that return multiple values, which are then used in the main query. 
Operator
Description
Example use case and query
in
Checks if a value is present in a list of values returned by the subquery.
Fetch all Contacts whose Accounts have won high-value deals.

{"select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won' AND Amount > 100000)"}
not in
Excludes records where the value is present in the subquery result.
Fetch all Contacts whose Accounts have never closed a deal.

{ "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name not in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won')"}

Single-Value Operators

These operators require the subquery to return a single value. If the subquery returns multiple values, an error will occur. 
Operator
Description
Example use case 
=
Matches records where the field is equal to the subquery’s result.
Fetch Deals created on the same date as the latest deal.
!=
Retrieves records where the field is not equal to the subquery’s result.
Fetch Deals not created on the same date as the latest deal.
<, >, <=, >=
Compares a field with the single value returned by the subquery.
Fetch all Deals that closed before the latest high-value deal.
between
Ensures a field's value falls within a range.
Fetch all Deals closed between two specific deal closure dates.
not between
Excludes records within the range.
Fetch all Deals closed outside a specific date range.

Example 1: Using the IN operator to fetch Contacts linked to high-value Deals

{ "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT Account_Name FROM Deals WHERE Amount > 100000 AND Stage = 'Closed Won')" }

Example 2: Using the NOT IN operator to fetch Contacts from Accounts that have never closed a Deal
{ "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name not in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won')"}

Example 3: Using the BETWEEN operator to identify Deals closed during a specific Campaign (Q1 Marketing Blitz)
{ "select_query": "SELECT Deal_Name, Created_Time FROM Deals WHERE Closing_Date between (SELECT Start_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz') and (SELECT End_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz')"}

Combine JOINs and Subqueries for Smarter Filtering

In many business scenarios, it is not enough to simply retrieve related fields via JOINs—you also need to dynamically filter data based on conditions from another module. This is where subqueries can be incredibly useful in conjunction with JOINs.

Let’s say you're analyzing deal performance and want to pull a list of Deals that are:
  • Associated with Active Campaigns
  • Linked to Accounts in high-revenue Industries (Annual Revenue > 10,000,000)
  • You need to fetch details from the related modules—like Account name, Campaign name, and Contact email—in the same query
Why this can't be solved easily: While COQL supports JOINs for pulling data from related modules and subqueries for dynamic filtering, you can’t do all of this in one approach alone.
  • JOINs allow you to retrieve fields from related modules (like Contact_Name.Email )—but they do not let you dynamically filter using fields from those modules.
  • Subqueries, on the other hand, allow you to filter based on fields from related modules (like filtering Deals based on the Annual Revenue of the associated Account)—but you can’t fetch fields from multiple related modules using just a subquery.
So, if you need to both filter based on fields in a related module (like Accounts.Annual_Revenue) and retrieve fields from related modules (like Contact_Name.Email, Campaign_Source.Campaign_Name), you need both tools.

Solution: Combine JOINs and Subqueries in the Same Query
{"select_query": "SELECT Deal_Name, Amount, Account_Name, Campaign_Source, Contact_Name.Email FROM Deals WHERE (Campaign_Source.Status = 'Active') AND Account_Name.Industry in (SELECT Industry FROM Accounts WHERE Annual_Revenue > 10000000 GROUP BY Industry)"}

This query:
  • Uses JOINs to fetch:
    • Contact_Name.Email – from Contacts
  • Uses a subquery to apply dynamic filtering on Deals based on the Industry of Accounts with Annual Revenue > 10000000. COQL subqueries return a maximum of 100 records. If multiple accounts satisfying the criteria share the same industry, using GROUP BY Industry ensures only unique industry values are returned. This helps stay within the 100-record limit and avoids redundant filtering.
In the results, you get a deduplicated, filter-accurate list of Deals tied to Active Campaigns and high-value industries—with rich contextual fields in one API call.

You can even use JOINs inside subqueries. For instance, to fetch all deals from Optical Networking accounts managed by Jane (jane.doe@zohotest.com), and include key details about the deal, contact, account, and campaign:
{ "select_query": "SELECT Deal_Name, Amount, Account_Name, Contact_Name.Email, Campaign_Source FROM Deals WHERE Account_Name in (SELECT id FROM Accounts WHERE Industry = 'Optical Networking' AND Owner.email = 'jane.doe@zohotest.com')"}

By combining JOINs and subqueries, you can handle more complex, real-world business requirements in a single query. JOINs help you enrich your data with fields from related modules, while subqueries let you apply smart, condition-based filters across modules. 

Advanced Filtering: Nested Subqueries

For more advanced use cases, you can nest subqueries within subqueries to create complex filtering conditions.
Let's say Imagine you need to identify all Contacts associated with Accounts that meet two specific criteria:
  • The Account is in the "Retail" industry.
  • The Account has at least one associated Deal that is in the "Closed Won" stage and has a value greater than $50,000.
This scenario is common in sales and marketing, where you want to target high-potential customers within a specific industry. Here's how you can achieve this using a nested subquery in COQL:
{
  "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT id FROM Accounts WHERE Industry = 'Communications' AND id in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won' AND Amount > 50000))"
}
Innermost Subquery: (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won' AND Amount > 50000)
This subquery identifies all Account_Name values from the Deals module where the Stage is "Closed Won" and the Amount is greater than $50,000. Although the field name is Account_Name, it's a lookup to the Accounts module, so it returns the Account ID. This effectively isolates Accounts that have closed high-value deals.

Middle Subquery: (SELECT id FROM Accounts WHERE Industry = 'Retail' AND id IN (...))
This filters Accounts by the "Retail" industry and ensures that only those whose ID appears in the innermost subquery are selected.

Main Query: SELECT Full_Name, Email FROM Contacts WHERE Account_Name IN (...)
Finally, the main query retrieves the Full_Name and Email of all Contacts whose Account_Name matches the id values returned by the middle subquery.

Info
Note: COQL supports a maximum subquery nesting depth of 5, and you can include up to 5 subqueries total within a single query. The nesting limit refers to subqueries embedded within the WHERE clause of another subquery. 
Subqueries in COQL are a game-changer for developers looking to build efficient, context-aware queries across modules—allowing dynamic filtering that was previously only possible with multiple API calls. While JOINs help you fetch rich, multi-module data in a single response, subqueries let you filter records based on conditions from related modules. And when you combine the two, you unlock a powerful mechanism to tackle real-world CRM business cases with precision and clarity.

For advanced use cases, don’t hesitate to nest subqueries—COQL allows up to five levels deep—giving you the flexibility to build truly nuanced filters. Mastering the balance between JOINs and subqueries is key to writing smarter, cleaner, and more performant queries.

We hope you found this guide useful in understanding and implementing COQL subqueries. If you have any questions or require further clarification, please don't hesitate to leave a comment below or reach out to us directly at support@zohocrm.com. 

Keep experimenting, and as always, happy querying!






      • Sticky Posts

      • Kaizen #197: Frequently Asked Questions on GraphQL APIs

        🎊 Nearing 200th Kaizen Post – We want to hear from you! Do you have any questions, suggestions, or topics you would like us to cover in future posts? Your insights and suggestions help us shape future content and make this series better for everyone.

      • Kaizen #198: Using Client Script for Custom Validation in Blueprint

        Nearing 200th Kaizen Post – 1 More to the Big Two-Oh-Oh! Do you have any questions, suggestions, or topics you would like us to cover in future posts? Your insights and suggestions help us shape future content and make this series better for everyone.

      • Celebrating 200 posts of Kaizen! Share your ideas for the milestone post

        Hello Developers, We launched the Kaizen series in 2019 to share helpful content to support your Zoho CRM development journey. Staying true to its spirit—Kaizen Series: Continuous Improvement for Developer Experience—we've shared everything from FAQs

      • Kaizen #193: Creating different fields in Zoho CRM through API

        🎊 Nearing 200th Kaizen Post – We want to hear from you! Do you have any questions, suggestions, or topics you would like us to cover in future posts? Your insights and suggestions help us shape future content and make this series better for everyone.

      • Client Script | Update - Introducing Commands in Client Script!

        Have you ever wished you could trigger Client Script from contexts other than just the supported pages and events? Have you ever wanted to leverage the advantage of Client Script at your finger tip? Discover the power of Client Script - Commands! Commands

        • Recent Topics

        • Zoho fsm scheduled maintenance dispatch

          Hi, I'm reaching out regarding an issue I'm encountering with the Scheduled Maintenance feature in Zoho FSM. I’m trying to configure it so that it automatically dispatches all maintenance jobs scheduled within the next 150 days, starting from today. However,

        • zoho.inventory.getRecords returns no records

          I running a custom function (Deluge) in Zoho Flow with a connection to Zoho Inventory. To debug the problem, I created the test function below. It returns "Number of contacts fetched: 0". This confirms that there's no issue with the org ID or connection

        • Zoho Campaigns Event timestamps do not propagate to Zoho CRM

          We have integrated Zoho CRM and Zoho Campaigns. But when looking at Contact records, the Campaign event data is missing the actual timestamps: especially when a particular email was sent. They're not in the Campaigns related list, and the cannot be found

        • Feature announcement - Simplifying document creation with Zoho Sign

          Hi there, We are pleased to announce the release of our document creation feature, enabling you to create, edit, and finalize documents like agreements, purchase orders, and contracts without relying on external tools or applications. &lt;br&gt; This

        • Integrating File Attachments in Zoho Flow Email Notifications

          Hi, I would like to be able to send an email once an entry is made in a form, and in this email, I would like to attach a file that has been added to the form using the ImageUpload (or FileUpload) widget. So, I started by creating a flow that will trigger

        • Zoho project purchases

          Hi Folks, I think having a purchase module in projects will help in putting together a project p and L. Project wise purchases and expenses.  Do let me know your thoughts.

        • Create Tasklist with Tasklist Template using API v3

          In the old API, we could mention the parameter 'task_template_id' when creating a tasklist via API to apply a tasklist template: https://www.zoho.com/projects/help/rest-api/tasklists-api.html#create-tasklist In API v3 there does not seem to be a way to

        • How can I restore all the deleted Time entries of a Task in Zoho Projects

          How can I restore all the deleted Time entries of a Task in Zoho Projects? Query: In Zoho Projects, I cloned a task and deleted the time entries from the cloned task. However, this also deleted the time entries from the original task. How can I restore

        • Is there a way to make an account inactive in ZoHo Desk

          We have a few Clients "Accounts" that we no longer do business with. It would be beneficial for them to not show up in lists. However, we want to go back and view tickets, time, etc.

        • How to set the value of the Phone field importing contacts in Zoho Desk

          Hi everyone, i'm new in Zoho Desk, we're setting up the environment and i'm importing contacts from another CRM using a file CSV and i'm getting a problem with phone numbers (italian): the leading zero is cut away, also if the value is inside double quotes.

        • Set Custom Icon for Custom Modules in new Zoho CRM UI

        • Deprecation Notice: OpenAI Assistants API will be shut down on August 26, 2026

          I recieved this email from openAI what does it means for us that are using the integration and what should we do? Earlier this year, we shared our plan to deprecate the Assistants API once the Responses API reached feature parity. With the launch of Conversations,

        • How to center a field inside a section?

          I’ve been trying to center a field inside a section in Zoho Canvas. When I align it visually, it looks centered in the editor, but after clicking Save, the field appears misaligned on the actual canvas. I also tried setting the field to full width, but

        • Kaizen #192 - Implementing Custom Token Persistence in Python SDK

          Welcome back to another week of Kaizen! Last week, we discussed how to implement Login with Zoho using OAuth 2.0 and saw how to bring it to life in a real-world application with the Zoho CRM Python SDK. We also discussed how Zylker Academy built a custom

        • Showing the map along with mileage expense

          When you use the GPS to track mileage, it shows you the map of the actual path travelled. It would be very useful and practical to save that map with the mileage expense, so that when the report is created, it provides a map of each mileage expense associated

        • Enable Validation Rule for Multi-Select Picklist Field

          Zoho, Please allow validation rules for multi-select fields.

        • File Upload field not showing in workflow

          Hi, I have added a field on Zoho CRM. I want to use it in a workflow where that particular field is updated based on another field, however it is not showing up in the field list to select it in the workflow. Why is this please?

        • CRM Custom function updating a module record shows the Super Admin user as the record modifier

          Dear Zoho CRM Team, Is there any way to update this so that when a custom function has updated a record the Super Admin user doesn't become the modifier? This happens on the record as a modifier and shows up in the audit logs. It would be more useful

        • Best practice importing items and matching assemblies

          Hi, I was wondering what would be the best practice to import items and composite items (assemblies) From my backup, what should I import first? The items or the composite items? I am on Zoho one, using inventory and books. Kind regards, Sabine

        • Best way to fetch employee names from Zoho People into Zoho Creator Inventory Stock Form field Employee Name Lookup

          Hi Team, I have a requirement in my Zoho Creator application (Inventory Stock Adjustment) where I need to fetch employee names from Zoho People and use them as a lookup in a form. Currently, I am considering using an integration field to fetch this data

        • get file api is returning Junk data

          I am working on extension development where at one point I need to retrieve attachments on records I found out I can use only invokeconnection and not invokeurl in extension development The invoke connection returns the image in raw binary format. When

        • Need help with message box

          End user updates many records at once. Each have unique serial number. They want a confirmation box that says starting number, ending number and qty. Is there any way to do this? I been searching and asking support but seems like no great solution.

        • [Webinar] The Transformative Power of Gen BI

          Traditional decision-making tools are no longer enough. The integration of generative AI into business intelligence (BI) is proving to be a true game changer—enabling businesses to make faster, smarter, and better informed decisions. Early adopters of

        • Backorder process review - Automating Removal of Sales Order from "On Hold" When PO is Received

          Hello Zoho Inventory Team, Currently, sales orders in On Hold status are released only when the bill for the purchase order is created. In our workflow, it would be much more efficient if the sales order could automatically move out of On Hold as soon

        • How to access the saved Query using API?

          I have created a query in setting. Is it possible to access it from a API? What's the endpoint? I tried /v8/queries/important_deals but didnt' work.

        • création d'une base de données

          base de donnee d'un lycée

        • User Session variables to recall after form submit & redirect to menu

          Hey, Forgive me if this is a simple answer I have overlooked. I have built a big onboarding process for my SAAS platform which is built and managed by an external Dev team. I am hoping to embed my new creator app on the SAAS platform. I have a menu page

        • Zoho Writer Merge Template with data from Zoho Analytics Views

          Hello, Is there any way to pull information from Zoho Analytics and put it into a Merge Template? I am trying to create a bulk export of one report that filters on a field to create a single document for each of the filter fields.

        • Having to enter bill before stock shows as available.

          Hi, Am I right in thinking you must create a bill from the purchase order receipt before the goods are available for shipping?

        • Agent Availability Report

          From data to decisions: A deep dive into ticketing system reports Businesses need to track when their support agents check in and check out from work. This report, titled Agent Availability, is one of the static reports that helps managers track the number

        • Writing by Hand in "Write" Notes

          Hi there! I just downloaded this app a few moments ago, and I was wondering if there was a way to write things by hand in "Write" mode instead of just typing in the keyboard. It would make things a bit more efficient for me in this moment. Thanks!

        • AI-driven construction analytics using Zoho Projects Plus

          Construction projects thrive on timelines; if a project is completed on or before the expected time, it makes headlines, but if it gets delayed, the company’s credibility will be at risk. Such projects require precise planning and constant monitoring,

        • Canadian payroll

          Hello ZOHO, is any updates on when payroll for Canada will be available?

        • Unified customer view: Bringing product intelligence into your CRM data

          For businesses today, applications and digital interfaces are the main touch points in the customer journey. While Zoho CRM data already tells who your customers are and what they buy, Zoho Apptics tells you how they interact and engage with your product.

        • Zoho Creator SaaS app with multiple client AND multiple users

          I am close to finalizing a Zoho Creator app that will be used by different companies to manage sale info, and each company can have multiple users using the app. Things were going perfectly until I tried a search on a report. I use a database field in each table to separate the data for each company, which works great. BUT when I do a search, I get to see ALL the data. This means that Company A could easily see the data from Companies B and C via the built-in search. Is there a way to set up the

        • Project Change Orders and Additions

          We are in the process of migrating from QuickBooks Online to Zoho Books. We have Zoho One and like the ability to sync all of our data across everything. And I like that projects work in a way that's less dumb than QuickBooks. I'm trying to figure out

        • Track online, in-office, and client location meetings separately with the new meeting venue option

          Hello everyone! We’re excited to announce meeting enhancements in Zoho CRM that bring more clarity and structure to how meetings are categorized. You can now specify the meeting venue to clearly indicate whether a meeting is being held online, at the

        • Create custom rollup summary fields in Zoho CRM

          Hello everyone, In Zoho CRM, rollup summary fields have been essential tools for summarizing data across related records and enabling users to gain quick insights without having to jump across modules. Previously, only predefined summary functions were

        • Possible to send Zoom AI Companion transcripts and summaries to contacts in CRM?

          Title says it all. Is it possible to send Zoom AI Companion transcripts and summaries to contacts in Zoho CRM?

        • How do I edit the Calendar Invite notifications for Interviews in Recruit?

          I'm setting up the Zoho Recruit Interview Calendar system but there's some notifications I don't have any control over. I've turned off all Workflows and Automations related to the Calendar Scheduling and it seems that it's the notification that is sent

        • Next Page