Telegram bot token (2 minutes)
Unlocks: the entire product loop — phone-number login via Telegram OTP, bots messaging you, routines delivered to your chat. Until this exists, the Telegram service stays parked.
Steps
- Open Telegram on your phone or desktop, search for @BotFather (blue checkmark), open a chat.
- Send
/newbot. - Name (shown to users): type
Aquila Assistant— or anything you like. - Username (must end in
bot, globally unique): tryAquilaAssistantBot; if taken, add a suffix likeAquilaAssistantInBot. - BotFather replies with a token that looks like:
8123456789:AAF3xk...long-string...— this is a password. Do not paste it in public chats. - (Optional but nice) In the same BotFather chat:
/setdescription→ "Your business assistant. Ek star jo aapke liye kaam karta hai. ✦"/setuserpic→ upload the Aquila mark when we have one./setcommands→ paste:start - Shuru karein(keeps the chat tidy).
Send back (in our chat)
TELEGRAM_BOT_TOKEN=8123456789:AAF3xk...
TELEGRAM_BOT_USERNAME=AquilaAssistantBot
It lands in the gitignored .env on the POC machine.
What I do next (no action from you)
docker compose up -d telegramwith the token + poll mode.- Send you the test link; you open the bot, tap Share my number — that's the verified login.
- Confirm
aquila exaflairOTP — you'll see the code arrive in Telegram and enter it on the welcome page.
Safety notes
- One bot serves all personas in the POC (messages are labelled VEGA / NOVA / PULSAR / SIRIUS). Per-persona bot identities are a deliberate post-POC item (each needs manual BotFather creation).
- Telegram tokens can be revoked any time via BotFather
/revokeif anything looks off.