> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Notify internal team

> Send updates to internal channels for coordination

This action sends notifications to your internal team members via Microsoft Teams, Slack, or email. Perfect for keeping everyone informed about workflow results, important alerts, or issues that need attention.

<Tip>
  Automating internal notifications ensures your team stays informed about important events without manual effort. No more forgetting to update stakeholders or spending time writing individual messages - everything happens automatically when workflows complete.
</Tip>

## How it works

### Message collection

The action takes messages from previous workflow steps (like analysis results, summaries, or alerts) and prepares them for delivery.

### Context addition

If the workflow was triggered by a ticket, it automatically adds ticket details (ID, title, company) to provide context.

### Attachment preparation

For email notifications, it can convert data tables from previous actions (like reports) into CSV files for easy review.

### Notification delivery

Based on your chosen channel, it sends the information to the specified team members, channels, or email addresses.

### Optional feedback

If enabled, it includes a feedback link so recipients can provide input on the automated process.

## Setup

**Message source**: Takes messages from previous actions like Ticket Triage, Executive Summary, or Data Analysis.

**Communication channel**: Choose how to notify your team:

* **Teams** - Send to specific users or Teams channels
* **Slack** - Send to Slack channels or direct messages
* **Email** - Send traditional email with optional attachments

**Recipients**: Specify who receives the notifications:

* **Teams Users**: Select team members who have the Neo AI Agent Teams app installed
* **Slack Channels**: Specify Slack channel IDs for notifications
* **Email Addresses**: Add email addresses for recipients

**Data attachments (optional)**: For email, attach CSV files with detailed data from previous actions.

**Feedback requests (optional)**: Add feedback links to gather input on automated processes.

## What you get

After running, you'll see confirmation of which notifications were sent successfully and details about any failed notifications and why they failed.

## Use cases

### Report analysis results

**When:** After a Data Analysis action creates a report
**Setup:**

1. Data Analysis - Generates a detailed report or table
2. Notify Internal Team - Sends the report to managers via email with CSV attachment

**Result:** Stakeholders receive comprehensive reports without manual effort

### Alert on critical issues

**When:** High-priority or unassigned tickets are detected
**Setup:**

1. Filter Tickets - Find tickets meeting specific criteria
2. Build Message - Create alert summary
3. Notify Internal Team - Send immediate Teams alert to support managers

**Result:** Critical issues get immediate attention from the right people

### Workflow completion updates

**When:** Complex automated workflows complete (successfully or with issues)
**Setup:**

1. Any complex workflow (like L1 Engineer attempts)
2. Notify Internal Team - Inform L2 support team about results

**Result:** Team knows what automation accomplished and what needs manual follow-up

### Quality assurance alerts

**When:** Ticket QA scores fall below acceptable levels
**Setup:**

1. Ticket QA - Reviews completed tickets
2. Conditional logic - Check if scores are below threshold
3. Notify Internal Team - Alert quality managers

**Result:** Quality issues get immediate management attention

### Executive summaries

**When:** Scheduled reports need to go to leadership
**Setup:**

1. Executive Summary - Analyzes tickets from past period
2. Notify Internal Team - Email comprehensive report to executives

**Result:** Leadership gets regular insights into service delivery

## Best practices

### Choose the right channel

* Use **Teams** for immediate alerts and collaborative discussions
* Use **Slack** for team coordination if that's your primary platform
* Use **Email** for formal reports and detailed information

### Set up recipients properly

* For Teams: Ensure recipients have installed the Neo AI Agent Teams app
* For Slack: Verify channel IDs are correct
* For Email: Use distribution lists for groups when appropriate

### Use clear message sources

Make sure previous actions create clear, useful messages. Use Build Message to format complex information into readable updates.

### Include relevant data

For email notifications with data analysis, enable CSV attachments to provide detailed information stakeholders can review.

### Enable feedback strategically

Use feedback requests when you want input on new or modified automated processes.

### Test delivery

Verify notifications are reaching intended recipients and adjust settings if needed.

### Consider timing

For scheduled workflows, consider when notifications are sent - avoid alerting people outside business hours unless it's truly urgent.

### Monitor success

Check the Event History to ensure notifications are being delivered successfully and identify any delivery issues.

## Communication channels

### Microsoft Teams

* Recipients must have the Neo AI Agent Teams app installed
* Works with both direct messages and channel notifications
* Supports rich formatting and interactive elements

### Slack

* Requires proper Slack channel ID configuration
* Works with your existing Slack workspace
* Integrates with Slack's notification preferences

### Email

* Works with any email address or distribution list
* Supports CSV attachments for detailed data
* Professional formatting for formal communications