Skip to main content

Notifications

Table of Contents

  1. Understanding Notifications
  2. Accessing Notification Settings
  3. Notification Types
  4. In-App Notifications
  5. Real-Time Notification Delivery
  6. Email Notifications
  7. Call Reports
  8. Configuring Report Triggers
  9. Report Recipients
  10. Notification Preferences
  11. Team Notification Coordination
  12. Notification History and Audit
  13. Best Practices

Understanding Notifications

Notifications keep you informed about important activities and events in your AI employee operations. The platform uses a sophisticated real-time notification system that ensures you never miss critical updates.

Why Notifications Matter

Timely Awareness: Know about important calls and events as they happen, with instant delivery to your screen. Issue Identification: Get alerts when problems occur, often before they impact your operations significantly. Performance Visibility: Stay informed about AI employee activity across your entire organization. Follow-Up Triggers: Know when calls need human attention, with context about why the follow-up matters. Collaborative Awareness: See when teammates are viewing or responding to notifications, reducing duplicate efforts.

Notification Channels

Information can reach you through multiple synchronized channels: In-App Notifications: Real-time alerts displayed within the platform interface as events occur. Email Notifications: Messages delivered to your inbox for events that require attention when you are away from the platform. Call Reports: Aggregated summaries combining multiple events into digestible reports sent on a schedule.

Accessing Notification Settings

Navigate to the notification configuration page to customize how you receive alerts.
  1. Click Settings in the main navigation
  2. Select Notifications from the settings menu
  3. The Notifications settings page displays immediately

Page Layout

The notification settings page is organized into logical sections: Header Section: Contains the page title, description, and quick access to documentation. Notification Preferences: Controls for enabling or disabling different notification categories and channels. Call Report Configuration: Settings for automated call reports, including triggers and frequency. Recipient Management: Interface for adding team members to notification distribution lists. Preview Section: Shows sample notifications based on current settings to help you understand what you will receive.

Notification Types

Different types of notifications serve different purposes and arrive through different delivery mechanisms.

Real-Time Alerts

Immediate notifications delivered instantly as events occur: Completed Calls: Notification appears within seconds of call completion, including outcome and duration. Failed Calls: Critical alerts about technical issues requiring immediate attention. Important Conversation Outcomes: Alerts triggered by specific conversation results or detected keywords. System Issues: Notifications about platform health, quota limits, or configuration problems.

Periodic Summaries

Regular reports containing aggregated information: Hourly Digests: Quick summaries of activity over the past hour, useful during high-volume periods. Daily Summaries: End-of-day compilation of all activity, sent at a configured time. Weekly Reports: Broader trend analysis comparing current week performance to previous periods. Monthly Analytics: Comprehensive performance reports with deep insights and recommendations.

Triggered Notifications

Notifications based on specific conditions you define: Outcome-Based Triggers: Alerts when calls result in specific outcomes like success, voicemail, or busy signals. Keyword Detection: Notifications when certain words or phrases are mentioned in conversations. Metric Thresholds: Alerts when performance metrics cross defined boundaries. Volume-Based Alerts: Notifications when call volumes exceed or fall below expected levels.

In-App Notifications

Notifications displayed within the platform interface provide immediate visibility into events and activities.

Notification Center

The notification center serves as your central hub for all platform alerts and updates. Bell Icon: Located in the top navigation bar, provides quick access to your notifications. Unread Badge: Numerical indicator showing how many unread notifications await your attention. Dropdown Panel: Click the bell icon to reveal your notification list in a dropdown panel that overlays the current page.

Notification Contents

Each notification in the list contains structured information to help you quickly understand and act on the alert: Title: Brief summary of what happened, designed for at-a-glance scanning. Description: Additional context about the event, including key details like call duration, outcome, or affected resources. Timestamp: Indicates when the event occurred, displayed in your local timezone with relative time descriptions like “2 minutes ago.” Status Indicator: Visual marker showing the notification type and priority level through color coding. Action Links: Buttons or links that navigate directly to the relevant record or provide quick actions like dismissing or acknowledging the notification. Read/Unread Status: Visual distinction between notifications you have seen and those requiring attention.

Managing In-App Notifications

The platform provides several ways to organize and process your notifications efficiently. Mark as Read: Click individual notifications to mark them as read and remove them from the unread count. Mark All as Read: Clear your entire unread count with one action when you want a fresh start. Clear Notifications: Remove notifications from your list entirely once you have addressed them. Filter by Type: Use filter controls to show only specific notification categories, helping you focus on what matters most at the moment. Sort Options: Organize notifications by time, priority, type, or read status based on your workflow preferences. Archive: Move processed notifications to an archive for future reference without cluttering your active notification list.

Real-Time Updates

In-app notifications arrive through multiple delivery mechanisms depending on your current activity state: Instant Push: When you are actively using the platform, notifications appear immediately as events occur. Toast Alerts: Important high-priority notifications briefly appear as toast messages in the corner of your screen, ensuring you notice them even when focused on other tasks. Background Updates: Notifications continue to arrive even when the platform tab is not actively focused, appearing when you return to the tab. Audio Alerts: Optionally enable sound notifications for specific alert types to ensure you notice them even when not looking at the screen. Desktop Notifications: With browser permission, critical alerts can appear as operating system notifications outside the browser window.

Real-Time Notification Delivery

Understanding how the platform delivers notifications in real-time helps you appreciate the reliability and immediacy of the system.

Connection Establishment

When you log into the platform, several connection processes occur automatically in the background: Initial Handshake: Your browser authenticates with the real-time infrastructure using your session credentials. Channel Subscription: The system subscribes you to notification channels relevant to your role and configured preferences. State Synchronization: Your current notification state loads, including unread counts and recent notification history. Presence Registration: The platform registers your active presence, enabling features like notification read receipts and collaborative awareness.

Event Broadcasting

When events occur anywhere in your organization, the notification system follows a consistent delivery pattern: Event Detection: System processes detect relevant events such as call completions, failures, or threshold crossings. Rule Evaluation: The event is evaluated against all configured notification rules to determine who should be notified. Notification Creation: A notification record is created containing all relevant event details and context. Channel Distribution: The notification is routed to appropriate channels based on recipient preferences and current presence. Delivery Confirmation: The system tracks whether notifications were successfully delivered to each recipient.

Connection Resilience

The real-time notification system is designed to remain reliable even when network conditions are challenging: Automatic Reconnection: If your connection drops temporarily, the system automatically reconnects when network access is restored. Message Buffering: Notifications that arrive during brief disconnections are buffered and delivered when connection resumes. Connection State Indicators: Visual indicators show your current connection status, helping you understand notification delivery reliability. Graceful Degradation: If real-time delivery cannot be established, the platform falls back to periodic polling while continuing to attempt reconnection.

Email Notifications

Notifications delivered to your email inbox ensure you stay informed even when not actively using the platform.

Email Delivery

Email notifications reach recipients through a carefully orchestrated delivery system: Primary Email Address: Your account email receives notifications according to your configured preferences. Team Distribution: Notifications are sent to team members based on their roles, permissions, and individual preferences. Verified Recipients: All email addresses must be verified before receiving notifications to ensure security and deliverability. Bounce Handling: The system monitors email delivery success and automatically disables addresses that consistently bounce.

Email Contents

Notification emails are carefully designed for clarity and actionability: Subject Lines: Clear, scannable subjects that communicate the notification type and key information at a glance. Event Summary: Brief overview of what happened, mirroring the in-app notification content. Detailed Context: Additional information beyond what appears in the in-app notification, such as full conversation summaries or extended metric reports. Direct Links: Buttons or hyperlinks that navigate directly to the relevant record in the platform. Action Items: Clear calls-to-action when the notification requires a response or decision. Metadata Footer: Information about when the event occurred, who else received the notification, and how to adjust your notification preferences.

Email Frequency

The platform offers flexible email delivery timing to match your workflow: Immediate Delivery: High-priority notifications are sent within seconds of the event occurring. Batched Delivery: Routine notifications are collected and sent together at configured intervals to prevent inbox overload. Scheduled Reports: Comprehensive reports are sent at specific times such as end-of-day or start-of-week. Smart Throttling: The system prevents email flooding by intelligently limiting message frequency during high-volume periods. Do Not Disturb Hours: Configure quiet periods when non-critical email notifications are suppressed.

Call Reports

Automated reports summarizing call activity provide comprehensive visibility into your AI employee operations without requiring constant platform monitoring.

What Call Reports Include

Call reports compile comprehensive information about your AI employee activities: Summary Statistics: High-level metrics showing total calls, success rates, average duration, and other key performance indicators. Call Outcomes Breakdown: Distribution showing how many calls resulted in each outcome type such as success, voicemail, no answer, busy, and failed. Performance Metrics: Detailed analytics about AI employee effectiveness including conversation quality scores, sentiment analysis, and goal achievement rates. Notable Events: Highlighted incidents requiring attention such as repeated failures, unusual patterns, or threshold violations. Trend Comparisons: Comparison to previous periods showing whether metrics are improving, declining, or remaining stable. Drill-Down Links: References to specific calls or conversations that contributed to reported metrics, allowing detailed investigation.

Report Types

The platform generates several types of reports serving different analytical needs: Per-Call Reports: Individual notifications for specific calls matching configured triggers. Hourly Snapshots: Brief summaries of activity over the past hour, useful for monitoring operations during high-activity periods. Daily Summaries: Comprehensive end-of-day compilation of all activity including detailed breakdowns and analysis. Weekly Reports: Broader trend analysis covering the week, comparing to previous weeks and highlighting significant changes. Monthly Analytics: Comprehensive performance reports with deep insights, recommendations, and strategic observations. Custom Period Reports: On-demand reports for specific date ranges you define, useful for analyzing campaigns or specific events.

Report Format

Reports are designed for efficient consumption and actionability: Executive Summary: Top-of-report overview highlighting the most important information and requiring immediate attention. Key Metrics Highlighted: Critical numbers displayed prominently with visual emphasis and trend indicators. Status Indicators: Color-coded visual markers showing whether metrics are healthy, concerning, or critical. Tabular Data: Structured tables for detailed information that benefits from row-by-row comparison. Charts and Graphs: Visual representations of trends, distributions, and comparisons where graphics communicate better than numbers. Links to Detailed Records: Every metric and aggregation includes navigation to the underlying detailed data for investigation. Footer Metadata: Information about report generation time, data coverage period, and who else received the report.

Configuring Report Triggers

Control precisely which calls generate reports and notifications, allowing you to focus on what matters most to your operations.

Status-Based Triggers

Select which call outcomes trigger per-call reports: Success: Generate reports for successful calls where the conversation completed as intended. Voicemail: Notify when voicemail is left, indicating the contact was not reached but a message was delivered. No Answer: Alert when calls ring but are not answered, suggesting potential contact information issues or timing problems. Busy: Report busy signals, which may indicate high call volumes to the same contacts or poor timing. Failed: Critical alerts for technical failures that prevent calls from completing. Canceled: Notifications when calls are intentionally stopped before completion. All Outcomes: Receive notifications for every call regardless of outcome, providing complete visibility.

Advanced Trigger Conditions

Beyond basic status matching, you can configure sophisticated trigger rules: Duration Thresholds: Trigger reports for calls shorter or longer than specified durations. Keyword Detection: Generate notifications when specific words or phrases appear in conversation transcripts. Sentiment Thresholds: Alert when conversation sentiment exceeds or falls below configured levels. Custom Property Values: Trigger reports based on custom property values associated with contacts or conversations. Combination Rules: Create compound triggers requiring multiple conditions to all be true.

Trigger Configuration

Configuring triggers through the platform interface is straightforward:
  1. Navigate to Settings > Notifications
  2. Locate the Call Report Configuration section
  3. Select which call statuses should trigger per-call reports
  4. Optionally configure advanced conditions using the trigger builder
  5. Preview which past calls would have matched your rules
  6. Save your trigger configuration
Immediate Effect: Trigger changes apply immediately to all new calls completing after you save. Historical Testing: Test your triggers against historical call data to verify they capture what you intend.

Common Trigger Strategies

Different organizations have different notification needs. Common effective strategies include: Failures Only: Report only technical issues requiring investigation and resolution. All Outcomes: Receive notifications for every call, providing comprehensive visibility into all activity. Selective Positive: Get notifications for Success and Voicemail outcomes to track positive progress. Problem-Focused: Receive alerts for No Answer, Busy, and Failed to identify and address issues. High-Value Only: Use custom property triggers to notify only for calls to priority contacts. Keyword-Based: Trigger notifications only when specific important words or phrases are detected.

Report Recipients

Configure precisely who receives notification reports, ensuring the right information reaches the right people without overwhelming anyone.

Primary Recipient

Your account email address is configured as a recipient by default based on your user profile. Automatic Inclusion: All users with accounts automatically have the option to receive notifications relevant to their roles. Personal Preferences: Control which notifications you receive through your personal notification settings.

Additional Recipients

Expand notification distribution beyond registered platform users: External Email Addresses: Add email addresses for stakeholders who do not have platform accounts but need to receive reports. Verification Required: New email addresses must be verified before receiving notifications to ensure security and deliverability. Individual Preferences: Each recipient can have different notification preferences, receiving only what is relevant to their role. Distribution Lists: Create named groups of recipients for easy management of team notifications.

Role-Based Distribution

The platform can automatically route notifications based on user roles and permissions: Administrators: Receive system alerts, configuration changes, security notifications, and health monitoring alerts. Team Leads: Receive performance summaries, team activity reports, and aggregated metrics for their areas of responsibility. Individual Contributors: Receive notifications about their assigned contacts, AI employees, and campaigns. View-Only Users: Receive limited notifications, primarily informational updates without actionable alerts.

Managing Recipients

Configuring notification recipients is straightforward through the platform interface:
  1. Navigate to Settings > Notifications
  2. Scroll to the Recipients section
  3. Click Add Recipient to include new email addresses
  4. Enter the email address and select initial preference template
  5. The system sends verification email automatically
  6. Configure specific notification types for each recipient
  7. Save changes to activate the new configuration
Bulk Import: Add multiple recipients at once by uploading a CSV file containing email addresses and preferences. Recipient Status: View verification status, last delivery time, and delivery success rate for each configured recipient. Quick Enable/Disable: Temporarily pause notifications to specific recipients without removing them from the configuration.

Notification Preferences

Customize precisely how and when you receive notifications, creating a notification experience that keeps you informed without overwhelming you.

Enable/Disable Notifications

Granular control over notification categories allows you to receive only what matters: Category Toggles: Enable or disable entire categories like call completions, system alerts, or performance reports. Per-Event Type Controls: Within categories, enable specific event types while disabling others. Temporary Snooze: Pause all notifications temporarily without changing your permanent configuration. Smart Defaults: The system suggests notification settings based on your role and typical usage patterns. Inheritance: Team-level notification policies can establish baseline settings that individual users can then customize.

Frequency Settings

Control when notifications are delivered to match your workflow: Immediate Delivery: Critical notifications arrive instantly as events occur, ensuring you can respond promptly to urgent matters. Batched Delivery: Routine notifications are collected and delivered together at intervals you define. Scheduled Digests: Comprehensive summaries delivered at specific times like start-of-day or end-of-week. Event-Based Triggers: Some notifications deliver based on activity thresholds rather than time, such as “every 50 calls completed.” Custom Schedules: Define unique delivery schedules for different notification types.

Quiet Hours

Define periods when non-critical notifications are suppressed: Business Hours Mode: Set your typical working hours; notifications behave differently inside versus outside these hours. Weekend Suppression: Pause non-urgent notifications on weekends while allowing critical alerts through. Vacation Mode: Temporarily disable all notifications during time off, with optional delegation to team members. Time Zone Awareness: Quiet hours follow your local time zone regardless of where platform servers are located. Critical Override: Define which notification types ignore quiet hours due to urgency.

Channel Preferences

Choose how notifications reach you based on context and importance: Email Only: Receive notifications exclusively via email, useful when you check the platform infrequently. In-App Only: Notifications appear only within the platform interface, reducing email volume. Dual Channel: Receive notifications through both email and in-app for maximum visibility. Per-Type Channel Preferences: Configure different channels for different notification types. Priority-Based Routing: High-priority notifications use all configured channels while low-priority notifications use only one. Desktop Notifications: Enable browser-based desktop notifications that appear outside the application window. Mobile Push: If using a mobile application, configure mobile push notifications for critical alerts. SMS Fallback: Optionally configure SMS delivery for the highest-priority notifications when other channels may be inaccessible.

Team Notification Coordination

When multiple team members work together, coordinating notification responses prevents duplicate effort and ensures efficient issue resolution.

Collaborative Notification Handling

Shared Read Status: When any team member views a notification, others can see it has been viewed. Claim and Assignment: Team members can claim responsibility for handling specific notifications, signaling to others that the issue is being addressed. Comment and Collaboration: Add notes or comments to notifications, sharing context and resolution status with teammates. Activity Indicators: See when other team members are currently viewing the same notification you are looking at.

Notification Handoff

Transfer notification responsibility between team members: Reassignment: Change the assigned owner of a notification when different expertise is needed. Escalation: Promote notifications to higher-priority or senior team members when appropriate. Delegation: When unavailable, delegate your notifications to another team member with context about what needs attention.

Team Notification Dashboard

Shared views showing team-wide notification status: Team Queue: See all notifications assigned to your team, with status indicators showing what has been handled and what needs attention. Load Balancing: Visualize notification distribution across team members to ensure balanced workload. Response Metrics: Track team performance in notification acknowledgment and resolution times.

Notification History and Audit

The platform maintains comprehensive notification history for compliance, troubleshooting, and analysis purposes.

Accessing Notification History

History View: Navigate to the notification history page to browse past notifications beyond what appears in your active notification list. Search and Filter: Find specific notifications using keywords, date ranges, types, or recipients. Date Range Selection: View notifications from specific time periods for analysis or auditing. Export Capabilities: Download notification history in various formats for external analysis or record-keeping.

Delivery Tracking

Monitor notification delivery status and troubleshoot delivery issues: Delivery Confirmation: See exactly when each notification was delivered to each recipient. Read Receipts: Track when recipients opened and viewed notifications. Failure Analysis: Identify notifications that failed to deliver and understand why delivery failed. Retry History: View automatic retry attempts for failed deliveries and their outcomes.

Audit Trail

Comprehensive logging of notification-related actions: Configuration Changes: Track modifications to notification settings, triggers, and recipients with timestamps and user attribution. User Actions: Log when users mark notifications as read, archive notifications, or interact with notification content. System Events: Record automated notification generation, batching decisions, and delivery processes. Compliance Reports: Generate reports demonstrating notification delivery for regulatory or compliance requirements.

Best Practices

Effective notification management balances comprehensive awareness with sustainable workload, ensuring you stay informed without being overwhelmed.

Start Conservative

Begin with fewer notifications and expand thoughtfully: Enable Only Essential Alerts: Start by enabling notifications for critical issues like failures and system alerts. Add Incrementally: After establishing baseline notification patterns, add additional notification types one at a time to assess impact. Monitor Notification Fatigue: Watch for signs that notifications are being ignored, indicating volume has exceeded useful levels. Adjust Based on Experience: Modify notification settings based on what you actually act upon versus what you ignore.

Focus on Actionable Items

Prioritize notifications that drive specific actions: Failed Calls Needing Investigation: Always enable notifications for technical failures requiring troubleshooting. Important Outcomes Requiring Follow-Up: Get alerted to conversation outcomes that trigger next steps like scheduling meetings or sending materials. Unusual Patterns Warranting Review: Configure threshold alerts for metrics deviating from normal patterns. Time-Sensitive Events: Ensure notifications for events requiring prompt response arrive immediately.

Segment by Role

Different team members need different information based on their responsibilities: Technical Staff: System alerts, error notifications, integration status, and health monitoring. Operations Team: Call completion notifications, campaign progress, volume metrics, and daily activity summaries. Leadership: Strategic reports, trend analysis, performance summaries, and exception highlights. Customer-Facing Roles: Notifications about specific conversations, follow-up triggers, and customer sentiment alerts.

Review Periodically

Notification needs evolve as your operations mature: Monthly Reviews: Evaluate notification effectiveness and adjust settings monthly. After Major Changes: Reconsider notification needs after launching new campaigns, adding AI employees, or changing processes. Based on Feedback: Listen when team members mention notification volume or missing important alerts. Remove Unused Notifications: Disable notification types that consistently go unread or generate no action.

Avoid Overload

Too many notifications reduce overall effectiveness: Important Alerts Get Lost: Critical notifications disappear in high volumes of routine alerts. Team Members Tune Out: Excessive notifications train people to ignore all notifications. Action Items Are Missed: Truly important items requiring response get overlooked.

Set Expectations

When adding team members to notification lists, provide context: Explain What They Will Receive: Describe the types and typical volumes of notifications. Clarify Expected Actions: Define what team members should do when receiving different notification types. Provide Context for Alerts: Help new recipients understand why notifications matter and how to interpret them. Share Response Time Expectations: Clarify which notifications require immediate response versus those for informational purposes.

Test Configuration

After modifying notification settings, verify they work as intended: Verify Delivery: Confirm notifications are actually received through configured channels. Check Formatting: Ensure email notifications are well-formatted and links work correctly. Test Triggers: Verify trigger conditions match events as expected by reviewing historical matches. Confirm Timing: Check that batched and scheduled notifications arrive at expected times.

Document Settings

Maintain records of your notification configuration: Current Configuration: Document what notifications are enabled, for whom, through which channels. Rationale: Record why specific notification settings were chosen to provide context for future adjustments. Team Member Assignments: Track who receives what notifications and why they are included. Change Log: Keep history of notification configuration changes and the reasons behind them.

Leverage Collaboration Features

When working in teams, use collaborative notification features effectively: Coordinate Responses: Use notification claiming and assignment to prevent duplicate effort. Share Context: Add comments to notifications explaining investigation findings or resolution steps. Monitor Team Load: Watch team notification queues to ensure balanced distribution of alert workload. Establish Protocols: Define team processes for handling shared notifications, including response time expectations and escalation procedures.

Summary

Notifications keep you connected to your AI employee operations without requiring constant platform monitoring. The platform’s notification system combines real-time delivery, flexible configuration, and collaborative features to ensure the right information reaches the right people at the right time. By thoughtfully configuring notification types, triggers, recipients, and delivery preferences, you create an information flow that supports your operations without overwhelming your team. The real-time nature of the notification system ensures you stay aware of events as they happen, while batching and scheduling options prevent notification fatigue. Balance comprehensive awareness with manageable volume. Start with essential notifications and expand based on actual needs rather than enabling everything initially. Regularly review and refine your notification configuration as your operations evolve and your team learns what information drives value. The collaborative features built into the notification system enable teams to coordinate responses efficiently, preventing duplicate effort while ensuring no alerts fall through the cracks. By leveraging shared notification state, presence awareness, and assignment capabilities, teams transform notifications from individual alerts into coordinated team awareness.