Telegram alerts (SuperAdmin)
Bot connection, critical events, OAuth setup, test message
Telegram alerts
The Telegram channel is the SuperAdmin (platform owner) tool. Critical events that matter at the salon-business level (SMS sending failing, payment provider down, waitlist over 100) arrive via Telegram.
Where to find it
SuperAdmin → Notifications → Settings → Telegram section.
Connection (OAuth)
Steps
- Click "Connect Telegram bot"
- Bookinda generates an OAuth URL
- Open it, allow the bot into your Telegram
- Return to Bookinda → status: "Connected"
What we store
- Your Telegram chat ID
- Bot username (e.g.,
@bookinda_alerts_bot) - Connection date
Test message
"Send test message" button: sends you a test, to verify it works. Expected: appears in Telegram within seconds.
What the bot sends
Only critical events:
- SMS sending repeated failure (3+ in a row)
- Payment provider (Stripe / Barion) unavailable
- Waitlist exceeds threshold (e.g., 100)
- Email tracking anomalies (lots of bounces, send errors)
- Platform-level critical alert (Bookinda's own failure)
- New SuperAdmin login (security alert)
Details are configurable in SuperAdmin → Notifications (which events to send).
When to use it
Scenario 1, you're the salon owner and want immediate critical alerts Telegram bot connected. Twilio SMS is failing? Telegram message arrives. You know in 30 seconds and act.
Scenario 2, multi-tenant platform owner Many salon tenants on your platform. Critical error in one tenant? You know before the tenant calls you.
Scenario 3, hot-on-call engineer Platform engineer. Watch Telegram alerts. Faster than email.
Scenario 4, team channel A team Telegram group, bot sends alerts there. Everyone sees, someone responds.
Disconnecting the bot
Settings → Telegram → "Disconnect" button. Bot no longer sends.
Privacy
The Telegram bot is SuperAdmin-only, not available to salon owners (tenants). Salon owners get email/in-app notifications.
Tips
- Connect early, before a critical failure. Don't fight OAuth in a panic.
- Test message verification is mandatory, otherwise you discover after 1 month it wasn't working.
- Bot should send too few alerts, not too many. One per day is fine, 5 daily alerts is annoying, you'll mute it, and miss the important ones.
- Don't send every tenant event to Telegram, only platform-level failures. Otherwise overload.
- Team channel: state who's responsible to react, otherwise no one does.
- Remember bot username, so you don't confuse with other bots.