Microsoft Teams experience

Teams gives employees the fullest experience of any external channel, because the Leena AI Tab App embeds the complete Web App inside a Teams tab. Parallel chats, the side menu, ticket history, workflow forms, the employee directory, theming, language settings — all of it, without leaving Teams.

This is the experience every current deployment gets.

For app registration, tenant setup and installation, see Teams setup.

The Tab App

Employees open the Leena AI tab in Teams and get the Web App interface in place. Because it is the Web App, the capability question mostly disappears: what works in a browser works here.

That includes the things other external channels cannot do at all:

• Chats — multiple parallel conversations with auto-generated titles and unread counts.
• Streaming and thinking state — answers appear token by token, with visible progress while the assistant works. See Streaming & Thinking State.
• Full webviews — raising a ticket, completing a workflow form, browsing knowledge, searching the directory, all as full pages rather than cramped dialogs.
• Native tables and rich formatting, copyable and searchable.
• Voice call — see Voice Call.
• Branding, theming and in-app language selection.
• Typing indicators and read receipts.

Employees are recognised by their Microsoft directory identity within your tenant, so there is no separate login. If someone leaves and is marked terminated in your HR system, the assistant stops responding on their next interaction.

Native chat alongside the tab

You can decide whether employees still receive messages in their Teams chat list as well, or whether everything funnels into the tab.

When the tab is the primary surface, buttons in cards sent to native chat are rewritten to open the Tab App rather than handling the interaction in chat — so a click bounces the employee into the tab where the full interface is available. Webview buttons are the exception; those stay as dialogs so they can resolve the correct destination.

Notifications

Teams notifications are delivered to the employee's Activity Feed through the Leena AI Teams app — the same place they see mentions and replies. They are not chat messages, so they don't add to the employee's unread chat count.

Two things matter operationally:

• Activity feed sends are paced to stay inside Microsoft's throttling limits, at roughly four notifications per second per tenant. A large announcement to thousands of employees is delivered steadily rather than all at once, so the last employee receives it noticeably later than the first.
• A notification can only reach an employee who has the Leena AI Teams app installed. Installation can be pushed to an Azure AD group, to a list of email addresses, or to the whole organisation.

Files and media

Employees can send files and attachments to the assistant in Teams, and receive them back.

Files the assistant sends are delivered as publicly reachable links rather than expiring ones, because Teams does not accept temporary or authenticated URLs. This is a meaningful difference from Slack, WhatsApp and Workvivo: a document link copied out of Teams keeps working. Factor that into how you handle genuinely sensitive documents.

Native chat (legacy)

Only relevant if your bot predates the Tab App. Everything here is a constraint the Tab App does not have.

In native chat the assistant behaves as a conventional Teams bot in the chat list, and responses are rendered as Adaptive Cards:

• Tables cannot be rendered natively, so they are converted into images — not copyable, not searchable.
• Images are automatically resized to fit within 1024×1024 pixels.
• Audio and video can't play inline in a card, so they become an Open Media button that launches the file in a secure webview.
• Where one answer would produce several cards, they are merged into a single payload so the employee gets one notification instead of several.
• Webviews open as task modules — a dialog over the chat, rather than a full page.

Interaction limits in native chat

Teams has no native quick-reply concept, so quick replies render as buttons that submit the chosen text back into the conversation.

There is also no streaming, no typing indicator, no read receipts and no parallel chats in native chat.

Compared with the Web App

The Tab App matches the Web App on essentially every row. That is the argument for it.

Things to tell your employees

• The Leena AI tab in Teams is the full assistant. Start there rather than messaging it in your chat list.
• Notifications land in your Activity Feed, not your chat list.
• Documents the assistant sends stay reachable by link, so treat them as you would any shared file.

Setting up the channel

App registration, tenant configuration, Tab App settings and bulk app installation are covered in Teams setup.