Getting started
Create an account, connect a Telegram number, and send your first auto-reply in about five minutes.
Prime Bot is a managed Telegram auto-reply platform. You keep your own Telegram account; we drive the inbox on your behalf using the rules you configure. This page walks you through the initial setup.
1. Create an account
Sign up at /user/register with an email address and a password. You'll land in the dashboard with an empty workspace and no connected accounts yet.
2. Connect your Telegram account
Open Accounts → Connect Telegram from the sidebar. You have two options:
- QR code — scan from the mobile Telegram app (Settings → Devices → Link Desktop Device). Fastest path if your phone is handy.
- Phone number — enter your number, wait for the SMS/Telegram code, then submit it. A 2FA password prompt appears if you have one enabled.
Once the account shows a green dot in the list, Prime Bot has an active MadelineProto session and can read/send DMs for that number.
Heads up: Telegram treats rapid account additions as suspicious. If you're connecting a brand-new number, let it sit for 24 hours before sending large campaigns.
3. Build your first campaign
Go to Campaigns → New campaign. The minimal happy path is:
- Pick a name (just for your own reference).
- Choose a mode:
auto_replylistens for inbound DMs,broadcastpushes to a contact list. Start withauto_reply. - Set a trigger keyword (optional). Leave blank to reply to every new DM, or set something like
pricingto only fire on matching messages. - Attach the Telegram account you just connected.
- Write the reply body. Markdown-style formatting is supported.
- Click Save & Start.
4. Verify it works
From a different Telegram account, DM the number you connected. Within a few seconds the reply should arrive, and a new row appears under Campaigns → (your campaign) → Logs.
# Or poll the API to see the log appear:
curl -H "Authorization: Bearer $TOKEN" \
https://prime-bot.live/api/v1/campaigns/1/logs
Next steps
- Core concepts — how campaigns, sequences, and followups fit together.
- API authentication — issue a Sanctum token for programmatic access.
- Webhooks — receive events in real time instead of polling.