When we talk about custom modules within Zoho Desk, we're taking this concept a step further. Custom modules in Zoho Desk play a crucial role in how businesses organize and manage their data. These modules are far from generic placeholders; they're more specialized and industry-specific designed to meet the unique needs of different businesses.
From a business perspective, these custom modules are like tailored compartments for your data. They allow you to store information in a manner that is not only relevant but also easily comprehensible to your workforce. Instead of dealing with generic data structures that may not align with your industry's unique challenges, custom modules empower you to create customized data repositories that precisely mirror your business processes.
Imagine having modules designed specifically for your industry, whether you're in healthcare, ecommerce, finance, or any other sector. These custom modules enable you to capture, organize, and retrieve data in a way that makes sense to your team. This tailored approach enhances not only your customer support, but also your overall operational efficiency.
Zoho Desk provides a range of system-defined standard modules, such as Tickets, Accounts, Contacts, Products, Tasks, and more, to store specific data. These modules come with a set of default fields and layouts that can be easily customized by Admins or Agents to align with the unique requirements of a business. For example, the Classifications field in the Tickets module can be renamed as "Ticket type" to make it relatable to the support agents. See also: Standard Zoho Desk modules and fields
At times, standard modules may not meet every business needs in such cases, custom modules can help businesses address their precise requirements. For example, modules like Customers, Products, or Knowledge Base may not be appropriate in the Education sector. They can create custom modules such as "Students," "Professors," and "Counselors" that will align with their operational processes.
Likewise, an insurance firm may require a standalone module to keep records of the policies and also link it with the customers to get a 360 degree view.
These custom modules can integrate seamlessly with core Desk modules using lookup fields and need not be stand-alone modules. In addition to this, custom modules provide several other benefits, such as field customization, creating workflow automations, defining the access controls, and more.
Consider a tourism business that uses Zoho Desk to manage bookings and ticketing system. They create the following custom modules to store data and customer information:
They have also configured the following to optimize the module for their business requirements:
In each module, they have added custom fields to store relevant data.
The company facilitates hotel and travel bookings, so they created two layouts under the Bookings module to capture the relevant details.
Since different teams handle tour packages, reservations, and bookings, instead of giving everyone access to all the modules, admins can give restrict access to the relevant members. Likewise, customer information and transaction details should only be accessible to authorized users, so users with the appropriate profile permissions can be given access to view and edit data within these modules.
To streamline processes further and ensure smooth operations, they implement workflow rules in the custom modules. For example, when the number of available seats for a tour package reaches a specific threshold, an automated notification can be sent to the sales team or respective agents, prompting them to take appropriate action or update the availability status promptly.
For streamlined communication, the reservation status and booking details are sent to the customers via email and SMS. Additionally, administrators can create custom reports to keep track of reservations and bookings and get relevant insights.=
Custom module is available in the following editions:
Zoho Desk administrators can create and configure custom modules. Creating custom modules involves the following steps:
Department-level data storage | Organization-level data storage | |
When to use? | When multiple departments need similar custom modules but store different datasets. For eg., In Bookings module:
| At the organizational level data storage, If the records are shared throughout the entire organization, selecting organization-level data storage is the appropriate choice. |
Why to use? | Instead of creating separate modules in each department that store similar datasets, a single module with relevant fields can be created. For eg, Vendors module having different vendors in dept A and B. | Records or datasets of a single module are relevant and common across the organization. For eg., employee details. |
No.of layouts | A separate standard layout of the custom module is created in each department. Let's say you have a custom module called "Projects" that is accessible to multiple departments within your organization. Each department has different requirements for the information they need to track and display in the Projects module. Hence, separate layout will be used for different departments. | Common standard layout is created across departments. In a "Tour Packages" custom module, a common set of records is stored and is reflected across the organization. Hence one standard layout will be used. |
Fields | Standard fields in the custom module will be available in the layout of all departments. Admins can create and customize fields as per their requirement. | Both system and custom field will be available in the layout of all departments. Admins can create and customize fields as per their requirement. |
Record Visibility | Records will be different for each department. | Records added to the custom module will be visible and accessible to all departments. It implies that the records are accessible to all departments, but it does not necessarily mean they will be shared as read-only. Whether the records can be edited by users from different departments depends on the specific access control settings and permissions configured in the system. |
Admins can perform various actions in addition to creating and editing custom modules. These actions include:
Once a custom module is created, it can be accessed from the top band on the Zoho Desk account.
The are two system-defined views in the custom module that allow the users to easily access the records they want.
Users can customize the list view by adding or removing columns.
Admins can set access permission for specific fields. For example, policy number can be made accessible to only select insurance agents. Likewise, admins can establish field dependencies, where certain fields rely on others. For example, when selecting a "Country," only the relevant "State" options are displayed. See also: Creating field dependencies and setting field permission.
Lookup fields can be added to the layouts to create a link between modules. This will allow admins or agents to establish a relationship between standard-custom and custom-custom modules.
For example, Tour Packages can be linked with the standard module Tickets. This will allow the travel agents to access and view the record from either modules. To establish such a relationship, admins can create a custom lookup field in the Tickets layout.
Once a lookup field is added, a subtab is automatically created in the linked module providing a 360 degree view of the related records. For example, while creating a lookup field a related subtab called Related Tickets can be created. This subtab will be displayed in the Tour packages module.
From the subtab users can:
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.