01
Meta messaging
WhatsApp, Instagram Direct, and Messenger use verified Meta webhook events and provider APIs.
Connected customer channels
Keep the customer’s channel. Bring the support work together.
Website, WhatsApp, Instagram, Messenger, Telegram, and support email feed one tenant-scoped inbox with provider verification and source-aware replies.
Connected channels
Illustrative product motion
Website
Telegram
One queue
Source retained
Provider verification happens before routing.
Managed AI execution flow
Verified provider events enter one queue without losing their source.
System view
Signals in
01WhatsApp
02Telegram
03Email
Channel Router
Verified events
Outcomes
01One queueSource-aware replies
What breaks
Separate provider inboxes split customer history and make ownership, automation policy, and reporting inconsistent.
The operational change
Every supported provider maps inbound events into one conversation model while preserving delivery through the original channel.
Product view
Keep every channel visible inside one routing system.
Illustrative layout of the shipped workflow. Live workspace screens use tenant data and permission checks.
Route every verified channel into one queue
Instagram Direct · product workflow
Website
Verified source
Signed provider event
One operational inbox
Customer, source, ownership, and delivery stay attached.
Telegram
Bot verified
Support email
Thread retained
The conversation keeps its Instagram source.
Capability map
Built around this job.
Every surface below maps to a working product state, server action, or provider-backed workflow.
02
Telegram
A validated Telegram bot receives messages and sends agent or eligible AI replies.
03
Support email
Brevo turns inbound email into threaded tickets and delivers outbound replies.
04
One queue
Source, customer, status, ownership, and conversation history stay visible to the workspace.
Working sequence
From provider event to reply.
- 01
Connect
An owner completes the provider-specific setup.
- 02
Verify
Evnao validates credentials and signed inbound events.
- 03
Route
The message becomes a tenant-scoped conversation.
- 04
Reply
AI or a human responds through the same provider.
Bring the channels together without hiding them.
See how a verified provider event enters one queue and keeps its delivery state.