Notification Channels

Junto posts into Slack or Microsoft Teams channels that you create and choose in Settings > Notifications. This page covers which channels to set up, what Junto posts to each, and how routing works.

Recommended Channels

Channel names are up to you; the ones below are suggestions. Two or three channels is the usual setup: approvals, alerts, and advisor.

1. Approvals -- required for runbook automation

Suggested name: #junto-approvals. Route the Runbook Approvals slot here.

• Runbook recommendation and auto-run cards with Approve / Reject buttons
• "Agent needs input" questions and delegated technician tasks
• Technicians can reply in the card's thread to talk to the agent, and the agent streams its progress into that thread

Without this channel, runbook cards never post and agent questions only appear in the Junto app.

2. Alerts -- recommended

Suggested name: #junto-alerts. Route the Alerts slot here, and usually Ticket Health Alerts too.

• Ticket-health alerts when a finding reaches high or critical. These can be filtered to specific boards or queues.
• Daily digest of integration and company-mapping gaps
• Urgent posts from the agent

3. Advisor -- optional

Suggested name: #junto-advisor. Route the Advisor slot here.

• New Advisor recommendations
• The daily ticket-health digest

4. Updates -- optional

Suggested name: #junto-updates. Route the Updates slot here.

• Non-urgent status posts from the agent

5. Report delivery -- optional, per schedule

Any channel a scheduled Workspace report should be sent to. This is chosen when you set up the schedule, not in Notification Channels.

A single channel can serve more than one purpose, and one purpose can go to several channels.

Direct Messages (no channel needed)

Some notifications go straight to the person concerned, matched by email address, and need no channel:

• Chatting with the agent happens in the Junto AI Assistant DM
• Time-entry nudges, Advisor owner notices, and escalations go to the assigned technician by DM

If a technician isn't matched to a Slack or Teams account, DMs to them cannot be delivered. Admins can check mappings under Settings > Notifications > Slack (or Teams) > Manage Users.

How Routing Works

Junto routes notifications by slot, a named type of notification. Each slot can be routed to one or more Slack or Teams channels, and notifications fan out to every active channel routed to that slot.

Slot	What posts to it
Runbook Approvals	Runbook recommendation and auto-run cards, agent questions, delegated tech tasks
Alerts	Urgent agent posts, the daily integration and mapping-gap digest
Ticket Health Alerts	Real-time alerts for high or critical Ticket Health findings, optionally filtered by board
Advisor	Advisor recommendations, the daily ticket-health digest
Updates	Non-urgent status posts from the agent

Prerequisites

At least one messaging provider must be connected under Settings > Notifications > Providers:

• Slack
• Microsoft Teams

Adding a Channel

1. Create the channel in Slack or Teams if it doesn't exist yet.
2. In Junto, go to Settings > Notifications and, in the Channels section, click Add Channel.
3. Select the Slot.
4. Choose the provider (Slack or Microsoft Teams) and pick the destination channel.
5. For Ticket Health Alerts, optionally choose which boards or queues this channel should receive. A channel with no filter receives everything.
6. Save.

Slack channels

Public channels are joined automatically when you select them. For a private channel, run /invite @Junto in that channel first; it then appears in the picker.

Teams channels

The picker lists channels from the teams the connecting account belongs to. When you select a channel, Junto installs the Junto AI app into that team automatically. This requires the app to have been published in your Teams admin center (see Microsoft Teams setup); if it hasn't been, the channel's health column shows the install failure.

Managing Channels

The channels table under Settings > Notifications shows each route's Slot, Provider, Destination, Used by (which features consume that slot), health, and Active status. From here you can:

• See at a glance which features are wired to each channel.
• Toggle a channel Active or inactive to pause delivery without deleting it.
• Delete channels you no longer need.

Optional: Let the Agent Search Slack

If you turn on Enable Slack agent tools under Settings > Integrations > Slack, the agent can read channel history to answer questions and find people who have discussed a topic. It is off by default and read-only, and you can map channels to client companies so answers stay scoped. See Slack setup.

TIP

Notification channels are for internal MSP team communication only. They are not used to contact end customers.

Troubleshooting

• No channels in the dropdown -- Connect Slack or Teams under Providers first. A private Slack channel only appears after /invite @Junto.
• Runbook cards never post -- No channel is routed to Runbook Approvals. Add one.
• Notifications not arriving -- Check the channel is Active, still exists in Slack or Teams, and (for Teams) that the health column doesn't show an install failure.
• A feature isn't posting to a channel -- Confirm a channel is routed to that feature's slot (see the table above) and is Active.
• A technician isn't getting DMs -- Their Slack or Teams account isn't matched to their Junto account. Check Manage Users under the provider.