Analyze a sharp change in the indicator

CRM suddenly has fewer closed applications. This can mean a change in demand, a delay in synchronization, or just one group of records that the manager moved to the next day. Zoho Zia helps to notice a deviation in the data and start parsing. The CRM also describes predictions of individual fields and other clues. The availability of functions varies by edition.

The value of such a signal is that it tells you where to look. The team looks for the cause in the original records and its own processes.

Start with the period and composition of records

For a training example, take one indicator, for example, the number of applications with the next step assigned. Compare the cards with the previous period. Mark new applications, status changes and records that previously fell into the report under a different rule. If the deviation started after the field change, first check the filter and completeness of the data.

When using the field forecast, it is useful to parse a few entries that have received different Zia scores. See if they have any clear differences in history. If the data was not loaded evenly, add this to the analysis results.

What is available in the work base

Check which features of Zia are included in your edition and who sees the necessary modules. To resolve the process, confirm the signal with a normal report. Separately write down what actions really explain the change and leave the rest of the versions open until the next check.

Suitable tasks

Verify CRM Deviation
Verify forecast with records

Features

Strengths

Signals are generated within CRM
There are different analytical functions

Things to consider

Limitations

Forecast depends on the quality of records
The composition of the functions changes according to the editors

Selection and conditions

Free access: Not confirmed
Trial period: Not confirmed
No sign-up required: Not confirmed
Russian interface: Not confirmed
Local installation: Not confirmed
API: Not confirmed

“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.

Input formats: Data
Result: Data, Text

Terms

Check the signal for the original CRM records and use the available edition.

From task to first result

Practical example

Task: Verify CRM Deviation
What to prepare: Comparable periods in the CRM training base and recording with a sharp change in the indicator.

Task brief or prompt

Open the deflection signal. Compare incoming entries, status changes and filter rules. Find the point from which the indicator has changed.

Expected result

Proven reasons for the change or a list of working versions indicating the original records.

How to check the result

Check the data in both periods.
Separate the technical change of the report from the process change.

An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.

Check details

Official sources

This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.

Zoho Zia.