MAX is a first-class messenger for a large Russian-speaking audience. This landing is a MAX bot you can operate: Bot API, commands, keyboards, webhooks, retries, and a sidecar API in TypeScript on Node.js. The combined VK and MAX page stays an overview. Telegram bots are a different platform with different limits—shared business logic, separate adapters.
I treat MAX like any production channel: secrets out of git, HTTPS webhooks, structured logs, rate-limit backoff, and a human handoff when the scenario ends. A bot can send a payment link; a full cart still belongs on store checkout. CRM writes go through APIs—see CRM integration and Bitrix24 / amoCRM.
Typical first slice: notifications + one transactional flow (status, appointment, lead capture). Mini-apps and rich UI, if needed, stay on mini-apps and scenarios. AI answers on your docs are RAG plus a MAX adapter, not a prompt pasted into the webhook.
Live messenger practice: My Dev News, cursor-telegram-integration, thinklens-bot. Those are Telegram-heavy; the engineering (Docker, webhooks, idempotency) transfers. MAX-specific constraints (moderation, attachment types, user identity) go in the brief before coding.
Timeline: a focused MAX MVP is often 3–6 weeks after bot credentials and a written scenario list. Multi-channel (MAX + VK + Telegram) adds adapter time, not a 3× rewrite of the core.
What you get
- Scenario map, command list, and “bot must not do”
- Webhook service, queues for slow CRM calls, staging bot
- Runbook: rotate token, read logs, disable the bot
- Short hypercare after go-live
