Skip to main content

Frequently Asked Questions

These questions typically come up during console configuration and first-time integration.

Common Issues​

Why can't I add my Bot to a group after creating it?​

Check whether the "Allow searching or direct group joining" toggle is enabled in the Bot configuration. If it's disabled, group owners or admins cannot directly invite the Bot to a group from the client. Also, if the target group has end-to-end encryption enabled, the Bot cannot process messages in that group.

Why isn't my command working?​

Check the following:

  • Has the Bot joined the group? — The Bot must be in the target group to respond to commands
  • Is the command format correct? — You need to include the @yourbot suffix (e.g. /help @yourbot)
  • Is group encryption enabled? — The Bot cannot receive message events in end-to-end encrypted sessions
  • Scope of effect — Check whether the command's scope covers the current group
  • Default reply configured? — If you only set a callback URL but the server didn't respond correctly, the command may not work

Why does my script break after resetting the token?​

After resetting the token, the old bot_token becomes invalid immediately. All scripts or services using the old token need to be updated with the new one.

When should I use the console vs. the API?​

  • Console: Best for quickly experiencing the flow, testing commands and default replies, and managing basic Bot info. No coding required to get a Bot running.
  • API: Best for production scenarios that need automated messaging, callback processing, and deep integration with your own services. After configuring commands in the console, the API enables a complete message loop.