Creating Signals

Custom signals allow you to create detection rules tailored to your organization's specific needs, terminology, and processes. You can create signals that detect industry-specific terms, company jargon, or any pattern that's important to your business.

Signal Creation Form

To create a custom signal:

1. Navigate to Signals & Insights → Custom Signals
2. Click "Create Signal" button
3. Fill out the signal creation form with the following information

Signal Name and Description

• Signal Name: Choose a clear, descriptive name that identifies what the signal detects (e.g., "Competitor Mention", "Budget Approval", "Security Incident")
• Description: Provide a detailed description explaining what this signal detects and why it's important. This helps team members understand the signal's purpose.

Best Practices:

• Use specific, action-oriented names
• Keep names concise but descriptive
• Include context in the description about when and why this signal matters

Detection Type (Keyword, AI Prompt)

Choose how you want the signal to be detected:

Keyword-Based Detection:

• Matches specific words or phrases in the transcript
• Fast and reliable for exact term matching
• Best for: Company names, product names, specific terminology
• Example: Detect mentions of "Q4 budget" or "security breach"

AI Prompt-Based Detection:

• Uses natural language understanding to detect concepts
• Understands context and meaning, not just exact words
• Best for: Complex concepts, sentiment-based detection, nuanced patterns
• Example: Detect "expressions of customer dissatisfaction" or "discussions about project delays"

You can use both types together for comprehensive detection.

Detection Rules

Configure the specific rules for how your signal should be detected:

For Keyword-Based Signals:

• Enter keywords or phrases (one per line)
• Use exact matches or partial matches
• Configure case sensitivity
• Set minimum occurrence count
• Add exclusion words to reduce false positives

For AI Prompt-Based Signals:

• Write a natural language prompt describing what to detect
• Include examples of what should and shouldn't be detected
• Specify context requirements
• Set confidence thresholds

Signal Category

Assign your signal to a category for better organization:

• Use existing categories or create new ones
• Categories help filter and organize signals
• Examples: "Sales", "Support", "Engineering", "Compliance"
• Signals can belong to multiple categories

Priority Settings

Set the priority level for signals detected by this rule:

• High Priority: Critical signals that require immediate attention
• Medium Priority: Important signals that should be reviewed soon
• Low Priority: Informational signals for reference

Priority settings help you focus on the most important signals first. You can also configure different notification settings based on priority.

Notification Settings

Configure how you want to be notified when this signal is detected:

• Email Notifications: Receive email alerts when signals are detected
• In-App Notifications: Get notifications in the platform
• Notification Frequency: Choose immediate, daily digest, or weekly summary
• Notification Recipients: Select who should receive notifications (you, team members, specific roles)

Notification settings ensure important signals don't go unnoticed.