---
title: Signals
slug: signals
description: Enable Signals to alert CSMs when customer behavior shifts, set per-segment thresholds, and use signal counts in segments, health scores, and metrics.
createdAt: 2024-08-01T10:34:12.380Z
---

Signals empower you to create notifications driven by customer interactions, enabling you to proactively monitor shifts in customer behavior and gain insights into trends and behavioral patterns. Select the critical events that should trigger notifications and ensure that your CSMs stay informed of any changes without the need for manual checks on metrics or health scores.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-RayGsd9YyRCqyt5ZGb6kf-20240801-140206.png)

Signals can be easily enabled under *Settings – Signals*. This setup is a one-time process. Once activated and configured, notifications will be triggered for CSMs assigned to the accounts. Additionally, new attributes for the number of *bad/good/open/closed signals* will be generated, allowing their use in segmentation, filtering, and other metric analyses.

## How to enable Signals

1. Go to *Settings – Signals.&#x20;*&#x59;ou will find the full list of events sent to your account.&#x20;
2. Think about the events that are the most relevant for customers’ health. Activate notifications for these specific events.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-OEZDVEVt8XFIbNKPg-8QB-20240801-140256.png)

3\. Choose the *Timeframe and Threshold.*

The *Timeframe* indicates the duration of the trend in days. This feature compares the current selected interval with the precedent one, allowing you to specify the length of that interval.

The *Threshold* represents the percentage of decrease or increase that, when exceeded, will prompt a notification.&#x20;

E.g. Consider the *Course\_started* and *Course\_completed&#x20;*&#x65;vents as crucial indicators of customer health. A decrease in event generation or a halt in interactions with the courses might indicate a churn risk, prompting the need for your Customer Success team’s awareness and outreach to these customers. Similarly, increased activity, signified by a higher volume of events, could present opportunities for upselling or engaging customers in advocacy programs.

In this scenario, you’ll activate notifications for the *Course\_started* and *Course\_completed* events, and you’ll select the *Timeframe* and *Threshold*. For instance, setting the *Timeframe* to 7 days and the *Threshold* to 15%. This configuration means that a notificatio&#x6E;**&#x20;will be triggered if customer activity either increased or decreased by more than 15% within the last 7 days, compared to the preceding 7-day period.&#x20;**

Observation! The default *Timeframe* is set to 7 days and the *Threshold* to 15. The *Timeframe* can range from 7 to 30 days, allowing for the largest trend window of 30 days compared to the preceding 30 days. The *Threshold* accepts values from 1 to 100, representing the percentage increase or decrease.

## How to use Signals

After enabling and configuring *Signals*, CSMs can choose to receive notifications for the *Signals* triggered. These notifications will be displayed in-app, or additionally, in case a CSM does not check the in-app notification, an email will be generated and sent to the CSM’s email address.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-RbmI4bGLhnH3ZP5dF60kS-20240801-142310.png)

For each company in Custify, four new default attributes will be created:&#x20;

- **Bad closed signals:&#x20;**&#x73;hows the total number of bad signals that were acknowledged by the CSM.
- **Bad open signals:&#x20;**&#x73;hows the total number of bad signals that were not acknowledged yet by the CSM.
- **Good closed signals:&#x20;**&#x73;hows the total number of good signals that were acknowledged by the CSM.
- **Good open signals:&#x20;**&#x73;hows the total number of good signals that were not acknowledged yet by the CSM.

Where:

- **Bad:&#x20;**&#x41; signal that is showing decreased activity.
- **Good:&#x20;**&#x41; signal that is showing increased activity.
- **Open:&#x20;**&#x41; signal that was not acknowledged by the CSM.
- **Closed:&#x20;**&#x41; signal that was acknowledged by the CSM.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-5yP8IEVph3Z63QDEz2vSw-20240801-142343.png)

A signal can be acknowledged either from the Customer List View or the Customer 360 Profile. Click on the *Signals* list, check the signal’s details, then click *Acknowledge*.&#x20;

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-aYjg2KV7W8R1JYYVifVEL-20240801-142411.png)

Before acknowledging the signal, a prompt requesting an acknowledgement reason will pop up. This ensures that everyone is aware of the actions taken in response to that specific signal.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-VTf-U-jhWjXtIWIKCUTwM-20240801-142439.png)

Closed signals can also be reopened. This allows the reopening of a signal in case it was closed mistakenly or if a change in decision regarding the action taken occurs.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU--5yY5cqWMk-YjEAXPO2g6-20240801-142510.png)

:::hint{type="warning"}
Observation! Closed signals cannot be deleted, so the number of bad/good closed signals will never decrease, they will always store the total number of bad/good signals that were ever generated.
:::

When going back to *Settings – Signals* and edit the logic for a Signal, the ones that were already opened remain unchanged. The new logic that you set will only apply for new *Signals*.

Before acknowledging/reopening signals, CSMs can look at the signal’s details by checking the *Observation timeframe* and the *Decision timeframe*.

- **Observation timeframe:&#x20;**&#x74;his represents the previous interval used for comparison with the current interval, enabling the observation of past behaviour.
- **Decision timeframe:&#x20;**&#x74;his signifies the current interval, displaying activity within the present timeframe.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-ypZgBMW6tX1lrGmeVqumX-20240801-142546.png)

To effectively manage signals, CSMs can filter and sort the complete list of signals for each company. The filters can be by *Type (Bad/Good), Acknowledgement (Open/Closed).&#x20;*&#x54;he sorting available is by *Event&#x20;*(alphabetically by event name)*, Status&#x20;*(Good/Bad), *Type&#x20;*(Open/Closed),*&#x20;Date&#x20;*(oldest to newest).&#x20;

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-2-Q46ERlk6wSxRLI8PPlL-20240801-142618.png)

### Per-segment Signal thresholds

**Signal** thresholds can be set per Segment. The same Signal can fire at different thresholds for SMB and Enterprise segments without duplicating the underlying signal definition.



![](https://api.archbee.com/api/optimize/16HhozMLfMR_uwZBLzFrU/-2nXgINPz8IWTJlH7S8gj_.blob)

## How to leverage Signals

In addition to generating notifications based on product usage and establishing new attributes for customer health, *Signals* can be used across various parts of the app, allowing you to construct new workflows.

### Customer List View

Signals’ attributes are visible on the Customer List View, facilitating sorting and filtering. This enables CSMs to gain a comprehensive understanding of the status of signals for their assigned customers.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-MGLSoceFkOA3yHvrYw_Ii-20240801-142652.png)

The values of the attributes are clickable, so signals’ details can be easily accessed within the list.&#x20;

### Customer 360 Profile

Within each customer profile, *Signals* are showcased on the right side of the page. This additional information enables CSMs to make informed decisions regarding their customers while reviewing the account health details.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-4iNdAokOL4c8778pw7goB-20240801-142725.png)

### Segmentation

These attributes are also accessible for segmentation purposes. This allows, for example, the retrieval of customer segments with higher counts of *bad open signals* or *good open signals*, which can then be utilized in reporting or various playbooks.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-wr9MaJ5AYc6MFGocUkhF9-20240801-142758.png)

### Health Scoring

Health Scores can be derived from these new attributes as well. The count of *Bad open signals&#x20;*&#x63;ould serve as a valuable metric to consider and contribute to the overall Global Health Score of each account.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-jdSndLS05mys-suYqA3po-20240801-142833.png)

### Calculated Metrics

Calculated metrics can be used to combine the signals’ attributes into formulas and get enhanced metrics. For example, summing the count of *bad open signals* and *bad closed signals* provides the total number of bad signals ever generated.

![](https://api.archbee.com/api/optimize/xmaGmZs1_xFDDYqFI69QU-5bOCFrtT7G4IUZ-9qcTaW-20240801-142913.png)

## Things to keep in mind

1. Signals will be generated for a specific company only if there has been at least one event within the last 2X days, where X represents the designated.

   E.g. If a company has recently been created and generates a ‘course\_created’ event, the system will not trigger a signal. Since the account is newly established, capturing this activity as an increase would be inaccurate. For example, if the timeframe is set to 7 days, the system will wait until 14 days have elapsed to ensure sufficient data for analyzing the activity over the last 7 days compared to the preceding 7 days.

2. Each signal is activated once per timeframe for the same category (good/bad). If the signal type remains the same, it won’t trigger again. However, if the signal type changes, a new notification will be generated.&#x20;

   E.g. If a notification was received for a usage drop of more than 15%, it won’t trigger again in the next X days (where X represents the interval selected for the trend). A new notification will be prompted only if the signal type changes, such as from a more than 15% decrease to a 20% increase.

3. The total count of events considered includes all events generated at the company level by all associated people. The formula does not normalize the event count, deliberately avoiding averaging the number of events per person. This deliberate exclusion of normalization allows for observing variations in activity when users join or depart from the company.

   E.g. If event counts were normalized, a person leaving the company would not reflect a decrease in activity, as the average number of events per person would remain constant. By not normalizing these numbers, a decrease in activity is observable when individuals leave a company, aiding in the identification of departures of key contributors.

