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.
Company 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 and metric
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.
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.
Founder checklist
- Read Microsoft Learn: Message extensions and identify what is directly supported.
- Choose one channel context: Product, Onboarding, Retention.
- Define the test around Microsoft documents three invoke locations for action commands and separately notes that search cards do not trigger from a message..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.