Relationship Fields
Relationship fields are used to connect records between different CRM modules.
They allow the system to link related data so that users can easily view, navigate, and manage connected information across modules.
For example:
- A Ticket can be linked to a Contact
- A Lead can be converted into a Contact and Opportunity
- A Service Request can be connected to a Customer and an Asset
This structure helps organizations track business processes, maintain data consistency, and improve reporting accuracy.
Important System Limitation
When creating relationships with system modules, the One-to-Many relationship type may not always be available.
This limitation occurs particularly with User and Group modules.
Users cannot create One-to-Many relationships directly with these modules because:
- These modules are part of system-level access control
- They are designed for assignment and permission management
- Relationships are handled internally by the system
Instead, these modules use predefined lookup or assignment relationships.
Example:
Ticket → Assigned Agent → User
Types of Relationships
When configuring module relationships, the system allows four relationship types.
1. One-to-One Relationship
A One-to-One relationship means one record in Module A can be connected to only one record in Module B.
Example Structure
Passenger → Passport
1 Passenger → 1 Passport
Example Scenario
In an Airline CRM system, each passenger may have one frequent flyer account.
Relationship:
Contacts ↔ Loyalty Account
Example
| Contact | Loyalty Account |
|---|---|
| John Silva | FF-98345 |
| Maria Gomez | FF-88432 |
Each passenger has only one loyalty account, and each loyalty account belongs to only one passenger.
2. One-to-Many Relationship
A One-to-Many relationship means one record in Module A can be linked to multiple records in Module B.
Structure
1 Parent → Many Child Records
Example Scenario
In an Airline Customer Support system, a single passenger can create multiple support tickets.
Relationship
Contact → Tickets
Example
| Contact | Tickets |
|---|---|
| John Silva | Ticket 1001 |
| John Silva | Ticket 1002 |
| John Silva | Ticket 1003 |
Here:
- One Contact
- Multiple Tickets
This allows the airline to track all service requests from the same passenger.
3. Many-to-One Relationship
A Many-to-One relationship is the reverse of One-to-Many.
Multiple records in Module A connect to one record in Module B.
Structure
Many Child Records → 1 Parent
Example Scenario
In a Real Estate CRM system, many property opportunities can belong to one customer.
Relationship
Opportunities → Contact
Example
| Opportunity | Contact |
|---|---|
| Apartment Purchase | John Silva |
| Villa Purchase | John Silva |
| Land Investment | John Silva |
Here:
- Many Opportunities
- One Customer
This helps sales teams track multiple deals from the same buyer.
4. Many-to-Many Relationship
A Many-to-Many relationship allows multiple records in both modules to be connected.
Structure
Many A ↔ Many B
Example Scenario
In an Elevator Maintenance system, a technician may work on multiple service requests, and a service request may involve multiple technicians.
Relationship
Technicians ↔ Service Requests
Example
| Technician | Service Request |
|---|---|
| Alex | Elevator Repair |
| Alex | Maintenance Visit |
| John | Elevator Repair |
This allows organizations to manage collaborative work environments.
Relationship Validation Preview
After selecting a relationship type, the system displays a relationship explanation preview.
This preview explains:
- Which module is the parent
- Which module is the child
- How records will be connected
- What data will appear in related record views
Example preview message:
“Each Contact can have multiple Tickets, but each Ticket will belong to only one Contact.”
This validation helps users confirm the relationship logic before saving the configuration.
How to Configure Relationships
Follow these steps to create relationships between modules.
Step 1 – Open Module Configuration
Navigate to:
Settings → CRM Configuration → Modules
Step 2 – Select the Primary Module
Choose the module where the relationship will be created.
Example:
Tickets Module
Step 3 – Add Relationship Field
Click:
Add Field → Relationship Field
Step 4 – Select Target Module
Choose the module you want to connect.
Example:
Contacts
Organizations
Assets
Customers
Leads
Opportunities
Step 5 – Select Relationship Type
Choose one of the following:
- One-to-One
- One-to-Many
- Many-to-One
- Many-to-Many
Step 6 – Review Relationship Preview
The system will display a clear explanation of how the relationship will function.
Example:
One Contact can be linked to multiple Tickets.
Each Ticket will belong to one Contact.
Confirm that this matches your business process.
Step 7 – Save Configuration
Click:
Save
The relationship will now appear in both modules.
Configuration Using Business Case Examples
Below are the correct relationship configurations based on the sample business scenarios.
Benefits of Using Relationships
Using relationships in CRM provides several advantages that help organizations manage data more effectively and improve business operations.
1. 360° Customer View
A relationship between modules allows users to see all related customer information in a single location.
For example, when a user opens a Contact record, they can immediately view the related Organization, Tickets, Leads, Opportunities, calls, or activities connected to that contact. This eliminates the need to manually search across multiple modules.
This unified view helps support agents, sales teams, and managers quickly understand the full history of interactions with a customer, including purchases, support requests, and communication records.
As a result, teams can provide faster responses and better customer service.
2. Better Data Organization
Relationships ensure that data is structured and logically connected across modules instead of being stored as isolated records.
For instance:
- An Organization can be linked to multiple Contacts.
- A Contact can be linked to multiple Tickets.
- A Lead can later be converted and connected to an Organization and Contact.
By organizing data this way, the CRM prevents data duplication and maintains clean and structured records.
It also makes it easier for users to understand how different pieces of information relate to each other.
3. Improved Reporting
Relationships enable managers and analysts to generate more powerful reports and insights by combining data from multiple modules.
For example:
- A manager can analyze how many tickets were raised by contacts from a specific organization.
- Sales teams can track how many leads converted into opportunities for a particular company.
- Management can measure customer engagement, support performance, and sales results using connected data.
Because the modules are linked through relationships, the CRM system can produce cross-module analytics and dashboards, helping organizations make data-driven decisions.
4. Process Automation
Relationships also enable automation and workflow triggers based on related records.
For example:
- When a Ticket is created for a Contact, the system can automatically notify the assigned account manager of the related organization.
- If a Lead is converted, the CRM can automatically create a related Contact and Organization record.
- When a high-priority ticket is created for a VIP organization, the system can trigger an SLA workflow or escalation process.
By using relationships, the CRM can automate complex business processes and ensure that actions are triggered based on related data. This improves operational efficiency and reduces manual work.