Skip to main content
YoLead can use a connected email mailbox as a company channel. Incoming messages are received from the mailbox, and employees can start or continue email conversations from the YoLead UI and embedded iframe. Email is exposed through the existing integration surfaces:
  • webhook tickets use channel.type: "email";
  • webhook clients can include email;
  • webhook and Public API history messages can include subject and attachment descriptors;
  • the Embed outbound composer can start email conversations when startOutboundChat is enabled.

​
Chats and recipients

An email chat is identified by the connected company mailbox and the client’s normalized email address. The same client address in two connected company mailboxes creates two separate chats. For an incoming message, YoLead uses a single valid Reply-To address as the client identity when one is present. Otherwise it uses the From address. The original From address remains available as the message fromId. Starting an outbound email chat requires a recipient with an email identity. One message is sent to one recipient; multiple To recipients, CC, and BCC are not currently supported.

​
Subjects and replies

A subject is optional when starting a new email chat. The maximum supported subject length is 998 characters. When an employee replies in an existing email chat, YoLead preserves the subject of the latest message and links the reply to that message when its email message id is available. A subject supplied while replying does not replace the existing subject. If the previous message did not have a subject, the reply is sent without one. The subject does not affect chat identity: messages between the same connected mailbox and client email address belong to the same chat and follow the normal ticket restore-period rules.

​
Message content

Email messages support plain-text content, an optional subject, and metadata for ordinary attachments received through the Inbox or discovered through Sent-folder synchronization. Multiple attachments preserve their original MIME order. Inline or related MIME parts such as signatures, logos, and tracking pixels are excluded. Employees can send photos and documents from the YoLead application and embedded iframe, both in existing chats and when starting a new conversation. Up to five attachments are sent as one email and appear as one history message. Photos and documents can be mixed in the same email, and a message with attachments does not require text. JPEG and PNG photos support up to 10 MiB per file. Documents support up to 20 MiB per file by default, and the combined attachment size is limited to 18 MiB before email encoding. YoLead storage settings can lower these limits, and the connected mailbox provider can reject a message under its own limits. Incoming attachments can be opened or downloaded in the YoLead application and embedded iframe while available. Outgoing attachments remain available while their stored copy is retained: the default retention is 30 days, and storage cleanup can remove a file earlier. Outgoing files are not automatically recovered from the mailbox after their stored copy is removed. The following content is not currently available through YoLead’s public integration surfaces:
  • HTML message bodies as HTML;
  • multiple recipients, CC, or BCC.
Incoming HTML is converted to text for the message body when needed. Webhook and Public API messages expose attachment descriptors, but the Public API does not provide an API-key-authenticated endpoint for downloading the underlying files. Attachment metadata is available only for messages processed after attachment support was enabled; existing messages are not backfilled. See Message attachments.

​
Public integration fields

Email mailbox connection, authentication, and credential management are performed in the YoLead application. They are not part of the public /v1 REST API.