Exception Queue Setup Guide (Microsoft Teams)

Microsoft Teams does not have a native "Exception Queue" feature. This guide shows you how to build a functional exception management system using Teams channels, Power Automate, and adaptive cards.

You'll create a dedicated channel for critical escalations, configure automated routing based on keywords and mentions, and set up notification workflows that ensure exceptions reach the right people within minutes.

Required access:

• Teams admin center access (teams.microsoft.com/admin)
• Power Automate license (included in most M365 Business plans)
• Owner or admin role in your target Team

Required decisions:

• Who monitors exceptions (specific people, not "the team")
• Response time SLA (recommend 15 minutes for critical, 2 hours for standard)
• Escalation path (who gets notified if no response in X minutes)

1. Open Teams and navigate to your operations or support Team.
2. Click the three dots next to the Team name, select "Add channel".
3. Name it "Exceptions" or "Critical Escalations" (avoid cute names).
4. Set channel type to "Standard" (not Private - exceptions need visibility).
5. In the description field, paste: "Critical issues requiring immediate response. SLA: [X] minutes. Monitored by: [Names]. Use @Exceptions to trigger alerts."
6. Click "Add".
7. Pin this channel to the top of your Team list (right-click channel > Pin).

Configure channel settings:

1. Click the three dots next to the channel name, select "Manage channel".
2. Under "Channel moderation", enable moderation if you want to control who can post (optional but recommended for high-volume teams).
3. Under "Connectors", add the "Incoming Webhook" connector (you'll use this in Step 3).
4. Copy the webhook

   webhook

   Click to read the full definition in our AI & Automation Glossary.

   URL and save it in a secure note - you'll need it later.

1. In the Exceptions channel, click the "+" tab button.
2. Add the "Tasks by Planner" app.
3. Create a new plan called "Exception Queue [Month Year]".
4. Create three buckets: "New", "In Progress", "Resolved".
5. Assign the monitoring team as plan members.

Create the on-call rotation:

1. In the channel, post a pinned message with the current on-call schedule.
2. Format: "On-call this week: [Name] (primary), [Name] (backup). Response SLA: 15 min."
3. Update this message weekly (set a recurring Outlook reminder).

Create the exception detection flow:

1. Go to make.powerautomate.com and sign in.
2. Click "Create" > "Automated cloud flow".
3. Name it "Exception Queue Router".
4. Search for and select the trigger "When a new channel message is added" (Microsoft Teams connector).
5. Configure the trigger:

   • Team: [Your Team name]
   • Channel: Exceptions
6. Click "New step" and add "Condition".
7. Set condition: "Message" contains "@Exceptions" OR "Message" contains "URGENT" OR "Message" contains "CRITICAL".

Configure the "Yes" branch (exception detected):

1. Add action "Post adaptive card in a chat or channel" (Teams connector).
2. Select "Flow bot" as the poster.
3. Post to: Channel
4. Team: [Your Team]
5. Channel: Exceptions
6. Paste this adaptive card JSON:

{
  "type": "AdaptiveCard",
  "body": [
    {
      "type": "TextBlock",
      "size": "Large",
      "weight": "Bolder",
      "text": "🚨 EXCEPTION DETECTED",
      "color": "Attention"
    },
    {
      "type": "TextBlock",
      "text": "Posted by: @{triggerOutputs()?['body/from/user/displayName']}",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "@{triggerOutputs()?['body/body/content']}",
      "wrap": true
    },
    {
      "type": "TextBlock",
      "text": "Time: @{utcNow()}",
      "isSubtle": true
    }
  ],
  "actions": [
    {
      "type": "Action.OpenUrl",
      "title": "View Message",
      "url": "@{triggerOutputs()?['body/messageLink']}"
    }
  ],
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.4"
}

7. Add action "Create a task" (Planner connector).

8. Configure:

   • Group Id: [Your Team's Group ID - find in Teams admin center]
   • Plan Id: [Your Exception Queue plan ID]
   • Title: "Exception from @{triggerOutputs()?['body/from/user/displayName']}"
   • Bucket Id: [ID of your "New" bucket]
   • Assignments: [User IDs of on-call team members]
9. Add action "Send an email" (Office 365 Outlook connector).

10. Configure:

    • To: [On-call team email addresses, separated by semicolons]
    • Subject: "EXCEPTION: Response required within 15 minutes"
    • Body: Include message link, poster name, and timestamp
11. Click "Save" at the top.

Create the escalation flow for unacknowledged exceptions:

1. In Power Automate, create a new "Scheduled cloud flow".
2. Name it "Exception Escalation Check".
3. Set to run every 15 minutes during business hours.
4. Add action "List tasks" (Planner connector).
5. Filter to tasks in "New" bucket older than 15 minutes.
6. Add "Apply to each" loop for filtered tasks.
7. Inside loop, add "Send an email" to escalation contacts (partners, directors).
8. Add "Update task details" to move task to "Escalated" bucket (create this bucket first).

Run these three tests:

Test 1: Basic exception trigger

1. Post a message in the Exceptions channel: "URGENT: Client portal down for BigCorp @Exceptions"
2. Verify within 60 seconds:

   • Adaptive card appears in channel
   • Planner task created in "New" bucket
   • Email received by on-call team
3. If any step fails, check Power Automate run history for errors.

Test 2: Task assignment and movement

1. Open the Planner task created in Test 1.
2. Assign it to yourself and move to "In Progress".
3. Add a comment: "Investigating - will update in 10 min".
4. Move to "Resolved" when done.

Test 3: Escalation trigger

1. Create a test task in Planner, set created date to 20 minutes ago (you'll need to use Graph API

   API

   Click to read the full definition in our AI & Automation Glossary.

   or do this manually by waiting).
2. Wait for the escalation flow to run (or trigger it manually).
3. Verify escalation email sent to leadership.

Add message extensions for faster categorization:

1. In the Exceptions channel, click "Format" under the message box.
2. Create quick-reply templates using the "Saved replies" feature:

   • "CRITICAL - System Down: [Description]"
   • "URGENT - Client Escalation: [Client Name] - [Issue]"
   • "STANDARD - Process Exception: [Process] - [Details]"

Set up tagging:

1. In each exception message, use hashtags: #SystemDown, #ClientIssue, #ProcessError
2. These become searchable and you can filter channel history by tag.

Weekly exception review:

1. Export Planner tasks to Excel (Planner > three dots > Export plan to Excel).
2. Track these metrics:

   • Total exceptions
   • Average time to acknowledgment
   • Average time to resolution
   • Exceptions by category
   • Repeat exceptions (same root cause)

Monthly leadership report template:

• Total exceptions: [Number]
• Met SLA: [Percentage]
• Top 3 exception types: [List with counts]
• Process improvements implemented: [List]
• Recommended actions: [Specific next steps]

Adaptive cards not posting:

• Verify the Flow bot has permission to post in the channel.
• Check that your adaptive card JSON is valid at adaptivecards.io/designer.

Emails not sending:

• Confirm the Office 365 Outlook connector is authenticated with an account that has send permissions.
• Check recipient email addresses are correct (no typos).

Planner tasks not creating:

• Verify the Group ID and Plan ID are correct (these are GUIDs, not names).
• Ensure the flow's connection has access to the Planner plan.

Escalation flow not triggering:

• Check the flow's run history - it may be running but finding no tasks to escalate.
• Verify the time filter logic (tasks older than X minutes).

Add sentiment analysis:

1. In Power Automate, add "Detect Sentiment" action (AI Builder) after the Teams trigger.
2. Add condition: If sentiment score < 0.3 (negative), auto-escalate.

Integrate with ticketing systems:

1. Add action "Create work item" (Azure DevOps) or equivalent for your system.
2. Map exception details to ticket fields.
3. Post ticket number back to Teams channel.

Create exception dashboard:

1. Use Power BI connector to pull Planner data.
2. Build real-time dashboard showing open exceptions, SLA compliance, trends.
3. Share dashboard link in the Exceptions channel description.

This system handles 50-100 exceptions per week reliably. For higher volumes, consider adding a triage role that reviews all exceptions before assignment.