> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yo-lead.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MAX

> Understand MAX bot conversations, start payloads, and attachments.

Connected MAX bots use `ticket.channel.type: "max"` in webhooks. Bots are connected and managed in the YoLead UI. Contact identities can include `max_user_id`, `max_username`, and `max_phone`; storing an identity does not enable a new outbound conversation.

## Messages and sending

Employees can reply to existing MAX chats. In Embed, replying requires `showSendInput` and the usual employee, channel, and ticket access. Starting a new conversation from a contact or external recipient is unavailable.

An incoming bot-start event appears as a message with `Запуск бота`, followed by its payload when available. If the event creates a ticket, that payload can be exposed as `ticket.attribution.payload`. See [Ticket attribution](https://docs.yo-lead.com/concepts/ticket-attribution.md).

## Attachments and history

Incoming messages can contain the common [attachment descriptors](https://docs.yo-lead.com/concepts/message-attachments.md), visible in Public API ticket history and message webhooks.

Employees can send up to five JPEG/PNG photos or one document in an existing chat. Photos and documents cannot be mixed. Photos support up to 10 MiB per file, documents up to 20 MiB, and captions up to 4000 characters. Storage settings can lower file limits. See [Embed capabilities](https://docs.yo-lead.com/embed/capabilities.md#attachments).

History contains messages stored by YoLead. Attachment metadata does not guarantee that the underlying file remains available; storage and provider availability still apply.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.