> ## Documentation Index > Fetch the complete documentation index at: https://docs.alysio.ai/llms.txt > Use this file to discover all available pages before exploring further. # Setting Up Revenue Signals > Configure revenue signal detection ## Setting Up Revenue Signals Setting up Revenue Signals allows organizations to configure how Alysio monitors operational data and identifies events that may affect pipeline health, deal progression, and forecast outcomes. Revenue signals are generated when the platform detects meaningful operational patterns across connected systems such as CRM platforms, engagement tools, and intelligence providers. These signals help revenue teams identify risks, opportunities, and operational changes that may influence revenue performance. During configuration, organizations define which signals should be monitored, which systems should provide data for signal detection, and how signals should be surfaced within the platform. This setup ensures that the Signals Engine can continuously analyze operational data and highlight events that require attention from revenue teams. *** ## Definition **Revenue Signals Configuration** refers to the process of enabling signal detection within Alysio and defining the operational conditions the platform should monitor across connected systems. Once configured, the Signals Engine continuously evaluates operational data and surfaces signals when relevant patterns or events are detected. These signals can then trigger insights, notifications, or automated responses through AI Revenue Agents. *** ## Prerequisites Before configuring revenue signals, certain platform components must be connected so the Signals Engine can access operational data. Required integrations typically include: CRM systems such as Salesforce or HubSpot\ Communication platforms such as email and calendar systems\ Conversation intelligence tools such as Gong\ Intelligence providers such as ZoomInfo\ Collaboration platforms such as Slack These integrations provide the operational data required for signal detection. Organizations should ensure that integrations are connected and authorized before configuring revenue signals. *** ## Configuration Process Setting up revenue signals typically involves several steps within the Alysio platform. ### 1. Enable the Signals Engine Revenue signals are generated by the platform’s Signals Engine. During setup, administrators enable the Signals Engine within the workspace configuration settings. Once enabled, the platform begins monitoring operational activity across connected systems. *** ### 2. Connect Data Sources The Signals Engine analyzes operational data retrieved from integrated revenue systems. Administrators should confirm that all relevant integrations are connected and functioning correctly. This ensures that the platform has access to the data required to detect operational signals. Common data sources include: CRM opportunity data\ Meeting and communication activity\ Account intelligence signals\ Customer engagement activity The more comprehensive the connected data sources, the more accurate signal detection will be. *** ### 3. Define Signal Types Organizations can configure which operational signals should be monitored within their workspace. Common signal types include: Deal stagnation signals\ Declining engagement signals\ Ghosting or communication drop-off\ Executive stakeholder changes\ Pipeline coverage gaps\ Renewal risk signals Defining these signal types allows the platform to monitor operational conditions that are most relevant to the organization’s revenue processes. *** ### 4. Configure Notifications and Responses Once signals are enabled, organizations can configure how signals should be surfaced or acted upon. Signals may trigger: Notifications to account owners\ Alerts in collaboration platforms such as Slack\ AI Revenue Agent workflows\ CRM task creation\ Executive brief generation These responses ensure that signals lead to operational awareness and action. *** ### 5. Validate Signal Monitoring After configuration is complete, administrators can review signal activity to confirm that the system is detecting operational events correctly. This validation step ensures that the Signals Engine is monitoring the intended operational conditions and that alerts or workflows are functioning properly. Administrators may adjust signal thresholds or response actions if needed. *** ## Example Signal Configuration A revenue operations team configures the platform to monitor stalled opportunities. The Signals Engine analyzes CRM stage progression and engagement activity for each opportunity. If an opportunity remains in the same stage longer than expected and engagement activity has declined, the platform generates a deal stagnation signal. An AI Revenue Agent then assigns a follow-up task to the account owner and posts an alert in Slack. This automated workflow ensures that stalled opportunities are addressed quickly. *** ## Operational Impact Configuring revenue signals improves operational awareness across the revenue organization. Organizations commonly experience: Earlier identification of pipeline risks\ Improved visibility into account engagement trends\ Faster response to operational changes affecting deals\ Reduced reliance on manual pipeline monitoring By continuously monitoring operational activity, revenue signals allow teams to respond proactively to revenue risks and opportunities. *** ## Platform Data Flow Revenue signal monitoring relies on operational data flowing through multiple components of the Alysio platform. Connected Revenue Systems (CRM, Engagement Platforms, Intelligence Providers)\ ↓\ Alysio Signals Engine\ ↓\ Revenue Signals Detection\ ↓\ AI Revenue Agents\ ↓\ Execution Engine\ ↓\ Notifications, Tasks, and Workflows Diagram Alt Text Diagram illustrating how Alysio retrieves operational data from connected revenue systems, analyzes patterns through the Signals Engine, detects revenue signals, and triggers automated responses through AI Revenue Agents and the Execution Engine. *** ## Summary Setting up Revenue Signals allows organizations to configure how Alysio monitors operational activity across their revenue systems. By enabling the Signals Engine, connecting data sources, defining signal types, and configuring response workflows, organizations can ensure that meaningful operational events are automatically detected and surfaced. This enables revenue teams to maintain visibility into pipeline health, account engagement, and operational conditions that may influence revenue outcomes.