Help center

Support

Setup help, troubleshooting, privacy requests and direct contact with the developer.

Contact support

First, confirm that you are using the official bot: @zoom_tele_bot. For direct help, email [email protected]. We aim to acknowledge support messages within two business days.

What to include

  • The product surface: Telegram bot, web archive or Zoom authorization.
  • The approximate time and time zone when the issue occurred.
  • The step you performed and the message shown on screen.
  • A screenshot with meeting links, access tokens, personal messages and confidential content removed.
Never send passwords, OAuth codes, access or refresh tokens, private host links, raw recordings or confidential transcripts by email.

Common troubleshooting

The meeting list does not load

Open @zoom_tele_bot, send /start and confirm that the Zoom controls appear. Reconnect only if the connection is reported as expired. A beta integration may require the Zoom account to be an approved tester.

The inline picker does not appear

In the target chat's message field, type the full username @zoom_tele_bot followed by a space. Wait for the result list and tap one item; do not send the typed username as a normal message.

A report did not return to the chat

Confirm that the original meeting card still exists. Processing begins only after Zoom reports the relevant meeting or recording event, and the same card is updated when the result is ready.

A meeting is missing

conmant.com lists meetings owned by the connected user. Meetings owned by another colleague are intentionally not shown.

Privacy and deletion requests

To request access to or deletion of your conmant.com data, email [email protected] with the subject "conmant.com privacy request". State which connected service you used and the user email associated with that service. We may ask for a verification step before acting.

You can also revoke conmant.com directly from the provider's marketplace. A valid provider deauthorization event removes the corresponding provider connection and local provider data.

Security reports

For a suspected vulnerability or security incident, follow the responsible disclosure instructions on the Security page. Do not include exploit details in a public issue or group chat.