Teams message extension context matches the user moment
Map the message-extension command to the exact moment of intent, because Teams gives different payload and behavior when the user starts from the compose box, command box, or an existing message.
Why this can grow a startup
Teams does not have one generic command surface. Microsoft's message-extension docs say users can invoke actions from the compose message area, the command box, or directly from a message, and the app-structure guide frames message extensions as shortcuts that let people act without leaving the conversation. That means the best extension design starts with the user moment. A search command for lookup work belongs in the compose area or command box. A reply helper or escalation action often belongs on the message itself. Context fit reduces explanation because the surface already explains why the command exists.
Source-backed example
Microsoft says message extensions let users search or initiate actions from the compose area, command box, or a message, and describes them as shortcuts for acting without navigating away from the conversation.
Source-reported evidence
Source: Microsoft Learn: Message extensions
Microsoft documents three invoke locations for action commands and separately notes that search cards do not trigger from a message.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Product, Onboarding, Retention is relevant to teams apps, message extensions, workflow design and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Product and Onboarding, using evidence from Microsoft Learn: Message extensions as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.