Run Telegram commerce and customer service from one console.
Manage catalogs and bots, answer customer messages, and hand a conversation to a person when the bot cannot finish the job.
Telegram firstMulti-tenantHuman handover
Platform
One workspace for the work behind the bot
Each capability maps to a screen that already exists in the dashboard. No mock data, no invented modules.
- 01
Catalog and products
Keep products, images, and prices in one catalog that the bot reads when it answers a customer.
- 02
Bots and webhooks
Connect a Telegram bot, set its prompt, and register the webhook that delivers each update.
- 03
Shared inbox
Read the conversation, claim it, reply as a person, and return it to the assistant when done.
- 04
Tenants and roles
Separate merchant data and limit each person to the tenants and actions their role allows.
- 05
Analytics
Follow sessions, active users, message volume, and response time, then export the range you need.
Architecture
A conversation keeps one state from Telegram to the inbox
The bot is a transport adapter. The session is the source of truth, which is why a person can pick up exactly where the assistant stopped.
- Per-bot webhook
- Every bot receives its own updates, so one tenant cannot read another tenant traffic.
- Session state
- A session moves between assistant, waiting, human, and resolved without losing its history.
- Tenant isolation
- Catalog, messages, and reports are scoped to the active tenant before a query runs.
From update to answer
Telegram update
A customer sends a message.
Session
State and history are stored.
Agent inbox
A person can claim and reply.
Analytics
Measure the queue, not vanity numbers
The dashboard reads the analytics endpoints that ship with the product. There are no preview numbers on this page.
Sign in to open analytics- Sessions
- Today, this week, and this month, split by tenant.
- Active users
- How many customers are in a live conversation.
- Response time
- The average time between a customer message and the first answer.
- Export
- Download the selected date range as CSV for reporting.
Stack
Built on a small, inspectable stack
The same code path serves the guest page, the dashboard, and the webhook.
Next.js
Server rendering and route handlers in one application.
Drizzle ORM
Typed queries against PostgreSQL with explicit schema.
Tailwind CSS
Utility styles generated at build time, not fetched at runtime.
Telegram Bot API
Webhook updates and outbound replies through the bot adapter.
Bring your Telegram support into one console.
Sign in to a workspace or create an account for your first tenant.