Skip to main content

Connect a MAX bot

Connect your MAX bot to receive customer messages and reply from the same Evercom inbox used for your other channels. Workspace owners and admins can manage the connection.

  1. Get your bot token from MAX for Business.
  2. Open Settings → Channels → Add → MAX.
  3. Paste the token and click Connect.

Evercom checks the token, loads the bot name, and automatically registers its webhook. The connected channel shows the webhook URL; you do not need to paste it into MAX settings. Keep the bot token private.

Ask a customer to open the bot and send a message. The conversation appears in Evercom; replies sent from that conversation arrive in MAX. Images, videos, audio, and documents appear as attachments after downloading completes.

Sending replies​

  • Text can contain up to 4000 characters.
  • Send up to 12 images/videos together, or one document/audio attachment.
  • Each outgoing attachment can be up to 50 MiB.
  • Select a message to send a quoted reply.

If MAX rejects a message, its delivery status explains the problem and offers the normal retry action. Sent MAX messages currently cannot be edited or deleted from Evercom. Failed messages can be corrected and retried.

Reconnect or disconnect​

If a token is revoked, reconnect the channel with the new token. Evercom updates the existing bot connection and webhook. A failed connection attempt preserves the previous working settings.

Removing the channel unregisters its webhook and removes the saved credentials. Conversation history stays in Evercom. Reconnect the same bot to resume messaging.

For self-hosted administrators​

CHANNEL_WEBHOOK_BASE_URL must be a publicly reachable HTTPS origin on port 443 with a trusted TLS certificate. A local development hostname cannot receive MAX events. The callback has this form:

https://your-webhook-host/webhooks/v1/max/workspace-id/bot-id

The bundled MAX client includes the official root certificate needed by the current MAX API. TLS certificate verification remains enabled.

See MAX API documentation for provider requirements.