Notes & History Tab

The CRM's "Notes and History" tab serves as a repository for capturing and tracking interactions, communications, and activities related to individual contacts, leads, or accounts.
​

This section allows users to store notes. These notes could include information about meetings, phone conversations, important details, or any relevant observations. Notes provide a way to capture essential information about interactions that may not be directly tied to specific dates or activities.

Columns organize it:

In each note, there is a Three dots icon menu with the options Details, Alert, and Remove.
​
​

​

Emails

This refers to a record of past email communications associated with a specific App. These emails are logged within the CRM platform to create a comprehensive history of interactions, providing users with insights into past conversations.

It's organized by columns:

In each email, there is an option for details where it is possible to find email details: From, to, subject, and body.

​
​

SMS refers to the collection and recording of past text messages exchanged between users and Apps.

This SMS history is logged within the CRM to create a comprehensive record of text message communications, offering insights into past conversations and engagements.
​

It's organized by columns:

Calls history refers to the collection of past phone calls made between Users an apps. This calls history is logged within the CRM to create a comprehensive record of phone call interactions, offering insights into previous conversations.

It's organized by columns:

You can also filter by From, to, and the button Refresh.

Refers to the collection and recording of past sign requests and signatures exchanged between users and Apps. This sign requests history is logged within the CRM to create a comprehensive record of document signing interactions, providing insights into previous signing activities.
​

It's organized by columns:

This refers to the detailed records or entries generated whenever specific triggers or events occur within the CRM. These logs serve several purposes, including tracking system activities, monitoring user actions, and troubleshooting issues.
​

It's organized by columns:

Refers to records or entries created to track the activity and status of webhook events. Webhooks are mechanisms that enable real-time communication between the CRM system and external applications or services.
​

Webhook logs play a critical role in monitoring and troubleshooting webhook interactions.
​

It's organized by columns:

This is a record of all the changes and movements of Apps through the various stages of the business development pipeline. This historical data provides valuable insights into the progression of activities and helps teams understand the evolution of customer interactions.

It's organized by columns:

This is a chronological record of all changes related to the assignment of leads/Apps to specific users or teams within the CRM platform.

This log helps track ownership, responsibilities, and the distribution of work.
​
​

It's organized by columns:

This documents the entire history and outcomes of underwriting. It also displays the results of each underwriting profile and individual underwriting policies.

It's organized by columns:

This logs the sequence of statuses that an App has gone through. It provides with the precise date and time when each action took place, who initiated this action, the specific category of the action, and the transition from one status to another.
​
​It's organized by columns:

This feature provides a comprehensive view of the app’s historical records, highlighting each milestone as it is achieved. It includes detailed time data, specifying the exact moments when each milestone was reached. This allows users to track the app’s progress over time with precision.

​It's organized by columns:
​

This feature displays a historical log of all field modifications within each tab. It provides detailed information, including the initial input and updates. Furthermore, it records the precise time of each modification and identifies the user responsible for the change.
​
​​
​