# Teams panels static tab only before room-device pitch

> Pitch room-device usage only when the app can deliver the core job as static web content, because bots and messaging capabilities still are not supported on Teams panels.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-panels-static-tab-only-before-room-device-pitch/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/app-support-on-teams-panels)
- GrowthDex source hub: [Microsoft Learn: Microsoft Teams apps support on Teams panels](/sources/microsoft-learn-microsoft-teams-apps-support-on-teams-panels-learn-micro/)
- Last checked: 2026-06-09T06:09:26.000Z
- Rarity: rare
- Budget: medium
- Channels: Product-led Growth, Brand Trust, Enterprise Rollout
- Stages: teams panels, static tabs, shared rooms, capability fit


## Why this can grow

A lot of collaboration products assume every Teams surface can carry the same capability set. Microsoft says Teams panels do not work that way. The current support is for static web content, while bot and messaging capabilities are not supported. That turns product fit into a rollout question. If the room experience depends on a bot, compose action, or message workflow, the panel is the wrong wedge. But if the product can do something useful as a clean static view, the room device can become a real discovery surface instead of a broken promise.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where teams panels static tab only before room-device pitch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product-led Growth and Brand Trust channel.
3. Use the evidence from learn.microsoft.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Microsoft says Teams panels currently support only static tabs web content and do not support bot or messaging capabilities for the app experience there.

## Adjacent tactics in the same lane

- [Teams panels five pinned actions before More screen sprawl](/growth-ideas/teams-panels-five-pinned-actions-before-more-screen-sprawl/) - same source, 1 shared stage
- [Telegram Main Mini App previews before store push](/growth-ideas/telegram-main-mini-app-previews-before-store-push/) - 2 shared channels
- [Notion owned-domain link preview before generic embed](/growth-ideas/notion-owned-domain-link-preview-before-generic-embed/) - 2 shared channels
- [Baremetrics live dashboard demo link before sales deck screenshot](/growth-ideas/baremetrics-live-dashboard-demo-link-before-sales-deck-screenshot/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Teams rollout should survive the policy layer](/blog/the-teams-rollout-should-survive-the-policy-layer/) - enterprise rollout, distribution, product-led growth

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.