Team Messaging Integration

Enable your AI agents to communicate through Microsoft Teams and Slack, sending messages, escalation cards, and status updates to team channels while responding to @mentions and chatting directly with users.

Overview

Team Messaging Integration transforms your agents from email-only processors into multi-channel collaborators. Once connected, agents can interact with your team in real time through the channels they already use every day.

Supported Platforms

Platform	Status	Setup Method
Microsoft Teams	Available	Teams app package upload + guided wizard
Slack	Available	OAuth "Add to Slack" button + guided wizard

Both platforms share the same underlying infrastructure: connections, channels, actions, tools, and audit logging. You can run Teams and Slack side by side, and the same agents work with both.

Key Capabilities

• Channel Messaging - Post updates, notifications, and status cards to Teams or Slack channels
• Escalation Cards - Send interactive cards (Adaptive Cards on Teams, Block Kit on Slack) with Approve/Deny buttons for rapid human-in-the-loop decisions
• @Mention Responses - Agents respond automatically when users @mention the bot in a channel
• 1:1 Personal Chat - Users chat directly with agents in private conversations
• Thread Replies - Continue conversations within existing message threads
• Proactive Notifications - Agents send messages to individual users without waiting for them to initiate

Benefits

Benefit	Description
Faster Approvals	Interactive buttons reduce approval time from hours to minutes
Team Visibility	Everyone sees agent activities in shared channels
Mobile Access	Approve requests from your phone via the Teams or Slack mobile app
Reduced Email	Move status updates from email to appropriate channels
Complete Audit Trail	All interactions are logged with automatic PII redaction
Multi-Platform	Connect both Teams and Slack to the same agents

Architecture

Outermind provides centralized bots for both Microsoft Teams and Slack that serve all customer tenants. There is no need to create your own Azure Bot resource, Slack App, or manage platform credentials. This ensures:

• Simple Setup - No Azure subscription, Bot Framework expertise, or Slack App creation required
• Automatic Updates - Bot capabilities are updated centrally by Outermind Inc.
• Multi-Tenant Isolation - Each tenant's data is isolated at the database and webhook level
• Enterprise Compatibility - Works with your existing Microsoft 365 or Slack workspace permissions

Your Microsoft 365 Tenant          Outermind                    Your Slack Workspace
        |                              |                              |
        v                              v                              v
+-------------------+           +-------------------+           +-------------------+
| Microsoft Teams   |    <->    |  Outermind API    |    <->    |  Slack            |
| (your channels)   |           |  (centralized     |           |  (your channels)  |
+-------------------+           |   bot + webhooks) |           +-------------------+
                                +-------------------+

Getting Started with Microsoft Teams

Prerequisites

Before setting up Teams, confirm you have the following:

1. Microsoft 365 Tenant - Your organization must have Microsoft Teams enabled as part of your Microsoft 365 subscription
2. Teams Admin Access - You need administrator privileges in the Microsoft Teams Admin Center to upload custom apps
3. Custom App Uploads Enabled - Your Teams tenant must allow custom app uploads (this is the default for most organizations)

info

Team Messaging uses a centralized Outermind-managed bot. You do not need an Azure subscription, Azure Bot resource, or any Azure expertise to set up this integration.

Teams Setup Wizard

The fastest way to get started is through the guided 4-step Setup Wizard.

1. Navigate to Build > Connections > Team Messaging
2. Click Setup Wizard and select Microsoft Teams
3. Follow the guided process below

Step 1: Welcome and Prerequisites

The wizard begins by explaining what you will set up and confirming your prerequisites:

• Microsoft 365 tenant with Teams enabled
• Teams Admin Center access
• Custom app upload permissions

Check each prerequisite box and click Next to continue.

Estimated time: 5-10 minutes for the entire wizard.

Step 2: Install the Teams App

In this step you configure the connection details and install the Outermind bot into your Teams workspace:

1. Enter connection details - Provide a connection name, display name, and optional description
2. Save the draft - Click Save Connection to create the connection and generate the Teams app package
3. Download the app package - Click Download App Package to get the .zip file containing the Teams manifest
4. Upload to Teams Admin Center - Open the Teams Admin Center, go to Manage apps, click Upload new app, and upload the downloaded .zip file
5. Set user permissions - On the app's page in Teams Admin Center, go to the Users and groups tab and configure who can use the bot (Everyone, specific users, or specific groups)
6. Add bot to Teams - In Microsoft Teams, go to Apps, search for "Outermind", click Add to a team, select the channel, and click Set up a bot. Repeat for additional teams as needed.

tip

You can grant admin consent for the Outermind app during this step by clicking the Grant Admin Consent link provided in the wizard. This allows the bot to access your tenant without individual user consent prompts.

Step 3: Verify Installation

The wizard listens in real time for channel registrations via SignalR. As you add the bot to teams, detected channels appear automatically in the wizard:

• Each detected channel shows a green checkmark with the team and channel name
• A pulsing indicator shows the wizard is listening for additional installations
• If channels are not detected automatically, click Verify Installation as a fallback
• You can also send a Test Message to any detected channel to confirm the bot can post messages

You must have at least one detected channel before proceeding.

warning

If verification fails with a "service principal not found" error, your tenant may need admin consent for the Outermind app. Click the Grant Admin Consent link shown in the error details and complete the consent flow, then retry.

Step 4: Complete

The wizard finalizes your connection, marks it as active, and presents next steps:

• Configure Channels - Set channel types and assign @mention agents
• Create Actions - Define what agents can do with Team Messaging
• Read Documentation - Learn about advanced features

Click Go to Connection to start configuring channels and actions.

Getting Started with Slack

Prerequisites

Before setting up Slack, confirm you have the following:

1. Slack Workspace - An active Slack workspace where you want to install the Outermind bot
2. Workspace Admin Access - You need administrator or owner privileges in the Slack workspace to authorize app installations

info

The Slack integration uses a centralized Outermind-managed Slack App. You do not need to create your own Slack App, manage API tokens, or configure any developer settings.

Slack Setup Wizard

1. Navigate to Build > Connections > Team Messaging
2. Click Setup Wizard and select Slack
3. Follow the guided process below

Step 1: Welcome and Configuration

The wizard explains what you will set up and collects initial configuration:

• Enter a connection name and optional description
• Select a default agent for @mention responses
• Confirm you have Slack workspace admin access

Click Next to continue.

Estimated time: 2-5 minutes for the entire wizard.

Step 2: Add to Slack

This step connects Outermind to your Slack workspace using a standard OAuth flow:

1. Click the Add to Slack button
2. A Slack authorization window opens where you can review the requested permissions
3. Select the workspace you want to connect (if you belong to multiple workspaces)
4. Click Allow to authorize Outermind

Once authorized, you are redirected back to the wizard. The connection is established and the bot token is securely stored.

tip

The OAuth flow requests only the permissions needed for bot messaging, channel reading, and user lookup. Outermind cannot access your files, private channels the bot is not invited to, or any workspace admin settings.

Step 3: Verify and Discover Channels

After authorization, the wizard verifies the connection and discovers available channels:

• The wizard calls Slack's auth.test API to verify the bot token is valid
• Available channels where the bot is a member are listed automatically
• Select which channels to register for agent messaging
• You can invite the bot to additional channels from Slack and they will appear here

You must register at least one channel before proceeding.

info

To add the bot to a channel in Slack, go to the channel, type /invite @Outermind, or click the channel name and add the Outermind app under Integrations.

Step 4: Complete

The wizard creates default actions, marks the connection as active, and presents next steps:

• Configure Channels - Set channel types and assign @mention agents
• Create Actions - Define what agents can do with Slack messaging
• Invite to More Channels - Add the bot to additional Slack channels

Click Go to Connection to start configuring channels and actions.

Core Concepts

Connections

A Connection links Outermind to your Microsoft Teams workspace or Slack workspace. It stores the workspace identifier, rate limit tracking, default settings, and the webhook endpoint that receives incoming activities.

Most organizations need one connection per platform. You can create multiple connections if you have separate workspaces.

Channels

Channels are registered messaging channels that your agents can post to. Each channel has:

• Channel Name - Friendly name (auto-detected from Teams or Slack)
• Team/Workspace Name - The parent team or workspace name
• Channel Type - Purpose of the channel (see below)
• @Mention Agent - Optional agent that responds to @mentions in this channel
• Default Flag - Mark one channel as the default for actions

Channel Types

Type	Purpose	Use Case
Escalation	Approval workflows	Human-in-the-loop decisions
Status	Status updates	Agent activity summaries
Alerts	Critical notifications	Urgent issues needing attention
Support	Support tickets	Customer service notifications
General	General purpose	Any messaging
Notifications	Non-urgent updates	Informational posts

Actions

Actions define what agents can do with Team Messaging. When you create an Action, it automatically becomes a Tool that agents can use during execution. This is powered by a database trigger that syncs actions to the Tools table in real time.

Actions work identically across Teams and Slack. The platform differences (Adaptive Cards vs. Block Kit, thread_ts vs. replyToId) are handled automatically.

Action Types

Action Type	Description	When to Use
Send Message	Post a plain text message to a channel	Status updates, notifications
Reply to Thread	Reply within an existing thread	Continue conversations
Send Escalation	Post an interactive card with approval buttons	Decisions requiring human approval
Send Status Card	Post a formatted status card	Visual status updates
Send Personal Message	Send a 1:1 direct message to a user	Private notifications, proactive outreach
Update Message	Edit an existing message	Correct or update previous posts
Delete Message	Remove a message	Clean up mistakes
Search Messages	Search message history	Find previous conversations

Creating Your First Integration

Step 1: Complete Setup Wizard

Follow the Setup Wizard for your platform (Teams or Slack) to install the bot and establish your connection, as described in the Getting Started sections above.

Step 2: Configure Channels

After the wizard completes, your detected channels are already registered. You can refine them:

1. Navigate to your connection's Channels tab
2. Click any row in the Channels table to open the edit modal
3. Configure:
   • Channel Type - Select the appropriate type (escalation, status, alerts, etc.)
   • @Mention Agent - Optionally assign an agent to respond to @mentions in this channel, or leave as "Use connection default"
   • Set as Default - Check if this should be the default channel for actions

The Channels table displays the Mention Agent column, showing which agent is assigned to each channel.

Step 3: Create Actions

1. Navigate to your connection's Actions tab
2. Click Add Action
3. Configure the action:
   • Action Name - Internal identifier (becomes the tool name)
   • Action Type - What the action does (send message, escalation, etc.)
   • Default Channel - Where messages go by default
   • Description - Help agents understand when to use this action

The Actions table includes a Channel column as the first column, showing which channel each action targets.

Step 4: Assign Tools to Agents

1. Navigate to Build > AI Agents > Agents
2. Edit the agent that should use Team Messaging
3. In the Tools section, find and enable your new Team Messaging actions
4. Save the agent

Each action you created in Step 3 appears as a tool that agents can call during execution.

@Mention Responses

When users @mention the Outermind bot in a Teams or Slack channel, an assigned agent processes the message and responds in the same thread.

Setting Up @Mention Responses

You can configure the @mention agent at two levels:

Connection-Level Default

1. Navigate to Build > Connections > Team Messaging and select your connection
2. Open the Settings tab
3. Locate the @Mention Agent section
4. Select an agent from the dropdown to serve as the default responder for all channels
5. Click Save

Channel-Level Override

1. Navigate to your connection's Channels tab
2. Click any row in the Channels table to open the channel edit modal
3. In the @Mention Agent dropdown, select a specific agent for this channel or choose Use connection default to fall back to the connection-level agent
4. Click Save

The Mention Agent column in the Channels table shows the currently assigned agent for each channel, making it easy to audit your configuration at a glance.

Resolution Order

When a user @mentions the bot in a channel, Outermind determines which agent responds using this priority:

1. Channel-level agent - If the channel has a specific agent assigned, that agent responds
2. Connection-level default - If the channel is set to "Use connection default," the connection's @Mention Agent responds
3. No response - If neither level has an agent configured, the mention is not processed

Example Interactions

Microsoft Teams:

User: @OutermindBot What's the status of my expense report?
         |
         v
Bot: I found your expense report #EXP-2024-001.
     Status: Pending approval by Finance team
     Submitted: January 20, 2026
     Amount: $450.00

Slack:

User: @Outermind What's the status of my expense report?
         |
         v
Bot: I found your expense report #EXP-2024-001.
     *Status:* Pending approval by Finance team
     *Submitted:* January 20, 2026
     *Amount:* $450.00

note

When you select a CAIOO (AI Chief of Staff) agent as the @mention responder, an amber note appears in the UI indicating that CAIOO agents have specialized behavior. CAIOO agents process mentions through their goal and project framework rather than as freeform chat.

Personal Chat (1:1 Messaging)

In addition to channel-based messaging, the bot supports direct 1:1 conversations with individual users in both Microsoft Teams and Slack.

How Personal Chat Works

• Teams: Users open a direct chat with the Outermind bot from the Teams app (search for "Outermind" in chat)
• Slack: Users send a direct message to the Outermind bot (find it under Apps or search for "Outermind" in DMs)
• Each user's conversation is tracked independently with a unique conversation reference
• The bot can both receive messages from and proactively send messages to individual users

Agent Assignment

Personal chat uses a two-level agent assignment model:

1. User-level assignment - Assign a specific agent to respond to a particular user's direct messages via the Users tab on the connection page
2. Connection-level fallback - If no user-level agent is assigned, the connection's default @Mention Agent responds

This allows you to give specific users a dedicated agent experience while maintaining a fallback for all other users.

Managing User Conversations

Navigate to your connection's Users tab to view all users who have interacted with the bot:

Column	Description
User	Display name and email (if available)
Status	Active or Inactive badge
Assigned Agent	Agent name or "Unassigned" with edit option
Installation	How the bot was installed (user, admin, etc.)
Last Interaction	When the user last interacted with the bot

From this tab you can:

• Assign an agent to a specific user via the inline dropdown
• Send a proactive message to a user by clicking the Send Message button
• Activate or deactivate a user's conversation

Proactive Messaging

Agents can proactively send messages to users who have interacted with the bot, even without the user initiating a conversation first. This is useful for:

• Notifying users about completed tasks
• Sending approval requests directly to a decision-maker
• Delivering personalized status updates
• Following up on escalations

Conversation Cleanup

Inactive personal chat conversations are automatically cleaned up after 90 days of inactivity. This ensures the system does not accumulate stale conversation references over time.

Escalation Workflows

One of the most powerful features is interactive escalation cards. These use Adaptive Cards on Microsoft Teams and Block Kit on Slack to present rich, actionable approval requests.

How Escalation Cards Work

1. An agent determines that human approval is needed
2. The agent calls the escalation action with a title, summary, and details
3. An interactive card appears in the configured channel with Approve/Deny buttons
4. A user clicks a button to make a decision
5. The decision is recorded in the Outermind approval queue, and the agent is notified

The card format adapts automatically to the platform:

Feature	Microsoft Teams	Slack
Card format	Adaptive Card JSON	Block Kit JSON
Buttons	Action.Submit	button elements in actions block
Text styling	Markdown subset	Slack mrkdwn (*bold*, _italic_)
Thread replies	Conversation reference + replyToId	thread_ts parameter

Example Escalation Card

+--------------------------------------------------+
|  URGENT: Purchase Order Approval Required         |
+--------------------------------------------------+
|  Vendor: Office Supplies Inc.                     |
|  Amount: $2,500.00                                |
|  Requested by: John Smith                         |
|  Due Date: January 25, 2026                       |
|                                                   |
|  [Approve]  [Deny]  [Request Info]                |
+--------------------------------------------------+

Viewing Approvals

Approval decisions made through escalation cards are tracked in the centralized approval system:

1. Navigate to Manage > Agent Self-Service > Approvals
2. Filter by source to see Teams- or Slack-originated approvals
3. Review approval history, response times, and decision details

Configuring Escalation Actions

When creating an escalation action, you can customize:

• Default channel - Which channel receives escalation cards
• Available actions - Which buttons appear (Approve, Deny, Request Info)
• Card template - Layout and fields displayed
• Urgency indicators - Visual styling for different priority levels

Agent Tools Reference

When you create actions for a Team Messaging connection, each action automatically becomes a tool that agents can use. Here is the complete set of tool capabilities:

Tool	Description	Key Parameters
send_message	Post a message to a channel	channel, message, mentions, priority
reply_thread	Reply in an existing thread	thread_id, message
post_escalation_card	Post interactive approval card	channel, title, summary, actions, deadline
post_status_card	Post formatted status update	channel, title, fields, color
send_personal_message	Send 1:1 message to a user	user_identifier, message
update_message	Edit an existing message	message_id, new_content
delete_message	Remove a message	message_id
search_messages	Search message history	query, channel, date_range, limit

These tools work identically regardless of whether the connection is Teams or Slack. The platform-specific formatting (Adaptive Cards vs. Block Kit, markdown vs. mrkdwn) is handled automatically by the tool factory.

tip

When writing agent instructions, reference the action names you created rather than these generic tool names. For example, if you created an action called "IT Escalation" of type "Send Escalation," instruct the agent: "When you need IT approval, use the IT Escalation tool to post an approval card to the IT channel."

Audit Logging

All Team Messaging activity is logged for compliance and debugging, with automatic PII redaction.

What Is Logged

• Message sends and responses (with content redacted in detailed logs)
• Escalation card posts and button clicks
• @Mention interactions
• Personal chat messages (metadata only, content redacted)
• Connection tests
• Errors and failures

Viewing Logs

1. Navigate to Build > Connections > Team Messaging
2. Select your connection
3. Open the Logs tab
4. Filter by:
   • Date range
   • Action type
   • Success/failure status

Log Storage

Tier	Location	Purpose
SQL Summary	Database	Quick lookup and filtering
Detailed Logs	Azure Blob Storage	Full request/response payloads
PII Redaction	Automatic	Sensitive data (emails, user IDs, conversation IDs, bot tokens) automatically redacted in detailed logs

Rate Limiting

Both Microsoft Teams and Slack enforce rate limits on bot messaging. Outermind tracks these automatically so you do not need to manage them manually.

Teams Rate Limits

Metric	Description
Remaining	Messages left in current window
Reset Time	When the limit resets
Daily Limit	Maximum messages per day
Today's Count	Messages sent today

Personal Chat: 7 messages/second, 60 messages/30 seconds, 1,800 messages/hour per conversation. 50 requests/second per tenant.

Slack Rate Limits

Slack uses tiered rate limits per API method:

Tier	Rate	Methods
Tier 2	20 requests/min	Channel listing, user listing
Tier 3	50 requests/min	Message history
Tier 4	100+ requests/min	Sending messages, reactions

What Happens at the Limit

• Actions return a clear error message instead of failing silently
• The system automatically retries with exponential backoff when transient rate limit errors occur
• Agents can decide to retry later or use alternative communication channels
• Administrators can monitor rate limit usage in the audit log

Security

Credential Management

• Teams: The centralized bot credentials are managed by Outermind Inc. and are not exposed to customers. Incoming webhooks are validated using JWT verification via the Microsoft 365 Agents SDK.
• Slack: Workspace-specific bot tokens are encrypted using AES-256-CBC before storage. Incoming webhooks are validated using HMAC-SHA256 signature verification with a 5-minute timestamp replay protection window.

Multi-Tenant Isolation

• All data is scoped by tenant ID
• Teams: The centralized webhook endpoint routes activities by the customer's Microsoft 365 tenant ID
• Slack: Webhook events are routed by the Slack workspace ID (team_id)
• Cross-tenant access is prevented at the database level

Permissions

Permission	Description
team-messaging:read	View connections, channels, actions, and logs
team-messaging:write	Create and modify connections, channels, and actions
team-messaging:send	Execute messaging actions
team-messaging:personal-chat	Send 1:1 personal messages to users
team-messaging:admin	Full administrative access

Troubleshooting

Microsoft Teams

Bot Not Responding to @Mentions

Symptoms: Users mention the bot but nothing happens.

Solutions:

1. Verify the bot is installed in the Teams channel (check the Channels tab on your connection)
2. Confirm a @Mention Agent is configured at the connection or channel level (check the Settings tab)
3. Verify the assigned agent is active and has at least one enabled tool
4. Check the audit logs on the Logs tab for errors
5. If using a CAIOO agent, verify CAIOO is configured and has completed its setup

Connection Test Failing

Symptoms: Clicking "Test Connection" returns an error.

Solutions:

1. Verify the Teams app is installed in your Teams Admin Center
2. Ensure the bot has been added to at least one team
3. If the error contains AADSTS700016, the App Registration may need to be set to Multi Tenant -- follow the troubleshooting modal instructions
4. If the error contains a "service principal not found" message, grant admin consent for the Outermind app
5. Check the audit logs for specific error messages

Messages Not Appearing in Teams

Symptoms: Actions succeed in the log but no message appears in Teams.

Solutions:

1. Verify the channel ID is correct by checking the Channels tab
2. Ensure the bot has permission to post in the target channel
3. Check that the channel is not restricted or read-only in Teams
4. Review the audit log for the actual API response from Teams

Escalation Buttons Not Working

Symptoms: Clicking Approve/Deny on an escalation card does nothing.

Solutions:

1. Check that the escalation has not already been resolved (buttons are disabled after first response)
2. Verify the webhook endpoint is receiving invoke activities in the audit log
3. Ensure the user clicking the button has permission to respond
4. Check that the Outermind API is running and accessible

Personal Chat Not Working

Symptoms: Users send messages to the bot but get no response.

Solutions:

1. Verify the user has installed the bot in their personal Teams chat
2. Check the Users tab on your connection to see if the user appears
3. Confirm an agent is assigned (either user-level or connection-level fallback)
4. Check the audit log for incoming personal message events
5. Verify the team-messaging-personal-chat queue is processing messages

Setup Wizard Stuck at Verify Step

Symptoms: The wizard does not detect any channels after installing the bot.

Solutions:

1. Ensure you completed all steps in the Teams Admin Center (upload app, set permissions, add to team)
2. Click Verify Installation to manually check for channels
3. Wait 1-2 minutes -- Teams may take time to propagate the installation
4. Try removing and re-adding the bot to a team
5. Check that the Teams Admin Center shows the Outermind app as available

Slack

Bot Not Responding to @Mentions in Slack

Symptoms: Users @mention the bot in a Slack channel but nothing happens.

Solutions:

1. Verify the bot has been invited to the channel (type /invite @Outermind in the channel)
2. Confirm the channel is registered in the Channels tab on your connection
3. Verify a @Mention Agent is configured at the connection or channel level
4. Check the audit logs on the Logs tab for webhook delivery errors

Slack OAuth Failed

Symptoms: The "Add to Slack" button fails or redirects with an error.

Solutions:

1. Ensure you have workspace admin privileges in Slack
2. Check that your browser is not blocking the OAuth popup
3. If you see an error code in the URL after redirect, contact Outermind support with the error code
4. Try the OAuth flow again -- transient network issues can cause failures

Slack DMs Not Working

Symptoms: Users send direct messages to the bot but get no response.

Solutions:

1. Check the Users tab on your connection to see if the user appears
2. Confirm an agent is assigned (either user-level or connection-level fallback)
3. Verify the connection is active (check the connection status badge)
4. Check the audit log for incoming DM events

Channels Not Appearing After Bot Invite

Symptoms: You invited the bot to a Slack channel but it does not appear in channel discovery.

Solutions:

1. Wait 30 seconds and click Refresh on the Channels tab
2. Ensure the bot was invited successfully (check in Slack that it appears in the channel's member list)
3. For private channels, the bot must be explicitly invited -- it cannot discover private channels on its own
4. Try removing and re-inviting the bot to the channel

Best Practices

Channel Organization

• Create separate channels for different purposes (escalations, status updates, alerts)
• Use descriptive channel types so agents can target the right channel
• Mark one channel as default for general messaging

Agent Instructions

Include clear guidance in your agent instructions for when and how to use Team Messaging tools:

When you need human approval for an action:
1. Use the escalation tool to post an approval card to the Escalations channel
2. Include a clear title, detailed summary, and any relevant context
3. Set an appropriate deadline if time-sensitive

When reporting status to the team:
1. Use the status card tool to post to the Status Updates channel
2. Include key metrics, changes, and any action items

@Mention Agent Selection

• Assign your most general-purpose agent as the connection-level default
• Use channel-level overrides for specialized channels (e.g., assign a finance agent to the Finance channel)
• Consider using CAIOO for channels where strategic or project-related questions are common

Personal Chat

• Start with a connection-level fallback agent and add user-specific assignments as patterns emerge
• Use proactive messaging sparingly to avoid notification fatigue
• Monitor the Users tab for installation trends and inactive conversations

Multi-Platform Tips

• You can connect both Teams and Slack to the same agents simultaneously
• Create separate actions per platform if you want different channel routing
• Audit logs distinguish between Teams and Slack activity for filtering

Related Topics

• Agents - Configure agents to use Team Messaging tools
• Tools - Learn about the tools system
• HTTP API Tools - Connect other external APIs
• Escalation Router Overview - Configure escalation workflows
• Safety Gateway Overview - Configure outbound message safety