Supported Channels
Employees can reach the Leena AI virtual assistant in two ways: through Leena channels, the apps and surfaces built and hosted by Leena AI, and through external channels, the collaboration and messaging tools your organisation already uses.
For each channel below, the Experience page describes what employees see and what the channel can and can't do. The Setup page covers what an admin configures in the Admin Console.
Choosing a channelThe Web App is the reference experience. Most external channels trade some capability (buttons, tables, forms, file uploads) for reach, and each external channel's experience page includes a side-by-side comparison with the Web App.
Leena channels
Configured in Admin Console → Leena Channels.
| Channel | What it is | Experience | Setup |
|---|---|---|---|
| Web App | The full assistant in a browser, reached through your assistant's own URL. | Understanding the interface | Settings · Web authentication |
| Desktop App | Windows application, available as the common Leena AI app (updates automatically) or a custom-branded build. Required for IT Automation (Device Genie). | Desktop App | Apps authentication |
| Mobile App | Leena AI app for iOS and Android, downloaded from the App Store or Google Play. | Mobile App | Apps authentication |
| Widget | Embeds the assistant in your intranet, portal, website or your own mobile app through a JavaScript snippet. | Widget | Widget config |
Settings shared across Leena channels
| Page | What it covers |
|---|---|
| Language | Override interface text (button labels, headings, prompts) in each enabled language |
| Other auth settings | Authentication settings shared by web and app sign-in |
| SAML apps | The SAML apps that web and apps authentication select from for SSO |
| Google SSO Config · Azure AD SSO Config · AD SSO Config | Identity-provider configuration guides for SSO sign-in |
External channels
Configured in Admin Console → External channels.
| Channel | What it is | Experience | Setup |
|---|---|---|---|
| Microsoft Teams | The Tab App embeds the full Web App inside Teams. Notifications arrive in the employee's Activity Feed. | Teams | Teams setup |
| Slack | Direct messages, Slack's Assistant tab, or @mentions in channels and group DMs, with answers streamed as they generate. | Slack | Slack setup |
| Google Chat | For Google Workspace organisations. Employees message the app directly or add it to a space. | Google Chat | Google Chat setup |
| Reaches frontline and deskless employees on their phones. Opt-in and WhatsApp's 24-hour messaging window apply. | WhatsApp setup | ||
| Workvivo | The assistant as a chat bot inside Workvivo. Responses are sent as plain text. | Workvivo | Workvivo setup |
| SMS | Employees text the assistant's number. No app, login or data connection needed. | SMS | Voice & SMS setup |
| Phone call | Employees dial the assistant from any phone, and can be transferred to a person mid-call. | Phone call | Voice & SMS setup · Voice (Orchestrator) |
SMS and phone call share one numberBoth are set up together on Voice & SMS setup. Configure SMS before enabling phone call in production: the assistant sends links to callers by text, and without SMS those links are never delivered.
Related pages
- Group Chat Agent for Slack — how @mentions in Slack channels work and the extra scopes they need
- Data Visibility for Leena AI Microsoft Teams Tab App — what Microsoft can and can't see when the Web App runs inside Teams
- WhatsApp logs — delivery troubleshooting for WhatsApp
- Network Requirements for Streaming Responses — proxy and network settings needed for streamed answers
- Voice Call — the in-app voice call, as distinct from the phone call channel
- Voice Architecture — how in-app voice and phone call work behind the scenes
Updated about 1 hour ago