|
Notification type
|
Alert on
|
|
Untouched records created in the last 7 days
|
Percentage of records created in the Leads and Contacts modules that have not been modified for at least 7 days.
|
|
Records created in the last 7 days without email follow-up |
Percentage of records in the Leads or Contacts modules created in the last 7 days that were not sent a follow-up email.
|
|
Anomaly in the number of records touched after modifying a workflow rule
|
Increase or decrease in the number of records that have been modified after the workflow configuration is
changed.
|
|
Anomaly in email open rate after modifying a workflow rule
|
Increase or decrease in the email open rate 2 days after a workflow is modified.
|
|
Top performing workflow rule template by open rate in last 7 days
|
The email template (associated with a workflow rule) that has the highest open rate in the last 7 days.
*compared with the other templates associated with the same workflow rule.
|
|
Same template sent to the same Lead or Contact on the same day
|
Anomaly alert when a lead or contact is sent the same email template twice on the same day.
|
|
Same Lead or Contact receiving more than one template on the same day
|
Anomaly alert when a lead or contact is sent more than one template on the same day.
|
|
Notification type
|
Alert on
|
|
Anomaly in Lead Creation
|
An increase or decrease in the number of leads created.
For example: If 10 leads are created everyday and one day less than 10 leads are created.
|
|
Anomaly in Deal Closure Amount
|
Anomaly alert if the deal amount is less than the usual amount.
Alert: Notifies the percentage of the abnormality found in the amount when closing a deal.
Example: If a user usually closes $100 of deals in a week, but no deals are closed by the user one week, this is considered as a anomaly and a notification is triggered.
|
|
Anomaly in Task Closure
|
Increase or decrease in the number of tasks closed.
Example: If all users close 100 tasks per week, and then one week only 50 tasks are completed, this is considered as an anomaly and Zia notification is triggered.
|
|
Anomaly in sales cycle
|
Sudden increase or decrease in the momentum of the sales cycle is recorded as anomaly in sales cycle.
Example: If all real estate deals are observed to close in 3 months, and for some unforeseeable circumstances if the deal drags beyond 6 months this is recorded as anomaly triggering notifications to the admins and managers to investigate the lag.
|
|
Anomaly in lead conversion
|
Converting a lead usually goes through a set of process and if there is a digression in the process then the same will be observed as anomaly and will be notified to the admins and the managers.
For example: If a lead is acquired and is idle for a long time, then this is considered as a process anomaly and notifications are trigerred.
|
Click here to know more information about the latest browsers supported in Zoho CRM
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.
All-in-one knowledge management and training platform for your employees and customers.
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.