Telegram setup
Your only conversational surface is a Telegram bot dedicated to your workspace. The bot is registered during provisioning and pointed at your VPS. No central server proxies the conversation.
What you’ll receive
After provisioning your operator emails you:
| Item | What to do with it |
|---|---|
| Bot username | Search for it in Telegram and tap Start. |
| Dashboard URL | https://<your-id>.hanai.systems — bookmark it. |
| Operator contact | The person to message if the bot stops responding. |
First message
Open Telegram, find the bot, and send any greeting. The bot replies. You are now in the onboarding phase.
What works in chat
- Plain text messages.
- Voice notes and audio — transcribed on your VPS before reply. See Voice messages.
- Video notes — audio is transcribed; visual content is ignored.
- File attachments such as PDFs and images — extracted by the document and OCR capabilities when relevant.
There are no custom slash commands beyond Telegram’s defaults. You speak to the AI COO in natural language. If you want it to do something, ask it.
Bringing your own bot token
If you prefer to own the bot in your own BotFather account, hand the token to your operator before provisioning. They drop it into your vault during step 9 of setup. Otherwise we register a fresh bot under our operator account and transfer ownership on request.
After setup: the BotFather step
Your operator runs /setdomain <your-id>.hanai.systems once against the bot. This is what lets the dashboard’s Telegram Login Widget verify you. Without it the dashboard displays “Bot domain invalid”.
Privacy
- The bot only responds to authorised user IDs configured during provisioning.
- Conversation history lives on your VPS at
/var/hanai/state/coo-history.jsonl. See Where your data lives. - Telegram itself sees the messages in transit; the contents at rest are on your hardware.
Next
- The onboarding phase — what the first conversation looks like.
- Live mode — the daily loop.
- Voice messages — speak instead of type.