ConnectWise-to-Slack: 12 reports that replace your daily standup

ConnectWise has the data. Slack is where the team lives. The problem is there's nothing meaningful connecting them by default.

The CW Slack Bridge fixes that. It's a scheduled Lambda function that pulls structured data from ConnectWise Manage and formats it into Slack Block Kit messages — operational intelligence your team actually reads, instead of CW dashboards they have to remember to open.

What it sends

Daily standup brief — Every morning before standup, the bridge posts a structured summary: tickets opened since yesterday, tickets due today, tickets overdue by priority, and which techs are carrying the most open tickets. The team walks into the room already knowing the shape of the day.

Unassigned ticket alert — Any ticket sitting unassigned for more than 4 hours gets a Slack alert with ticket ID, company, priority, and summary. The channel name is configurable — most MSPs route these to #triage. The alert includes an "Assign to me" deep link (opens the CW ticket in browser).

Workload balance report — A weekly view of ticket distribution across techs. Sorted by open ticket count. Flags techs carrying 2× the team average. Flagging doesn't reassign — it gives the team lead visibility before it becomes a burnout issue.

SLA countdown — Tickets approaching SLA breach within the next 4 hours. Formatted as a table with time remaining, company, priority, and assigned tech. Runs on a 2-hour interval so the team sees the window closing before it closes.

New ticket notification — Webhook-style: when a new ticket is created above a priority threshold (configurable), a message goes to the relevant channel within 60 seconds. Includes the full ticket body, not just the title.

Ticket merge candidate alert — Two or more tickets from the same company with the same category and status opened within 30 minutes of each other. These are almost always the same issue reported by multiple users. One tech should own both.

On-call rotation reminder — Who's on call today, who's on call tomorrow, and their contact info. Posted every morning at 7 AM. The tech knows they're on call because they set the schedule. The rest of the team knows who to escalate to.

CSAT daily rollup — Yesterday's CSAT scores by tech, sorted highest to lowest. Average, median, count. Color-coded green/yellow/red based on threshold. Designed to take 10 seconds to read, not 10 minutes.

Open ticket summary by category — Organized by ticket category/subcategory. Gives operational visibility into whether there's a spike in any particular issue type (networking, email, hardware, etc.) that might indicate a pattern.

Stalled ticket alert — Tickets in "In Progress" status with no update in 48+ hours. With a reason summary and the last tech to touch it. Stalled tickets are the ones that fall through the cracks.

First response time report — Weekly average time-to-first-response by priority level. P1 < 30 minutes, P2 < 2 hours, P3 < 4 hours. This is the SLA compliance number before it becomes the SLA breach number.

Shift handoff summary — End of day (configurable time), the bridge sends a structured handoff: open tickets by status, anything created today that's still open, and one-liner notes on the hot ones. The tech coming in the next morning knows the state of play before they log in.

The format

All reports use Slack Block Kit: structured blocks with headers, context lines, and section dividers. They look like Slack-native messages, not text dumps. They're scannable in 5 seconds and linkable in 5 more.

The Slack Channel Router handles tenant-specific routing: different companies can route to different Slack workspaces or different channels based on client tags in ConnectWise.

Current state

997 tests across 12 report modules. Built with injectable ConnectWise API mocks — every report has tests covering the happy path, empty queue (no tickets), priority filters, and formatting edge cases.

The CW Slack Bridge is a Stripe product waiting to happen. The pricing target: $39/month for a single ConnectWise instance, $99/month for up to 5 instances (useful for MSP groups with multiple CW environments). The marginal cost is near-zero — it's scheduled Lambda invocations against the CW REST API.

The integration time is 20 minutes: CW API key, Slack bot token, configure channels, deploy the SAM template. The first report shows up the next morning.

If you're running an MSP on ConnectWise and your team lives in Slack, reply — I'm looking for the first pilot user.