Microsoft Teams app source

When to use it

Choose Teams when you want to notify an agent about a message you address to Doorbell without building a Power Automate flow or a separate Teams app for each agent.

Set it up

1. In Doorbell, open Sources, choose New source, then Microsoft Teams app. If it says Not configured, ask the service operator to enable the Teams integration first.
2. Verify your Microsoft identity from that page. This checks your tenant and user identity; it does not authorize mail access or discover every app in your tenant.
3. Choose Install in Microsoft Teams when the app is available in the Teams catalog. Otherwise, download the app package from this page and upload the ZIP in Microsoft Teams under Apps → Manage your apps → Upload an app → Upload a custom app. Your organization may first need to allow custom apps. Add the app to your personal chat or to a team; one team installation covers its standard channels.
4. In personal chat, send Connect to the app. In a standard channel, choose the app from the @mention suggestions and add Connect. Select Connect on the app’s card and approve the Teams identity check, then refresh connected installations in Doorbell.
5. Set up or edit a named agent. Select the linked installation as an input, choose optional conditions and fields to share, and save sample previews. Several agents can select the same installation.
6. Test the receiver and approve activation, then send a fresh private message or structured channel @mention. Check the Teams receipt, retained message, and receiver history separately.

Important limits

• Only newly created personal messages to the app and direct app @mentions in standard channels are supported. Ordinary channel text, group chats, private channels, and shared channels are outside this first version. Do not add the app to a private or shared channel for routing.
• Messages route only to agents owned by the linked sender. Installation alone does not authorize every member to route; each customer links their own Teams identity. The app acknowledges capture and does not post the receiving agent's eventual response into Teams.
• Forwarding to the personal bot is a planned path, but live delivery has not been verified. Do not rely on Forward for this pilot.
• Details to include can select message text, verified sender, an exact message link when available, and observed attachment descriptors. Attachment metadata can omit items visible in Teams; file contents and download links are not implemented.
• A later edit or deletion does not add, retract, or change a captured event. A five-minute Connect challenge works once; start again if it expires.
• A source receipt confirms capture, not notification delivery or completed agent work. Grouping, quiet periods, cooldown, overflow handling, and receiver handoff follow the agent's notification settings.

Troubleshooting

• If the Teams card says Not configured, the service operator must supply the Teams app configuration. If Teams says the app cannot be found from an installation link, use the package download and custom upload path or ask your Teams administrator whether the catalog app is available under its app policy.
• If a channel message gets no receipt, verify the app is installed in that team and choose it from the @mention suggestions. Typing its name as plain text does not address the app.
• If Connect does not link the installation, verify the same Microsoft tenant and user in Doorbell and Teams, then request a new Connect card. An expired, replayed, or different user’s challenge cannot link it.
• If Teams acknowledged a message but no notification arrived, inspect the sender's linked installation, the agent's active inputs, conditions, notification timing, and receiver evidence. One customer's setup cannot route another sender's message.
• If the app was removed, the installation becomes unavailable until it is added again. Other selected sources can continue; pending Teams detail can become unavailable after removal.