Telegram troubleshooting

Telegram integration usually works without issues, but sometimes problems arise. Solutions here.

"Not getting messages"

Check

1. Connection status: Connect → Telegram → Connected (green)?
2. Trigger config: Trigger settings → questionable event enabled?
3. Quiet hours: Was event during quiet hours? (Then delayed.)
4. Bot mute: In Telegram bot chat, notifications muted?

Fix

• After toggle checks, if still no message → SuperAdmin support.

"Connection token expired"

Problem

Bookinda-generated connection token expires after 10 minutes.

Fix

1. Bookinda → Connect → Telegram → again "Connect with Telegram" button
2. New token + new deep link
3. New /start in Telegram

"Bot doesn't respond to /start"

Problem

Bot username wrong, or token format invalid.

Fix

• Verify deep link correct format: https://t.me/{botUsername}?start={token}
• {botUsername}: platform-level bot name (marked in Bookinda UI)
• {token}: exactly what Bookinda generated
• Copy + paste, don't type

"Bot sends new message but not visible in Telegram"

Problem

Telegram app notifications rules blocking.

Fix

• Telegram → Settings → Notifications → Bot messages enabled?
• iOS: Settings → Notifications → Telegram → enabled?
• Android: similar

"Daily digest not arriving"

Problem

Daily digest off, or stored daily value already gone today.

Fix

• Connect → Telegram → Settings → Daily digest ON
• Digest goes once daily (at set time)
• If set time already passed today, you get tomorrow

"Trigger toggle doesn't save"

Problem

Browser cache or frontend bug.

Fix

• Ctrl+F5 (cache refresh)
• Logout + login
• Try another browser

"Sends same to multiple users"

Problem

Multiple users connected, all triggers on.

Fix

• Per-user filtering: only Owner gets digest, Reception only online bookings.
• Trigger config fine-tuning.

Audit trail

TelegramMessageLog table records every send:

• Timestamp
• Trigger
• User (chat ID)
• Success / failure (SENT / FAILED)
• Error message (if failed)

Accessible in SuperAdmin UI (for dispute resolution).

Re-connect

If connection completely broken:

1. Bookinda: Connect → Telegram → user row → Disconnect
2. Telegram: in bot chat /stop (optional)
3. Bookinda: new connection (new token + deep link + /start)

Telegram bot queries

In Telegram UI bot supports:

• /status: current connection status, trigger counts
• /help: command list, documentation link
• /stop: end connection

When to use it

Scenario 1, customer dispute Customer complains: "Booking confirmation not received." Telegram message absence isn't relevant (customer doesn't get Telegram message, it's salon-internal).

Scenario 2, connection dispute Salon owner complains: "No Telegram messages for 1 week." Status check → Connection ERROR (token expired). Re-connect.

Scenario 3, trigger overload Owner complains: "Daily 50 Telegram messages." Trigger config fine-tuning (only important events).

Scenario 4, group chat noise Telegram group reception staff. Team complains: "Too many messages." Group-level trigger selection (only online bookings).

Scenario 5, daily digest error Daily digest set 21:00 but doesn't arrive. Quiet hours 21:30-09:00 → 21:00 digest still before quiet hours. Check quiet hours start (set 22:00 or later).

Tips

• Status check always first step, don't rush.
• Trigger config worth fine-tuning yearly, as salon strategy changes.
• Telegram app notifications rule is common problem, check first.
• Re-connect is harmless, old data stays.
• SuperAdmin log is dispute-resolution base, always requestable.
• Daily digest and quiet hours interaction: digest before quiet hours starts.

Related articles

• Overview
• Connection
• Triggers
• Daily digest