Channels · Operational entry points
One Assistant. Every approved channel.
Tellexa Assistants operate across WhatsApp, Telegram, the web portal, voice and phone, under one identity, one set of permissions and one audit trail.
Channels change. Accountability does not.
Assistants
Manage and monitor your AI Assistants
Anna
RunningAn extension of you — personal, not shared.
1 / 3.0k credits
- Calendar helper running
- Inbox helper running
- Research helper running
The channel layer
Conversations become part of how work gets done.
People work across many channels: a WhatsApp message from a client, a Telegram command from a colleague, an after-hours voice call. For AI to operate in real workflows, it must be present in those channels while preserving context, permissions and accountability.
Tellexa treats every channel as an approved operational entry point. The same identity, scope, approval gates and audit trail apply wherever the interaction begins.
The principle
Every channel follows the same rules.
Channels
Work can begin in any approved channel.
CH · 01
The conversational channel most teams already operate on. Tellexa treats inbound WhatsApp messages as first-class events, interpreted, scoped to the assigned Assistant and run against the same permission and approval rules as any other channel.
Available-
Voice notes & media
Speech and images interpreted, transcribed and routed through the same permission pipeline.
-
Document handling
Receipts, contracts and forms classified and filed against the user's permitted scope.
-
On-the-go authority
Sensitive actions still hit the approval queue, regardless of where the request came from.
-
Full audit
Every message, action and approval is recorded with timestamp and actor identity.
CH · 02
Telegram
A precise command channel for operations-led teams. Structured slash-commands, rich list responses and a desktop-grade interaction model, all routed through the same permission and approval layer as every other channel.
Available-
Command shortcuts
Structured commands map to permitted Assistant actions. Unknown or out-of-scope commands escalate.
-
Structured responses
Task lists, tables and status blocks render natively for high-density information work.
-
Multi-device parity
Same identity and audit history across desktop, mobile and web Telegram clients.
-
Approval prompts
Sensitive operations trigger inline approval prompts within the same chat thread.
CH · 03
Web portal
The full operational dashboard. Configure Assistants, review approval queues, inspect audit trails and manage permissions. This is where administrators and operators run the platform.
Available-
Assistant configuration
Define roles, scopes, tools and approval policies for each Assistant.
-
Approval queues
Review, approve or reject pending sensitive actions across all channels in one place.
-
Audit log
Filter and export every Assistant action, message, approval and escalation event.
-
Permissions & users
Manage user access, scope Assistants by department, and adjust permission levels.
CH · 04
Voice
Natural spoken interaction inside the browser. Hands-free operation for moments when typing is impractical, interpretation, response and any resulting actions still flow through the standard permission layer.
Available-
In-browser voice
No app install. Open the portal, speak, the Assistant responds in voice or text.
-
Transcription on record
Every voice interaction is transcribed and stored in the same audit log as text channels.
-
Hands-free authority
Sensitive instructions trigger the same approval gates as any other channel.
CH · 05
Phone
Inbound voice as a first-class channel. Tellexa Assistants answer calls, capture intent, log every interaction and escalate to the right human when the scope or approval boundary is reached.
Coming soon-
Inbound call answering
The Assistant takes the call within its configured scope and operating hours.
-
Intent capture
Caller intent is structured, recorded and matched against the Assistant's permitted actions.
-
Human handoff
Out-of-scope or sensitive calls escalate live to a human, with full context handed over.
Consistency
One permission layer.
Every channel.
Regardless of where an interaction begins, the same rules apply. Channels are entry points; they do not change the Assistant's identity, scope or accountability.
| What stays the same | Across every channel |
|---|---|
| Assistant identity | Same Assistant, same role, same scope, whether reached on WhatsApp, web or voice. |
| Permissions | Read, draft, send, update and escalate boundaries apply uniformly. |
| Approval gates | Sensitive actions reach the approver, no matter where the request originated. |
| Audit trail | One unified log, message, action, approval, escalation, timestamp, actor. |
| Memory & context | A conversation that starts on WhatsApp continues coherently on the web portal. |
| Escalation routing | The same human decision-maker is reached regardless of channel. |
A channel is an entry point.
Tellexa is the layer beneath.
Get started
See your Assistant
on every approved channel.
Request a demo to walk through the full channel layer, one Assistant, every approved channel.
Telegram
Tellexa Sales
4 members
Schedule a call with John tomorrow 10am and send the brief.
14:32 ✓✓
Skye · Sales Assistant
Slot is open in both calendars. Brief from last week ready to attach. Confirm to send?
14:33
Anna · Personal Assistant
online
Summarise my unread emails from today.
16:34 ✓✓
3 emails need attention:
- • 2 from clients on Q3 proposal
- • 1 finance approval awaiting sign-off
16:35
Show today's schedule and any conflicts.
4 meetings today, no conflicts.
- 10:00 · Design review
- 13:00 · Focus block (auto-set)
- 15:00 · Board prep
- 16:30 · Vendor call
Type a message…