Help center

Support

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

Contact support

Email info@conmant.com. We aim to acknowledge support messages within two business days.

What to include

  • The product surface: Bitrix24, Telegram, web archive or meeting provider 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

Confirm that the same Zoombot user has an active meeting-provider connection. Disconnect and authorize again only if the connection is reported as expired. A beta integration may require the provider account to be an approved tester.

The application is small inside a chat

Open the full Zoombot slider from the chat application menu. On mobile, use the application context menu and allow the embedded view to finish loading.

A report did not return to the chat

Confirm that the original message still exists and that Zoombot remains authorized to update it. Processing begins only after the meeting provider reports the relevant meeting or recording event.

A meeting is missing

Zoombot 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 Zoombot data, email info@conmant.com with the subject "Zoombot 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 Zoombot 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.