Troubleshooting

Webhook health fails

• Reconnect the bot token. Health checks Telegram’s webhook URL against /tg/{locationId} on the Optigram API host.
• Confirm the location is not disabled (Marketplace uninstall stops relay even if a token is still stored).
• Create the bot with BotFather; a revoked token fails getMe and will not stay connected.

Sends fail with no_telegram_optin

That contact has no active Telegram mapping. Generate an opt-in link (contact-bound if you already have the GHL contact) and have them tap Start. Do not try to “just send” — Telegram will refuse a bot-initiated chat.

Media did not come through

MVP is text-first. Inbound photos are supported; voice, video, and documents may show as a placeholder. Outbound attachments from GHL are not sent as Telegram files yet. Full media parity is deferred.

Reading status in the dashboard

Open Optigram → message logs. Outbound rows show delivered vs failed (including no_telegram_optin). Usage shows recent counts and the 30/s and 1/s ceilings. Logs do not include message bodies.

Phantom phone on the contact

Expected for custom providers. Use the Telegram Handle custom field. See Install & connect.