diff --git a/_i18n/en/numbers/email-channel-fundamentals.md b/_i18n/en/numbers/email-channel-fundamentals.md
index 673584b3..62a8f384 100644
--- a/_i18n/en/numbers/email-channel-fundamentals.md
+++ b/_i18n/en/numbers/email-channel-fundamentals.md
@@ -3,7 +3,7 @@ Use Email when customers need a message they can receive and reply to in their u
This guide explains everyday use of the Email channel after you have added a sender. For the sender form, DNS records, and domain verification, follow [Set up email sending]({% link _integrations/set-up-email-sending.md %}).
- Email is available on Enterprise. A saved sender must finish domain verification before its channel becomes available for sending.
+ Email is available on Pro and Enterprise. A saved sender must finish domain verification before its channel becomes available for sending.
## What Email is best for
@@ -13,7 +13,7 @@ Use Email for:
- One-to-one customer conversations from the Inbox.
- Detailed answers that benefit from paragraphs and a written record.
- Support and order follow-up with customers who prefer email.
-- Sharing documents, images, and other supported files.
+- Sharing images and information, with links to documents when needed.
- Continuing a conversation after the customer replies to an email sent from Hellotext.
Email does not require the customer to install a messaging app or have a phone number on their profile. You do need the correct email address and permission to contact the customer for the purpose of the message.
@@ -35,7 +35,7 @@ Keep reading: [Customer profiles]({% link _audience/customer-profiles.md %}) and
## Where you can use Email
-The Inbox provides an Email destination for customers with an email address when the business has an active Email sender.
+The Inbox destination menu can show **Email** before sending is ready. To send, you need an address on the customer profile, channel access, and an active sender; seeing the option does not confirm those requirements.
The campaign creator shows Email as a delivery option, but selecting it does not by itself enable sending. To send an Email campaign, the business needs Email access through its subscription and a verified, active sender. Connecting a sender does not automatically change the delivery channels of an existing campaign.
@@ -51,10 +51,22 @@ An email conversation uses three addresses or identities:
| **Recipient** | The customer's address that will receive this message. | The email address you select from the customer's profile in the destination menu. |
| **Reply address** | The address the customer's email application uses when they choose Reply. | Hellotext supplies it automatically so it can associate the response with the conversation. |
-For example, your sender might be `support@acme.com` and your customer might receive the message at `alex@example.com`. The reply address can be different from `support@acme.com`; that is how Hellotext receives the response for the conversation.
+For example, your sender might be `support@example.com` and your customer might receive the message at `alex@example.com`. The reply address can be different from `support@example.com`; that is how Hellotext receives the response for the conversation.
The destination menu lists the customer's email addresses. It is not a list of your business's senders. When you choose an address, Hellotext uses the existing Email conversation's active sender when available, or an available Email channel for a new destination.
+
+
+
+
+
+
+
+
+
+ Real interface with fictional data: choose the customer's intended recipient address under Email.
+
+
If your business has several active senders, verify which one is used before relying on a particular From address. The Inbox destination menu does not currently provide a separate Email sender picker.
To change a sender's name or email address, use its **Edit** action in **Settings > Integrations**. Changing its domain requires verification again. See [Set up email sending]({% link _integrations/set-up-email-sending.md %}) before making that change.
@@ -66,27 +78,53 @@ To change a sender's name or email address, use its **Edit** action in **Setting
3. Open the destination menu beside the message editor.
4. Find the **Email** group.
5. Select the customer's intended email address. If the profile has more than one, choose the address that should receive this message.
-6. Write your message. Use clear paragraphs, add any required links, and attach supported files when needed.
-7. Check that Email is selected before sending, especially if you were previously replying over another channel.
+6. Write the **Subject** and prepare the body in the Email editor. Organize the content into text blocks, adding images or actions when they help the customer.
+7. Open **Preview** to review the desktop and mobile layouts. Check the recipient, subject, text, and links before sending, especially if you were previously replying over another channel.
8. Send the message and review its sending or delivery information in the conversation.
-Selecting one email address sends to that destination. It does not send copies to every email address on the profile. The Email destination menu does not provide CC or BCC fields.
+
+
+
+
+
+
+
+
+
+ Draft with fictional data: review the email subject and body before sending.
+
+
+When you send, only the selected address is used. No copies are sent to the other addresses on the profile. The Email destination menu does not provide CC or BCC fields.
For a customer whose only available destination is Email, Hellotext can open the composer with Email selected when an active sender is available. Always check the destination when the customer also has phone numbers or other connected channels.
-If the Email group is missing, check the profile's email address and the sender's activation before trying to send. A pending domain verification does not provide an active sending channel.
+If you cannot send through Email, check the profile's address, your plan access, and the sender's activation. A pending domain verification does not provide an active sending channel, even if the menu lets you explore the Email option.
Keep reading: [Message editor overview]({% link _numbers/message-editor-overview.md %}).
## What the customer receives
-Hellotext renders the message as an email with the business name, message body, and a footer showing the sender name and email address. It also includes a plain-text version for email applications that use it.
+Hellotext prepares the email from the design you edited. The selected appearance supplies its branding and footer; the sender name and address come from the Email channel. A plain-text version is also included for email applications that use it.
+
+Use **Subject** to write the email title. It is separate from the body and sender name; the sender name does not automatically change to the teammate who clicked Send.
-The current email subject uses the business name. The Inbox composer does not provide a separate subject field for each message. The sender name comes from the sender integration; it does not automatically change to the teammate who clicked Send.
+The body retains the design's blocks, such as text, images, and buttons. Images added to the design appear within the email; they are not automatically offered as downloadable file attachments. Do not rely on copied styling or another channel's controls to appear identically.
-The message body uses the text and paragraph breaks from your message. Do not rely on copied styling, custom HTML, or another channel's interactive controls to appear identically in the email. Files are delivered as email attachments, and the customer's email application controls their preview or download experience.
+Use **Preview** to review the unsent draft and switch between desktop and mobile layouts. Email applications can display the same design differently; a received test message lets you check the final appearance, line breaks, and links.
-The layout adapts to smaller screens, but email applications can display the same message differently. Check an actual received message when evaluating appearance, line breaks, and attachments.
+The preview footer may show **Unsubscribe**. That link is not automatically added when you send a manual email from the Inbox.
+
+
+
+
+
+
+
+
+
+
+ Preview of the draft with fictional data. Switch between desktop and mobile to check how the content is arranged.
+
### Links and personalization
@@ -98,29 +136,21 @@ Keep reading: [Tracked links]({% link _analytics-reporting-attribution/tracked-l
## Text length and attachments
-Email allows longer text than a short chat reply, but the editor still applies limits:
+The Email editor organizes content into blocks. Use its image controls; the file list for other channels does not describe what you can add to this design.
| Item | Limit or behavior |
| --- | --- |
-| **Message text** | Up to 100,000 characters in the Email editor. |
-| **An uploaded image** | Up to 25 MB per file. |
-| **An uploaded document** | Up to 25 MB per file. |
-| **An uploaded audio or video file** | Up to 25 MB per file. |
-| **Several attachments** | Each file must be accepted by the uploader. The complete email must also fit the sending and receiving services' message-size limits. |
-
-An accepted upload is not a guarantee that every recipient's email service will accept the complete message. Several large files can make an email too large even when each file is individually allowed. Use smaller files or share an appropriate download link when a message does not need to carry the full file itself.
-
-Supported file types include:
+| **Subject** | Up to 998 characters. |
+| **Formatted text** | Validated per block; formatting also uses space. Simplify or split a block if the editor rejects its length. |
+| **Top-level blocks** | Up to 30 in the design. |
+| **An uploaded image** | PNG, JPEG, GIF, or WebP up to 5 MB. It becomes part of the email body. |
+| **Documents, audio, or video** | Share an appropriate link; the current Email editor does not offer the general file uploader for these attachments. |
-- **Images:** JPEG, PNG, GIF, WebP, AVIF, HEIC, HEIF, BMP, TIFF, and SVG.
-- **Documents:** PDF, Word, Excel, PowerPoint, OpenDocument files, RTF, plain text, and CSV.
-- **Audio:** supported AAC, MP4 audio, MP3, AMR, Ogg, Opus, WAV, FLAC, and WebM audio files.
-- **Video:** supported MP4, MPEG, 3GP, QuickTime, WebM, and AVI files.
-- **Other files:** supported ZIP, Gzip, EPUB, JSON, XML, HTML, calendar, and contact files.
+The formatted-text limit is not a fixed character count for the entire email. The combined design size is also validated. Keep the message concise and split information into useful blocks without repeating content.
-Choose a supported file type and keep each file within the size limit. If a file is rejected, use a supported export or share a suitable link. Changing only the filename extension does not convert the file.
+Wait for each image to finish loading and check its content in **Preview**. An accepted image does not guarantee that every email service will accept the complete message. Use smaller images when possible.
-Use the attachment control in the composer, wait for the upload to finish, and confirm that the intended files are attached before sending. Review filenames and contents so you send the correct version to the correct customer.
+To share a document or a large file, add a download link and check that the customer has access. Changing only a filename extension does not convert the file to a supported format.
## How customer replies reach the Inbox
@@ -133,7 +163,7 @@ After receiving an email sent from Hellotext, the customer should:
Hellotext associates a supported reply with the original outgoing email, customer profile, and conversation. Your team can then read and answer it from the Inbox.
-A reply can include text and supported attachments. The Inbox shows the reply content and attachments using its usual message presentation. It does not reproduce the customer's complete HTML email layout as a mailbox view.
+A reply can include text and supported attachments. The Inbox retains supported elements of the received email, such as images, tables, and lists, and can group quoted text from earlier messages. Some styles or elements of the original email may appear differently.
### Replies from another address
@@ -143,7 +173,7 @@ When testing replies, use the same address that received the email and leave the
### New emails sent to your existing business mailbox
-Verifying a sending domain does not move an existing mailbox into Hellotext. A new email written directly to `support@acme.com` continues to follow that address's existing incoming-mail setup.
+Verifying a sending domain does not move an existing mailbox into Hellotext. A new email written directly to `support@example.com` continues to follow that address's existing incoming-mail setup.
Sending from that address in Hellotext and receiving replies through the supplied reply address are separate from importing mailbox history or receiving every new email sent to the domain. If you need broader incoming-mail routing, discuss the setup with [Hellotext support]({% link _troubleshooting-deliverability/contact-hellotext-support.md %}).
@@ -204,7 +234,7 @@ If the only destination on the profile is Email and no Email sender is active, t
### The message used an unexpected sender or subject
-The destination menu chooses the recipient. The sender comes from the Email channel, and the current subject comes from the business name.
+The destination menu chooses the recipient. The sender comes from the Email channel; you write the subject in **Subject**. Check that field before sending, including when replying to an earlier email.
Review the sender's name and address in **Settings > Integrations**. If you have several senders, check which channel the conversation used. Contact support if you need help identifying the sender before sending further messages.
@@ -212,7 +242,7 @@ Review the sender's name and address in **Settings > Integrations**. If you have
Confirm the exact recipient address and review whether the message has delivery information or a failure. Ask the customer to check their spam or junk folder as well as their usual inbox.
-If the email is still sending, give processing time to complete. If it failed, review the available reason, correct the destination or content when appropriate, and check the total attachment size before retrying.
+If the email is still sending, give processing time to complete. If it failed, review the available reason, correct the destination or content when appropriate, and reduce images or simplify the design if its size prevents sending.
### The customer's reply does not appear
@@ -222,7 +252,7 @@ Incoming replies must also pass the receiving checks. If a reply still does not
### An attachment fails or looks different
-Check the accepted file type and size, confirm that the upload finished, and try a smaller supported export when necessary. A file's appearance in the customer's email application may differ from its preview in Hellotext.
+In the Email editor, add images through its image blocks. Check that they are PNG, JPEG, GIF, or WebP files up to 5 MB and wait for the upload to finish. A design image appears within the email; its appearance can vary between email applications.
For a large document or media file, consider sharing an appropriate download link. Keep access to the linked file suitable for the intended customer.
@@ -232,8 +262,8 @@ Before your team relies on Email conversations in the Inbox, confirm that:
1. The intended sender is verified and active in the correct business.
2. A test customer's email address is saved correctly on the profile.
-3. Selecting that address sends through Email.
-4. The received message shows the expected sender, business name, text, and attachments.
+3. The selected destination is Email and shows the correct address.
+4. The received test message shows the expected sender, subject, design, images, and links.
5. A reply from the same recipient address appears in the correct Inbox conversation.
6. The right teammate or team takes responsibility for the reply.
7. Your team understands sender selection, delivery information, and the scope of unsubscribe requests.
diff --git a/_i18n/es/numbers/email-channel-fundamentals.md b/_i18n/es/numbers/email-channel-fundamentals.md
index 33b9fd5f..8345f66f 100644
--- a/_i18n/es/numbers/email-channel-fundamentals.md
+++ b/_i18n/es/numbers/email-channel-fundamentals.md
@@ -3,7 +3,7 @@ Usa Correo electrónico cuando tus clientes necesiten un mensaje que puedan reci
Esta guía explica el uso diario del canal de correo electrónico después de agregar un remitente. Para conocer el formulario del remitente, los registros DNS y la verificación del dominio, sigue [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %}).
- Correo electrónico está disponible en Enterprise. El dominio de un remitente guardado debe terminar de verificarse antes de que su canal esté disponible para enviar.
+ Correo electrónico está disponible en Pro y Enterprise. El dominio de un remitente guardado debe terminar de verificarse antes de que su canal esté disponible para enviar.
## Para qué sirve mejor el correo electrónico
@@ -13,7 +13,7 @@ Usa Correo electrónico para:
- Conversaciones individuales con clientes desde el Inbox.
- Respuestas detalladas que necesitan párrafos y un registro escrito.
- Soporte y seguimiento de pedidos con clientes que prefieren el correo.
-- Compartir documentos, imágenes y otros archivos compatibles.
+- Compartir imágenes e información, con links a documentos cuando haga falta.
- Continuar una conversación después de que el cliente responda a un correo enviado desde Hellotext.
El correo electrónico no requiere que el cliente instale una aplicación de mensajería ni que tenga un número de teléfono en su perfil. Sí necesitas la dirección correcta y permiso para contactar al cliente con el propósito del mensaje.
@@ -35,7 +35,7 @@ Sigue leyendo: [Cómo funcionan los perfiles de clientes]({% link _audience/cust
## Dónde puedes usar correo electrónico
-El Inbox ofrece un destino de correo electrónico para los clientes que tienen una dirección de correo cuando el negocio cuenta con un remitente de correo activo.
+El menú de destino del Inbox puede mostrar **Email** antes de que el envío esté listo. Para enviar necesitas una dirección en el perfil del cliente, acceso al canal y un remitente activo; ver la opción no confirma esos requisitos.
El creador de campañas muestra Correo electrónico como opción de entrega, pero seleccionarla por sí sola no habilita el envío. Para enviar una campaña por correo, el negocio necesita acceso al canal según su suscripción y un remitente verificado y activo. Conectar un remitente no cambia automáticamente los canales de una campaña existente.
@@ -51,10 +51,22 @@ Una conversación por correo utiliza tres direcciones o identidades:
| **Destinatario** | La dirección del cliente que recibirá este mensaje. | La dirección de correo que eliges del perfil del cliente en el menú de destino. |
| **Dirección de respuesta** | La dirección que utiliza la aplicación de correo del cliente cuando elige Responder. | Hellotext la proporciona automáticamente para asociar la respuesta con la conversación. |
-Por ejemplo, tu remitente puede ser `support@acme.com` y tu cliente puede recibir el mensaje en `alex@example.com`. La dirección de respuesta puede ser distinta de `support@acme.com`; así recibe Hellotext la respuesta para la conversación.
+Por ejemplo, tu remitente puede ser `support@example.com` y tu cliente puede recibir el mensaje en `alex@example.com`. La dirección de respuesta puede ser distinta de `support@example.com`; así recibe Hellotext la respuesta para la conversación.
El menú de destino muestra las direcciones de correo del cliente. No es una lista de los remitentes de tu negocio. Cuando eliges una dirección, Hellotext usa el remitente activo de la conversación de correo existente, si está disponible, o un canal de correo electrónico disponible para un destino nuevo.
+
+
+
+
+
+
+
+
+
+ Interfaz real con datos ficticios: elige en Email la dirección del cliente que recibirá el mensaje.
+
+
Si tu negocio tiene varios remitentes activos, verifica cuál se utiliza antes de depender de una dirección de origen específica. El menú de destino del Inbox no ofrece actualmente un selector separado de remitentes de correo.
Para cambiar el nombre o la dirección de un remitente, usa su acción **Editar** en **Ajustes > Integraciones**. Cambiar su dominio requiere una nueva verificación. Consulta [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %}) antes de realizar ese cambio.
@@ -64,29 +76,55 @@ Para cambiar el nombre o la dirección de un remitente, usa su acción **Editar*
1. Abre la conversación del cliente en el **Inbox**.
2. Revisa el perfil del cliente y confirma que la dirección de correo sea correcta. Agrega o corrige la dirección en el perfil si es necesario.
3. Abre el menú de destino junto al editor de mensajes.
-4. Busca el grupo **Correo electrónico**.
+4. Busca la opción **Email**.
5. Selecciona la dirección del cliente a la que quieres enviar. Si el perfil tiene más de una, elige la que debe recibir este mensaje.
-6. Escribe tu mensaje. Usa párrafos claros, agrega los links necesarios y adjunta archivos compatibles cuando haga falta.
-7. Comprueba que Correo electrónico esté seleccionado antes de enviar, especialmente si antes estabas respondiendo por otro canal.
+6. Escribe el **Asunto** y prepara el cuerpo en el editor de correo. Organiza el contenido en bloques de texto y agrega imágenes o acciones cuando ayuden al cliente.
+7. Abre **Vista previa** para revisar el diseño en escritorio y móvil. Comprueba el destinatario, el asunto, el texto y los links antes de enviar, especialmente si antes estabas respondiendo por otro canal.
8. Envía el mensaje y revisa su información de envío o entrega en la conversación.
-Seleccionar una dirección de correo envía el mensaje a ese destino. No envía copias a todas las direcciones del perfil. El menú de destino de correo electrónico no ofrece campos CC ni CCO.
+
+
+
+
+
+
+
+
+
+ Borrador con datos ficticios: revisa el asunto y el cuerpo del correo antes de enviarlo.
+
+
+Al enviar, se usa únicamente la dirección seleccionada. No se envían copias a todas las direcciones del perfil. El menú de destino de correo electrónico no ofrece campos CC ni CCO.
Si Correo electrónico es el único destino disponible del cliente, Hellotext puede abrir el editor con ese canal seleccionado cuando hay un remitente activo. Revisa siempre el destino si el cliente también tiene números de teléfono u otros canales conectados.
-Si falta el grupo Correo electrónico, revisa la dirección del perfil y la activación del remitente antes de intentar enviar. Un dominio pendiente de verificación no ofrece un canal de envío activo.
+Si no puedes enviar por Email, revisa la dirección del perfil, el acceso de tu plan y la activación del remitente. Un dominio pendiente de verificación no ofrece un canal de envío activo, aunque el menú permita explorar la opción Email.
Sigue leyendo: [Resumen del editor de mensajes]({% link _numbers/message-editor-overview.md %}).
## Qué recibe el cliente
-Hellotext presenta el mensaje como un correo con el nombre del negocio, el cuerpo del mensaje y un pie que muestra el nombre y la dirección del remitente. También incluye una versión de texto sin formato para las aplicaciones de correo que la utilizan.
+Hellotext prepara el correo a partir del diseño que editaste. La apariencia elegida aporta la marca y el pie del mensaje; el nombre y la dirección del remitente provienen del canal de correo. También se incluye una versión de texto sin formato para las aplicaciones de correo que la utilizan.
+
+Usa **Asunto** para escribir el título del correo. Es independiente del cuerpo y del nombre del remitente; este último no cambia automáticamente al nombre de la persona del equipo que hizo clic en enviar.
-El asunto actual del correo usa el nombre del negocio. El editor del Inbox no ofrece un campo de asunto separado para cada mensaje. El nombre del remitente proviene de su integración; no cambia automáticamente al nombre de la persona del equipo que hizo clic en enviar.
+El cuerpo conserva los bloques del diseño, como texto, imágenes y botones. Las imágenes que agregas al diseño aparecen dentro del correo; no se ofrecen automáticamente como archivos adjuntos descargables. No dependas de que los estilos copiados o los controles de otro canal se vean exactamente igual.
-El cuerpo usa el texto y los saltos de párrafo de tu mensaje. No dependas de que los estilos copiados, el HTML personalizado o los controles interactivos de otro canal se vean exactamente igual en el correo. Los archivos se entregan como adjuntos y la aplicación de correo del cliente controla cómo se previsualizan o descargan.
+Usa **Vista previa** para revisar el borrador sin enviarlo y alterna entre escritorio y móvil. Distintas aplicaciones de correo pueden mostrar el mismo diseño de manera diferente; una prueba recibida te permite comprobar la apariencia final, los saltos de línea y los links.
-El diseño se adapta a pantallas más pequeñas, pero distintas aplicaciones de correo pueden mostrar el mismo mensaje de manera diferente. Revisa un mensaje recibido real para evaluar la apariencia, los saltos de línea y los adjuntos.
+El pie de la vista previa puede mostrar **Cancelar suscripción**. En un correo manual del Inbox ese enlace no se agrega automáticamente al envío.
+
+
+
+
+
+
+
+
+
+
+ Vista previa del borrador con datos ficticios. Alterna entre escritorio y móvil para revisar cómo se distribuye el contenido.
+
### Links y personalización
@@ -98,29 +136,21 @@ Sigue leyendo: [Links con tracking]({% link _analytics-reporting-attribution/tra
## Longitud del texto y archivos adjuntos
-El correo electrónico permite textos más largos que una respuesta breve de chat, pero el editor sigue aplicando límites:
+El editor de correo organiza el contenido en bloques. Usa sus controles de imagen; la lista de archivos de otros canales no describe lo que puedes agregar a este diseño.
| Elemento | Límite o comportamiento |
| --- | --- |
-| **Texto del mensaje** | Hasta 100.000 caracteres en el editor de correo electrónico. |
-| **Una imagen cargada** | Hasta 25 MB por archivo. |
-| **Un documento cargado** | Hasta 25 MB por archivo. |
-| **Un archivo de audio o video cargado** | Hasta 25 MB por archivo. |
-| **Varios adjuntos** | Cada archivo debe ser aceptado al cargarlo. El correo completo también debe respetar los límites de tamaño de mensaje de los servicios de envío y recepción. |
-
-Que la carga de un archivo se acepte no garantiza que el servicio de correo de cada destinatario acepte el mensaje completo. Varios archivos grandes pueden hacer que el correo sea demasiado pesado, aunque cada archivo esté permitido por separado. Usa archivos más pequeños o comparte un link de descarga adecuado cuando no sea necesario incluir el archivo completo en el mensaje.
-
-Los tipos de archivo compatibles incluyen:
+| **Asunto** | Hasta 998 caracteres. |
+| **Texto con formato** | Se valida por bloque; el formato también ocupa espacio. Simplifica o divide un bloque si el editor rechaza su longitud. |
+| **Bloques principales** | Hasta 30 en el diseño. |
+| **Una imagen cargada** | PNG, JPEG, GIF o WebP de hasta 5 MB. Se incorpora al cuerpo del correo. |
+| **Documentos, audio o video** | Comparte un link adecuado; el editor de correo actual no ofrece la carga general de estos archivos como adjuntos. |
-- **Imágenes:** JPEG, PNG, GIF, WebP, AVIF, HEIC, HEIF, BMP, TIFF y SVG.
-- **Documentos:** PDF, Word, Excel, PowerPoint, archivos OpenDocument, RTF, texto sin formato y CSV.
-- **Audio:** archivos compatibles AAC, audio MP4, MP3, AMR, Ogg, Opus, WAV, FLAC y audio WebM.
-- **Video:** archivos compatibles MP4, MPEG, 3GP, QuickTime, WebM y AVI.
-- **Otros archivos:** archivos compatibles ZIP, Gzip, EPUB, JSON, XML, HTML, de calendario y de contactos.
+El límite del texto con formato no equivale a un número fijo de caracteres para todo el correo. También se valida el tamaño conjunto del diseño. Mantén el mensaje breve y divide la información en bloques útiles, sin repetir contenido.
-Elige un tipo de archivo compatible y mantén cada archivo dentro del límite de tamaño. Si se rechaza un archivo, usa una exportación compatible o comparte un link adecuado. Cambiar solo la extensión del nombre no convierte el archivo.
+Espera a que termine la carga de cada imagen y revisa su contenido en **Vista previa**. Que una imagen se acepte no garantiza que todos los servicios de correo acepten el mensaje completo. Usa imágenes más pequeñas cuando sea posible.
-Usa el control de adjuntos del editor, espera a que termine la carga y confirma que los archivos correctos estén adjuntos antes de enviar. Revisa sus nombres y contenidos para enviar la versión correcta al cliente correcto.
+Para compartir un documento o un archivo grande, agrega un link de descarga y comprueba que el cliente tenga acceso. Cambiar solo la extensión de un archivo no lo convierte a un formato compatible.
## Cómo llegan las respuestas del cliente al Inbox
@@ -133,7 +163,7 @@ Después de recibir un correo enviado desde Hellotext, el cliente debe:
Hellotext asocia una respuesta compatible con el correo saliente original, el perfil del cliente y la conversación. Tu equipo puede leerla y responder desde el Inbox.
-Una respuesta puede incluir texto y adjuntos compatibles. El Inbox muestra el contenido y los archivos con su presentación habitual de mensajes. No reproduce el diseño HTML completo del correo del cliente como una vista de su casilla.
+Una respuesta puede incluir texto y adjuntos compatibles. El Inbox conserva elementos compatibles del correo recibido, como imágenes, tablas y listas, y puede agrupar el texto citado de mensajes anteriores. Algunos estilos o elementos del correo original pueden mostrarse de otra forma.
### Respuestas desde otra dirección
@@ -143,7 +173,7 @@ Cuando pruebes las respuestas, usa la misma dirección que recibió el correo y
### Correos nuevos enviados a la casilla existente de tu negocio
-Verificar un dominio de envío no traslada una casilla existente a Hellotext. Un correo nuevo escrito directamente a `support@acme.com` sigue la configuración de recepción que ya tenga esa dirección.
+Verificar un dominio de envío no traslada una casilla existente a Hellotext. Un correo nuevo escrito directamente a `support@example.com` sigue la configuración de recepción que ya tenga esa dirección.
Enviar desde esa dirección en Hellotext y recibir respuestas mediante la dirección de respuesta proporcionada son funciones distintas de importar el historial de una casilla o recibir todos los correos nuevos enviados al dominio. Si necesitas una configuración más amplia de recepción, consúltala con el [soporte de Hellotext]({% link _troubleshooting-deliverability/contact-hellotext-support.md %}).
@@ -204,7 +234,7 @@ Si Correo electrónico es el único destino del perfil y no hay un remitente de
### El mensaje usó un remitente o un asunto inesperados
-El menú de destino elige el destinatario. El remitente proviene del canal de correo electrónico y el asunto actual proviene del nombre del negocio.
+El menú de destino elige el destinatario. El remitente proviene del canal de correo electrónico; el asunto se escribe en **Asunto**. Revisa ese campo antes de enviar, también cuando respondes a un correo anterior.
Revisa el nombre y la dirección del remitente en **Ajustes > Integraciones**. Si tienes varios remitentes, comprueba qué canal usó la conversación. Contacta al soporte si necesitas ayuda para identificar el remitente antes de enviar más mensajes.
@@ -212,7 +242,7 @@ Revisa el nombre y la dirección del remitente en **Ajustes > Integraciones**. S
Confirma la dirección exacta del destinatario y revisa si el mensaje tiene información de entrega o un fallo. Pide al cliente que revise la carpeta de spam o correo no deseado, además de su bandeja de entrada habitual.
-Si el correo todavía se está enviando, espera a que termine el procesamiento. Si falló, revisa el motivo disponible, corrige el destino o el contenido cuando corresponda y comprueba el tamaño total de los adjuntos antes de volver a intentarlo.
+Si el correo todavía se está enviando, espera a que termine el procesamiento. Si falló, revisa el motivo disponible, corrige el destino o el contenido cuando corresponda y reduce las imágenes o simplifica el diseño si el tamaño impide el envío.
### La respuesta del cliente no aparece
@@ -222,7 +252,7 @@ Las respuestas entrantes también deben superar las comprobaciones de recepción
### Un adjunto falla o se ve diferente
-Revisa el tipo y el tamaño de archivo aceptados, confirma que la carga haya terminado y prueba una exportación compatible más pequeña cuando sea necesario. La apariencia del archivo en la aplicación de correo del cliente puede diferir de su vista previa en Hellotext.
+En el editor de correo, agrega las imágenes mediante sus bloques de imagen. Comprueba que sean PNG, JPEG, GIF o WebP de hasta 5 MB y espera a que termine la carga. Una imagen del diseño se muestra dentro del correo; su apariencia puede variar entre aplicaciones.
Para un documento o archivo multimedia grande, considera compartir un link de descarga adecuado. Mantén el acceso al archivo enlazado apropiado para el cliente al que se dirige.
@@ -232,8 +262,8 @@ Antes de que tu equipo dependa de las conversaciones por correo en el Inbox, con
1. El remitente elegido esté verificado y activo en el negocio correcto.
2. La dirección de un cliente de prueba esté guardada correctamente en su perfil.
-3. Seleccionar esa dirección envíe a través de Correo electrónico.
-4. El mensaje recibido muestre el remitente, el nombre del negocio, el texto y los adjuntos esperados.
+3. El destino seleccionado sea Email y muestre la dirección correcta.
+4. El mensaje de prueba recibido muestre el remitente, el asunto, el diseño, las imágenes y los links esperados.
5. Una respuesta desde la misma dirección del destinatario aparezca en la conversación correcta del Inbox.
6. La persona o el equipo adecuados se hagan responsables de la respuesta.
7. Tu equipo entienda la selección del remitente, la información de entrega y el alcance de las solicitudes de baja.
diff --git a/docs/editorial-work/captures/email-completion-20261011/accepted-source-manifest.json b/docs/editorial-work/captures/email-completion-20261011/accepted-source-manifest.json
new file mode 100644
index 00000000..5cc386f9
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/accepted-source-manifest.json
@@ -0,0 +1,331 @@
+{
+ "schema": "email-native-source-manifest-v1",
+ "status": "captured_pending_pixel_admission",
+ "clip_normalization": "exact array [x,y,width,height] sidecar values copied to named object; no pixel transformation",
+ "records": [
+ {
+ "id": "email-compose",
+ "locale": "en",
+ "layout": "desktop",
+ "file": "email-compose-en-desktop.png",
+ "sha256": "dca9d83767687997ffedfdd68a5cce6987ee3769af13c854b0e87aa776533653",
+ "pixelSize": [
+ 2068,
+ 980
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 302,
+ "y": 632,
+ "width": 517,
+ "height": 245
+ }
+ },
+ {
+ "id": "email-compose",
+ "locale": "en",
+ "layout": "mobile",
+ "file": "email-compose-en-mobile.png",
+ "sha256": "1633bb19ace6e63796708337cea4c59dab9cb0b2ed5157e74103efa972349096",
+ "pixelSize": [
+ 1560,
+ 1108
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 0,
+ "y": 573,
+ "width": 390,
+ "height": 277
+ }
+ },
+ {
+ "id": "email-compose",
+ "locale": "es",
+ "layout": "desktop",
+ "file": "email-compose-es-desktop.png",
+ "sha256": "50ae22dbdeb28f4f30a96805fc9624700f49a1251c28914a9a234c2a200a68ad",
+ "pixelSize": [
+ 2068,
+ 980
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 302,
+ "y": 632,
+ "width": 517,
+ "height": 245
+ }
+ },
+ {
+ "id": "email-compose",
+ "locale": "es",
+ "layout": "mobile",
+ "file": "email-compose-es-mobile.png",
+ "sha256": "c412d9d24f985e746715e0d6f7f5244ce9221c311c57a56d88e6aec75c89ec09",
+ "pixelSize": [
+ 1560,
+ 1108
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 0,
+ "y": 553,
+ "width": 390,
+ "height": 277
+ }
+ },
+ {
+ "id": "email-inline-preview",
+ "locale": "en",
+ "layout": "desktop",
+ "file": "email-inline-preview-en-desktop.png",
+ "sha256": "084ba9845b9ea1cb0be692eda804d2ba21d60017d8a5dca6392159490728e9ca",
+ "pixelSize": [
+ 2464,
+ 2280
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 242,
+ "y": 215,
+ "width": 616,
+ "height": 570
+ }
+ },
+ {
+ "id": "email-inline-preview",
+ "locale": "en",
+ "layout": "mobile",
+ "file": "email-inline-preview-en-mobile.png",
+ "sha256": "f6e2e1b7d5b30c20f88a8e19dc196937fcf36ec5dd91fce22f200d6cf7b8ec53",
+ "pixelSize": [
+ 1464,
+ 2280
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 12,
+ "y": 190,
+ "width": 366,
+ "height": 570
+ }
+ },
+ {
+ "id": "email-inline-preview",
+ "locale": "es",
+ "layout": "desktop",
+ "file": "email-inline-preview-es-desktop.png",
+ "sha256": "ae9e9d3f21beddb2229904372173431a833acc8771fcceefa2779042dc78036e",
+ "pixelSize": [
+ 2464,
+ 2280
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 242,
+ "y": 215,
+ "width": 616,
+ "height": 570
+ }
+ },
+ {
+ "id": "email-inline-preview",
+ "locale": "es",
+ "layout": "mobile",
+ "file": "email-inline-preview-es-mobile.png",
+ "sha256": "56b6093709e1f54f77b6118015826593ec17e297f0a2aa56f2a0c612809b0212",
+ "pixelSize": [
+ 1464,
+ 2280
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 12,
+ "y": 190,
+ "width": 366,
+ "height": 570
+ }
+ },
+ {
+ "id": "email-recipient-menu",
+ "locale": "en",
+ "layout": "desktop",
+ "file": "email-recipient-menu-en-desktop.png",
+ "sha256": "f074689a94aa3609ab02c70a080ae5031ffe6e309ada819d4fbd4e629b9b34f0",
+ "pixelSize": [
+ 2672,
+ 632
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 397,
+ "y": 591,
+ "width": 668,
+ "height": 158
+ }
+ },
+ {
+ "id": "email-recipient-menu",
+ "locale": "en",
+ "layout": "mobile",
+ "file": "email-recipient-menu-en-mobile.png",
+ "sha256": "19a5fee49bed8e470ad9e95739a4f6142a8d424890f6d37251a39c09ffb41d48",
+ "pixelSize": [
+ 2000,
+ 736
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 16,
+ "y": 558,
+ "width": 500,
+ "height": 184
+ }
+ },
+ {
+ "id": "email-recipient-menu",
+ "locale": "es",
+ "layout": "desktop",
+ "file": "email-recipient-menu-es-desktop.png",
+ "sha256": "b461acbaa46e2ba4c5377b5b3af6f1d440772f0470dee697de1a098931ec9dc0",
+ "pixelSize": [
+ 2672,
+ 628
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 397,
+ "y": 573,
+ "width": 668,
+ "height": 157
+ }
+ },
+ {
+ "id": "email-recipient-menu",
+ "locale": "es",
+ "layout": "mobile",
+ "file": "email-recipient-menu-es-mobile.png",
+ "sha256": "dc2b15f06ed0fe8f1b81171e0844f47bf30669bc59d7bb90b8ebc34795bdf8d5",
+ "pixelSize": [
+ 2000,
+ 736
+ ],
+ "nativeDensity": 4,
+ "devicePixelRatio": 2,
+ "captureScale": 2,
+ "sourceRevision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "transformations": "none",
+ "icc": {
+ "profile": "Display P3 Gamut with sRGB Transfer",
+ "sha256": "6e72ac49fd45d1275f29daca1038a0b9af5befd0e891af9267f47ab066a5dffb",
+ "bytes": 520
+ },
+ "clip": {
+ "x": 16,
+ "y": 558,
+ "width": 500,
+ "height": 184
+ }
+ }
+ ]
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/copy-adjustment.json b/docs/editorial-work/captures/email-completion-20261011/copy-adjustment.json
new file mode 100644
index 00000000..c20a96cc
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/copy-adjustment.json
@@ -0,0 +1,174 @@
+{
+ "status": "copy_corrected_pending_independent_review_native_captures_and_build",
+ "at": "2026-10-11T15:41:07.494920+00:00",
+ "base": "83709b00e107739ba3679d7ce8a80388f804eecf",
+ "records": [
+ {
+ "locale": "es",
+ "path": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "before_sha256": "f845b81cbdac3308558c30321f17ca9fa7cf8ec3bbf0a7c52af8b2daacf2d953",
+ "after_sha256": "3ad1b1bfcccd4e822691afd89e3c94c3211f0cede8f4397e94bba5346e40b14d",
+ "headings": 22,
+ "liquid_links": 20,
+ "changes": [
+ {
+ "before": "Correo electrónico está disponible en Enterprise.",
+ "after": "Correo electrónico está disponible en Pro y Enterprise."
+ },
+ {
+ "before": "- Compartir documentos, imágenes y otros archivos compatibles.",
+ "after": "- Compartir imágenes e información, con links a documentos cuando haga falta."
+ },
+ {
+ "before": "El Inbox ofrece un destino de correo electrónico para los clientes que tienen una dirección de correo cuando el negocio cuenta con un remitente de correo activo.",
+ "after": "El menú de destino del Inbox puede mostrar **Email** antes de que el envío esté listo. Para enviar necesitas una dirección en el perfil del cliente, acceso al canal y un remitente activo; ver la opción no confirma esos requisitos."
+ },
+ {
+ "before": "4. Busca el grupo **Correo electrónico**.",
+ "after": "4. Busca la opción **Email**."
+ },
+ {
+ "before": "6. Escribe tu mensaje. Usa párrafos claros, agrega los links necesarios y adjunta archivos compatibles cuando haga falta.",
+ "after": "6. Escribe el **Asunto** y prepara el cuerpo en el editor de correo. Organiza el contenido en bloques de texto y agrega imágenes o acciones cuando ayuden al cliente."
+ },
+ {
+ "before": "7. Comprueba que Correo electrónico esté seleccionado antes de enviar, especialmente si antes estabas respondiendo por otro canal.",
+ "after": "7. Abre **Vista previa** para revisar el diseño en escritorio y móvil. Comprueba el destinatario, el asunto, el texto y los links antes de enviar, especialmente si antes estabas respondiendo por otro canal."
+ },
+ {
+ "before": "Seleccionar una dirección de correo envía el mensaje a ese destino. No envía copias a todas las direcciones del perfil.",
+ "after": "Al enviar, se usa únicamente la dirección seleccionada. No se envían copias a todas las direcciones del perfil."
+ },
+ {
+ "before": "Si falta el grupo Correo electrónico, revisa la dirección del perfil y la activación del remitente antes de intentar enviar. Un dominio pendiente de verificación no ofrece un canal de envío activo.",
+ "after": "Si no puedes enviar por Email, revisa la dirección del perfil, el acceso de tu plan y la activación del remitente. Un dominio pendiente de verificación no ofrece un canal de envío activo, aunque el menú permita explorar la opción Email."
+ },
+ {
+ "before": "Hellotext presenta el mensaje como un correo con el nombre del negocio, el cuerpo del mensaje y un pie que muestra el nombre y la dirección del remitente. También incluye una versión de texto sin formato para las aplicaciones de correo que la utilizan.",
+ "after": "Hellotext prepara el correo a partir del diseño que editaste. La apariencia elegida aporta la marca y el pie del mensaje; el nombre y la dirección del remitente provienen del canal de correo. También se incluye una versión de texto sin formato para las aplicaciones de correo que la utilizan."
+ },
+ {
+ "before": "El asunto actual del correo usa el nombre del negocio. El editor del Inbox no ofrece un campo de asunto separado para cada mensaje. El nombre del remitente proviene de su integración; no cambia automáticamente al nombre de la persona del equipo que hizo clic en enviar.",
+ "after": "Usa **Asunto** para escribir el título del correo. Es independiente del cuerpo y del nombre del remitente; este último no cambia automáticamente al nombre de la persona del equipo que hizo clic en enviar."
+ },
+ {
+ "before": "El cuerpo usa el texto y los saltos de párrafo de tu mensaje. No dependas de que los estilos copiados, el HTML personalizado o los controles interactivos de otro canal se vean exactamente igual en el correo. Los archivos se entregan como adjuntos y la aplicación de correo del cliente controla cómo se previsualizan o descargan.",
+ "after": "El cuerpo conserva los bloques del diseño, como texto, imágenes y botones. Las imágenes que agregas al diseño aparecen dentro del correo; no se ofrecen automáticamente como archivos adjuntos descargables. No dependas de que los estilos copiados o los controles de otro canal se vean exactamente igual."
+ },
+ {
+ "before": "El diseño se adapta a pantallas más pequeñas, pero distintas aplicaciones de correo pueden mostrar el mismo mensaje de manera diferente. Revisa un mensaje recibido real para evaluar la apariencia, los saltos de línea y los adjuntos.",
+ "after": "Usa **Vista previa** para revisar el borrador sin enviarlo y alterna entre escritorio y móvil. Distintas aplicaciones de correo pueden mostrar el mismo diseño de manera diferente; una prueba recibida te permite comprobar la apariencia final, los saltos de línea y los links."
+ },
+ {
+ "before": "El menú de destino elige el destinatario. El remitente proviene del canal de correo electrónico y el asunto actual proviene del nombre del negocio.",
+ "after": "El menú de destino elige el destinatario. El remitente proviene del canal de correo electrónico; el asunto se escribe en **Asunto**. Revisa ese campo antes de enviar, también cuando respondes a un correo anterior."
+ },
+ {
+ "before": "corrige el destino o el contenido cuando corresponda y comprueba el tamaño total de los adjuntos antes de volver a intentarlo.",
+ "after": "corrige el destino o el contenido cuando corresponda y reduce las imágenes o simplifica el diseño si el tamaño impide el envío."
+ },
+ {
+ "before": "Revisa el tipo y el tamaño de archivo aceptados, confirma que la carga haya terminado y prueba una exportación compatible más pequeña cuando sea necesario. La apariencia del archivo en la aplicación de correo del cliente puede diferir de su vista previa en Hellotext.",
+ "after": "En el editor de correo, agrega las imágenes mediante sus bloques de imagen. Comprueba que sean PNG, JPEG, GIF o WebP de hasta 5 MB y espera a que termine la carga. Una imagen del diseño se muestra dentro del correo; su apariencia puede variar entre aplicaciones."
+ },
+ {
+ "before": "3. Seleccionar esa dirección envíe a través de Correo electrónico.",
+ "after": "3. El destino seleccionado sea Email y muestre la dirección correcta."
+ },
+ {
+ "before": "4. El mensaje recibido muestre el remitente, el nombre del negocio, el texto y los adjuntos esperados.",
+ "after": "4. El mensaje de prueba recibido muestre el remitente, el asunto, el diseño, las imágenes y los links esperados."
+ },
+ {
+ "section": "## Longitud del texto y archivos adjuntos",
+ "before": "\nEl correo electrónico permite textos más largos que una respuesta breve de chat, pero el editor sigue aplicando límites:\n\n| Elemento | Límite o comportamiento |\n| --- | --- |\n| **Texto del mensaje** | Hasta 100.000 caracteres en el editor de correo electrónico. |\n| **Una imagen cargada** | Hasta 25 MB por archivo. |\n| **Un documento cargado** | Hasta 25 MB por archivo. |\n| **Un archivo de audio o video cargado** | Hasta 25 MB por archivo. |\n| **Varios adjuntos** | Cada archivo debe ser aceptado al cargarlo. El correo completo también debe respetar los límites de tamaño de mensaje de los servicios de envío y recepción. |\n\nQue la carga de un archivo se acepte no garantiza que el servicio de correo de cada destinatario acepte el mensaje completo. Varios archivos grandes pueden hacer que el correo sea demasiado pesado, aunque cada archivo esté permitido por separado. Usa archivos más pequeños o comparte un link de descarga adecuado cuando no sea necesario incluir el archivo completo en el mensaje.\n\nLos tipos de archivo compatibles incluyen:\n\n- **Imágenes:** JPEG, PNG, GIF, WebP, AVIF, HEIC, HEIF, BMP, TIFF y SVG.\n- **Documentos:** PDF, Word, Excel, PowerPoint, archivos OpenDocument, RTF, texto sin formato y CSV.\n- **Audio:** archivos compatibles AAC, audio MP4, MP3, AMR, Ogg, Opus, WAV, FLAC y audio WebM.\n- **Video:** archivos compatibles MP4, MPEG, 3GP, QuickTime, WebM y AVI.\n- **Otros archivos:** archivos compatibles ZIP, Gzip, EPUB, JSON, XML, HTML, de calendario y de contactos.\n\nElige un tipo de archivo compatible y mantén cada archivo dentro del límite de tamaño. Si se rechaza un archivo, usa una exportación compatible o comparte un link adecuado. Cambiar solo la extensión del nombre no convierte el archivo.\n\nUsa el control de adjuntos del editor, espera a que termine la carga y confirma que los archivos correctos estén adjuntos antes de enviar. Revisa sus nombres y contenidos para enviar la versión correcta al cliente correcto.\n\n",
+ "after": "\nEl editor de correo organiza el contenido en bloques. Usa sus controles de imagen; la lista de archivos de otros canales no describe lo que puedes agregar a este diseño.\n\n| Elemento | Límite o comportamiento |\n| --- | --- |\n| **Asunto** | Hasta 998 caracteres. |\n| **Texto con formato** | Se valida por bloque; el formato también ocupa espacio. Simplifica o divide un bloque si el editor rechaza su longitud. |\n| **Bloques principales** | Hasta 30 en el diseño. |\n| **Una imagen cargada** | PNG, JPEG, GIF o WebP de hasta 5 MB. Se incorpora al cuerpo del correo. |\n| **Documentos, audio o video** | Comparte un link adecuado; el editor de correo actual no ofrece la carga general de estos archivos como adjuntos. |\n\nEl límite del texto con formato no equivale a un número fijo de caracteres para todo el correo. También se valida el tamaño conjunto del diseño. Mantén el mensaje breve y divide la información en bloques útiles, sin repetir contenido.\n\nEspera a que termine la carga de cada imagen y revisa su contenido en **Vista previa**. Que una imagen se acepte no garantiza que todos los servicios de correo acepten el mensaje completo. Usa imágenes más pequeñas cuando sea posible.\n\nPara compartir un documento o un archivo grande, agrega un link de descarga y comprueba que el cliente tenga acceso. Cambiar solo la extensión de un archivo no lo convierte a un formato compatible.\n\n"
+ }
+ ],
+ "example_sender_replacement": "support@acme.com → support@example.com (reserved domain)"
+ },
+ {
+ "locale": "en",
+ "path": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "before_sha256": "d275f2a5a47e7ca89c08da4697ff9303d066382ab79dbedbb6e9f0d06939e444",
+ "after_sha256": "dc82c9c4cf627826b2681d51bf80526d73f76dfd91029e6fc48828826f24f3b2",
+ "headings": 22,
+ "liquid_links": 20,
+ "changes": [
+ {
+ "before": "Email is available on Enterprise.",
+ "after": "Email is available on Pro and Enterprise."
+ },
+ {
+ "before": "- Sharing documents, images, and other supported files.",
+ "after": "- Sharing images and information, with links to documents when needed."
+ },
+ {
+ "before": "The Inbox provides an Email destination for customers with an email address when the business has an active Email sender.",
+ "after": "The Inbox destination menu can show **Email** before sending is ready. To send, you need an address on the customer profile, channel access, and an active sender; seeing the option does not confirm those requirements."
+ },
+ {
+ "before": "6. Write your message. Use clear paragraphs, add any required links, and attach supported files when needed.",
+ "after": "6. Write the **Subject** and prepare the body in the Email editor. Organize the content into text blocks, adding images or actions when they help the customer."
+ },
+ {
+ "before": "7. Check that Email is selected before sending, especially if you were previously replying over another channel.",
+ "after": "7. Open **Preview** to review the desktop and mobile layouts. Check the recipient, subject, text, and links before sending, especially if you were previously replying over another channel."
+ },
+ {
+ "before": "Selecting one email address sends to that destination. It does not send copies to every email address on the profile.",
+ "after": "When you send, only the selected address is used. No copies are sent to the other addresses on the profile."
+ },
+ {
+ "before": "If the Email group is missing, check the profile's email address and the sender's activation before trying to send. A pending domain verification does not provide an active sending channel.",
+ "after": "If you cannot send through Email, check the profile's address, your plan access, and the sender's activation. A pending domain verification does not provide an active sending channel, even if the menu lets you explore the Email option."
+ },
+ {
+ "before": "Hellotext renders the message as an email with the business name, message body, and a footer showing the sender name and email address. It also includes a plain-text version for email applications that use it.",
+ "after": "Hellotext prepares the email from the design you edited. The selected appearance supplies its branding and footer; the sender name and address come from the Email channel. A plain-text version is also included for email applications that use it."
+ },
+ {
+ "before": "The current email subject uses the business name. The Inbox composer does not provide a separate subject field for each message. The sender name comes from the sender integration; it does not automatically change to the teammate who clicked Send.",
+ "after": "Use **Subject** to write the email title. It is separate from the body and sender name; the sender name does not automatically change to the teammate who clicked Send."
+ },
+ {
+ "before": "The message body uses the text and paragraph breaks from your message. Do not rely on copied styling, custom HTML, or another channel's interactive controls to appear identically in the email. Files are delivered as email attachments, and the customer's email application controls their preview or download experience.",
+ "after": "The body retains the design's blocks, such as text, images, and buttons. Images added to the design appear within the email; they are not automatically offered as downloadable file attachments. Do not rely on copied styling or another channel's controls to appear identically."
+ },
+ {
+ "before": "The layout adapts to smaller screens, but email applications can display the same message differently. Check an actual received message when evaluating appearance, line breaks, and attachments.",
+ "after": "Use **Preview** to review the unsent draft and switch between desktop and mobile layouts. Email applications can display the same design differently; a received test message lets you check the final appearance, line breaks, and links."
+ },
+ {
+ "before": "The destination menu chooses the recipient. The sender comes from the Email channel, and the current subject comes from the business name.",
+ "after": "The destination menu chooses the recipient. The sender comes from the Email channel; you write the subject in **Subject**. Check that field before sending, including when replying to an earlier email."
+ },
+ {
+ "before": "correct the destination or content when appropriate, and check the total attachment size before retrying.",
+ "after": "correct the destination or content when appropriate, and reduce images or simplify the design if its size prevents sending."
+ },
+ {
+ "before": "Check the accepted file type and size, confirm that the upload finished, and try a smaller supported export when necessary. A file's appearance in the customer's email application may differ from its preview in Hellotext.",
+ "after": "In the Email editor, add images through its image blocks. Check that they are PNG, JPEG, GIF, or WebP files up to 5 MB and wait for the upload to finish. A design image appears within the email; its appearance can vary between email applications."
+ },
+ {
+ "before": "3. Selecting that address sends through Email.",
+ "after": "3. The selected destination is Email and shows the correct address."
+ },
+ {
+ "before": "4. The received message shows the expected sender, business name, text, and attachments.",
+ "after": "4. The received test message shows the expected sender, subject, design, images, and links."
+ },
+ {
+ "section": "## Text length and attachments",
+ "before": "\nEmail allows longer text than a short chat reply, but the editor still applies limits:\n\n| Item | Limit or behavior |\n| --- | --- |\n| **Message text** | Up to 100,000 characters in the Email editor. |\n| **An uploaded image** | Up to 25 MB per file. |\n| **An uploaded document** | Up to 25 MB per file. |\n| **An uploaded audio or video file** | Up to 25 MB per file. |\n| **Several attachments** | Each file must be accepted by the uploader. The complete email must also fit the sending and receiving services' message-size limits. |\n\nAn accepted upload is not a guarantee that every recipient's email service will accept the complete message. Several large files can make an email too large even when each file is individually allowed. Use smaller files or share an appropriate download link when a message does not need to carry the full file itself.\n\nSupported file types include:\n\n- **Images:** JPEG, PNG, GIF, WebP, AVIF, HEIC, HEIF, BMP, TIFF, and SVG.\n- **Documents:** PDF, Word, Excel, PowerPoint, OpenDocument files, RTF, plain text, and CSV.\n- **Audio:** supported AAC, MP4 audio, MP3, AMR, Ogg, Opus, WAV, FLAC, and WebM audio files.\n- **Video:** supported MP4, MPEG, 3GP, QuickTime, WebM, and AVI files.\n- **Other files:** supported ZIP, Gzip, EPUB, JSON, XML, HTML, calendar, and contact files.\n\nChoose a supported file type and keep each file within the size limit. If a file is rejected, use a supported export or share a suitable link. Changing only the filename extension does not convert the file.\n\nUse the attachment control in the composer, wait for the upload to finish, and confirm that the intended files are attached before sending. Review filenames and contents so you send the correct version to the correct customer.\n\n",
+ "after": "\nThe Email editor organizes content into blocks. Use its image controls; the file list for other channels does not describe what you can add to this design.\n\n| Item | Limit or behavior |\n| --- | --- |\n| **Subject** | Up to 998 characters. |\n| **Formatted text** | Validated per block; formatting also uses space. Simplify or split a block if the editor rejects its length. |\n| **Top-level blocks** | Up to 30 in the design. |\n| **An uploaded image** | PNG, JPEG, GIF, or WebP up to 5 MB. It becomes part of the email body. |\n| **Documents, audio, or video** | Share an appropriate link; the current Email editor does not offer the general file uploader for these attachments. |\n\nThe formatted-text limit is not a fixed character count for the entire email. The combined design size is also validated. Keep the message concise and split information into useful blocks without repeating content.\n\nWait for each image to finish loading and check its content in **Preview**. An accepted image does not guarantee that every email service will accept the complete message. Use smaller images when possible.\n\nTo share a document or a large file, add a download link and check that the customer has access. Changing only a filename extension does not convert the file to a supported format.\n\n"
+ }
+ ],
+ "example_sender_replacement": "support@acme.com → support@example.com (reserved domain)"
+ }
+ ],
+ "runtime_operations": 0,
+ "publication_operations": 0,
+ "limits": "Retain original headings, links, slug, stub and inventory. New subject/design/image instructions require native pixel confirmation; source proofs are recorded separately. No claim of actual delivery or provider verification."
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/copy-independent-review.json b/docs/editorial-work/captures/email-completion-20261011/copy-independent-review.json
new file mode 100644
index 00000000..53bb28c5
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/copy-independent-review.json
@@ -0,0 +1,210 @@
+{
+ "schema": "email-copy-independent-review-v1",
+ "status": "passed",
+ "scope": "Complete bilingual Fundamentals prose and its current source corrections only; not source-pixel admission, runtime verification, Help QA or publication.",
+ "at": "2026-10-11T15:59:43.033029+00:00",
+ "reviewer": "assignment_capture",
+ "records": [
+ {
+ "locale": "es",
+ "path": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "after_sha256": "468b1665404cdb4851958932d623539eb442c30837c74f6d50e76bca2295fa61",
+ "status": "passed",
+ "complete_article_read": true,
+ "headings_preserved": 22,
+ "liquid_links_preserved": 20,
+ "native_pixel_confirmation_pending": true
+ },
+ {
+ "locale": "en",
+ "path": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "after_sha256": "912f2218984e3f3f2fca7ab8d7873190655e2f5b70d82a7fa752324dcc0fb073",
+ "status": "passed",
+ "complete_article_read": true,
+ "headings_preserved": 22,
+ "liquid_links_preserved": 20,
+ "native_pixel_confirmation_pending": true
+ }
+ ],
+ "bindings": {
+ "copy-adjustment.json": "9be905fbc24d623ffd431ce4101b8b10eaef012e548b3b76d13fa38a45849172",
+ "reply-copy-adjustment.json": "d453e0a08989ebc685963232832ab70c41a7c23e58c558defee1737f59d03c6b",
+ "copy-source-register.json": "792de8b4b23ee4b9c82a0f4cd121b2fbd448c4d3b72192facc786058922c58af"
+ },
+ "source_bindings_rehashed": [
+ {
+ "path": "app/components/compose/destination_component.html.erb",
+ "sha256": "596a8e4889cb85fe4acc0591a0c6ab150a9d1800803b54ca2c8346acb35eb3eb",
+ "bytes": 12267
+ },
+ {
+ "path": "app/components/compose/email_design_component.html.erb",
+ "sha256": "c8b80169649a191e7bae0f03d8a6e8a2b923883737c6bad1d4ecbaf6aca78064",
+ "bytes": 37084
+ },
+ {
+ "path": "app/components/compose/email_preview_devices_component.html.erb",
+ "sha256": "6a95d7fdd03f0f342314a068775bca8c4156dd9212561a35978e28dd3c6146f0",
+ "bytes": 530
+ },
+ {
+ "path": "app/components/compose/email_subject_component.html.erb",
+ "sha256": "421c2aa921f93e79a8f013883db0db5eb4d0dff5357c1013e2285756c9f4ddf1",
+ "bytes": 530
+ },
+ {
+ "path": "app/components/conversation/footer_component.rb",
+ "sha256": "43e80de4cb6c5b957b7c60654b943ca6ee22e4235163c27c27eeb4f919a7662c",
+ "bytes": 5021
+ },
+ {
+ "path": "app/controllers/conversation/email_designers_controller.rb",
+ "sha256": "8f335974cb20c0c110a820f9b2856709abc096d1c2c3447573b372642346d562",
+ "bytes": 517
+ },
+ {
+ "path": "app/helpers/email_compose_helper.rb",
+ "sha256": "8a5fdeedacc5c36a63b2f75429df574a5def8df54ff83230b2b5d4e00e246697",
+ "bytes": 356
+ },
+ {
+ "path": "app/javascript/controllers/compose/email_design_controller.js",
+ "sha256": "72bd388d9d041fbe95830ce6c78c30ccd5263eefa77857de474badbc14228aee",
+ "bytes": 266777
+ },
+ {
+ "path": "app/javascript/controllers/compose/inbox_email_controller.js",
+ "sha256": "a7cd122352d10ea8e1f658c9a99ed64bb6a8d393d1f77f456a1415ca73e4f5a7",
+ "bytes": 39968
+ },
+ {
+ "path": "app/mailers/ses/mailer.rb",
+ "sha256": "eda3bf5bddf5680a5fa80ebdc301b213eb5ccca5d5c6f85a6abec8aba1d6709a",
+ "bytes": 2822
+ },
+ {
+ "path": "app/models/mailing/blocks/text.rb",
+ "sha256": "223e3ffcf09aea8b81a47a9566ba8bd24721fb386e01525559c946e7108d5c2b",
+ "bytes": 3941
+ },
+ {
+ "path": "app/models/mailing/document.rb",
+ "sha256": "aafcb5c130bcf6d956166db173e2371a9bdf54a16ddf6124c79428a2e0ef5dd1",
+ "bytes": 12944
+ },
+ {
+ "path": "app/models/mailing/rendering/source.rb",
+ "sha256": "be885326eeb89c871d78fe9d36aba063d880148b96a3f72afcbd3c5ee6e4be54",
+ "bytes": 22239
+ },
+ {
+ "path": "app/models/message/email_content.rb",
+ "sha256": "a6541c28e23f3bf2bd3864318b90d9645fede8c910c18175ca979c838dcb59cf",
+ "bytes": 4808
+ },
+ {
+ "path": "config/locales/views/compose/email_design/es.yml",
+ "sha256": "375fd7ad42095569e3410dda8dca093be25eca0a46c17175c710da4179a4b331",
+ "bytes": 8092
+ },
+ {
+ "path": "config/locales/views/compose/es.yml",
+ "sha256": "17d6c64baa6442fc642fd1ee7323decf8ad4ca33088449c25b8224c7dfe4c845",
+ "bytes": 3743
+ },
+ {
+ "path": "db/seeds/packages.rb",
+ "sha256": "47ea3e4feb70a889ba3f89c51bf3261c42953e0dd0aec71550dde28858808e0d",
+ "bytes": 20782
+ },
+ {
+ "path": "app/components/message/email_content_component.rb",
+ "sha256": "5afe8c4df8931e7f14aced00407acb675f9323b5b323aab56616b1832b97fd68",
+ "bytes": 1481
+ },
+ {
+ "path": "app/controllers/landing/unsubscriptions_controller.rb",
+ "sha256": "71f0d076d2e62ef6cca7558cea3057fba28be94327ccbffa6416934f7bbbcab8",
+ "bytes": 1778
+ },
+ {
+ "path": "app/integrations/ses/gateway.rb",
+ "sha256": "104a605a54ba8582dd37f5ad40b0250e91bd8b364a39e006e60b488c119c861b",
+ "bytes": 8040
+ },
+ {
+ "path": "app/integrations/ses/mail/complained.rb",
+ "sha256": "560af53358f7fcddb6a8998e9b0a4180c58128ca2de6a862eaaf94230a8598b7",
+ "bytes": 349
+ },
+ {
+ "path": "app/integrations/ses/mail/content.rb",
+ "sha256": "4a23fc1407921e5fd9c7e1a21c3b60541d52e329e44fc944f67f3c9453f85bd1",
+ "bytes": 1856
+ },
+ {
+ "path": "app/integrations/ses/mail/delivered.rb",
+ "sha256": "272d2253343a2e2906f6bcd8811633d4abdda2500052057fde8b026731ca3409",
+ "bytes": 137
+ },
+ {
+ "path": "app/integrations/ses/mail/failed.rb",
+ "sha256": "f2f162a4b27d5c2a2693fdaa40bb3e86ff0e3e256b5f0e5b988d8e53b141f17a",
+ "bytes": 155
+ },
+ {
+ "path": "app/integrations/ses/mail/received.rb",
+ "sha256": "efef5b72a1757805a79a959f5471917b966fd2a770ec237828935abefeebef65",
+ "bytes": 5176
+ },
+ {
+ "path": "app/integrations/ses/mail/seen.rb",
+ "sha256": "a0b8cdd39933f005a69a21ff276e568724f1ca5b666f48293989c0ba98c4d1f0",
+ "bytes": 139
+ },
+ {
+ "path": "app/jobs/contact/unsubscribe_from_email_job.rb",
+ "sha256": "f117e0c0e83d49ccfdd6653945fad48197f14a858313667d72475b6725619d72",
+ "bytes": 264
+ },
+ {
+ "path": "app/views/landing/unsubscriptions/show.html.erb",
+ "sha256": "71264f9e0c55832f9dad76d53011e9462320012c58488a6768cfaa78c9a9ff82",
+ "bytes": 1871
+ },
+ {
+ "path": "app/views/messages/_email_content.html.erb",
+ "sha256": "4ec07d336ca71123bc1df1cd2904167a4ad5a758704c047f075099f2bce92ecf",
+ "bytes": 567
+ }
+ ],
+ "checks": {
+ "source_files_rehashed": 29,
+ "all_match_closed_source_manifest": true,
+ "headings_and_liquid_links_unchanged": true,
+ "stub_and_csv_byteexact_head": true,
+ "article_diff_check": "passed",
+ "source_current_scope": "Root source registers establish no overlap with 16 changed paths 8e→afac; no full app/assets parity asserted."
+ },
+ "reviewed_corrections": [
+ "Pro/Enterprise editor access and menu visibility separate from route readiness",
+ "Separate Subject and authored body/preview",
+ "998-character Subject; 30 root blocks; formatted-text bytes are not a global character limit",
+ "PNG/JPEG/GIF/WebP image blocks, native 5MB label for 5×1024×1024 bytes; generic file attachments excluded from this editor",
+ "Image placement in document, appearance branding/footer, MIME plain-text alternative",
+ "Supported sanitized incoming HTML tables/images/lists and conditional quoted-reply grouping",
+ "Original address/token reply matching, unsubscribe confirmation and separate delivery/open semantics retained",
+ "Reserved example.com sender; no local fixture presented as provider verification or actual delivery"
+ ],
+ "findings": [],
+ "pending": [
+ "Real native UI labels and every new source pixel review",
+ "Runtime fixture and source closure",
+ "Complete Help responsive QA/build/link checks and root publication gates"
+ ],
+ "writes": {
+ "help_files": 0,
+ "report_files": 1
+ },
+ "runtime_or_provider_operations": 0
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/copy-review-for-integration.json b/docs/editorial-work/captures/email-completion-20261011/copy-review-for-integration.json
new file mode 100644
index 00000000..ef0dda9a
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/copy-review-for-integration.json
@@ -0,0 +1,182 @@
+{
+ "schema": "email-preview-footer-independent-copy-review-v1",
+ "status": "passed",
+ "at": "2026-10-11T16:37:07.941093+00:00",
+ "records": [
+ {
+ "locale": "es",
+ "path": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "after_sha256": "beb9cf44197a248bb49efce30f52e41ed4690294762507a9d2dc5cff0182e007",
+ "status": "passed"
+ },
+ {
+ "locale": "en",
+ "path": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "after_sha256": "29ed9c667abcc334e4e9618a8a9dc68f4d036731b166158ef6c899678ec3a0aa",
+ "status": "passed"
+ }
+ ],
+ "historical_full_copy_review": {
+ "path": "audit/email-completion-preparation-20261011/copy-independent-review.json",
+ "sha256": "eb546f45864d8e4e12e0dcd0c3296a617926783c617ee764d537a726e3a25dc3"
+ },
+ "adjustment": {
+ "path": "audit/email-help-preparation-20261011/preview-footer-copy-adjustment.json",
+ "sha256": "b3684ac03a5a55521c5a3d7b83ffc027c8563d8571c89b2c34de55a3f3e4a861"
+ },
+ "source_bindings": [
+ {
+ "path": "app/components/conversation/footer_component/footer_component.html.erb",
+ "sha256": "a049195c1463646f3c7b188ba9c3ca0f5b5ea19c613ebcc37ea704e4a43fd6cf",
+ "bytes": 6113,
+ "lines": [
+ [
+ 119,
+ 126
+ ]
+ ]
+ },
+ {
+ "path": "app/javascript/controllers/compose/inbox_email_controller.js",
+ "sha256": "a7cd122352d10ea8e1f658c9a99ed64bb6a8d393d1f77f456a1415ca73e4f5a7",
+ "bytes": 39968,
+ "lines": [
+ [
+ 659,
+ 671
+ ]
+ ]
+ },
+ {
+ "path": "app/views/campaign/broadcasts/_email_preview.html.erb",
+ "sha256": "a6fb99bd4762327811a2e1e63bc6e828f6c25c5e836dd6681cfbaf7128fc56c6",
+ "bytes": 3104,
+ "lines": [
+ [
+ 34,
+ 43
+ ]
+ ]
+ },
+ {
+ "path": "app/views/shared/_email_subscription_links.html.erb",
+ "sha256": "4463cdfda984a6899f51298fd530e29e5409dc9a58fa3ec6943fe2e6cc85ccf6",
+ "bytes": 477,
+ "lines": [
+ [
+ 1,
+ 7
+ ]
+ ]
+ },
+ {
+ "path": "app/javascript/controllers/campaign/email_preview_controller.js",
+ "sha256": "9e69a60236c6f8933d9f0473770fed56e1c13262b1ea9dd532a877f4085106f9",
+ "bytes": 114500,
+ "lines": [
+ [
+ 2119,
+ 2132
+ ]
+ ]
+ },
+ {
+ "path": "app/javascript/lib/email_subscription_preview.js",
+ "sha256": "c58c27e404488d4338a6e2c38592491db84c251b00155d95c8dd337408d2d0fb",
+ "bytes": 6001,
+ "lines": [
+ [
+ 127,
+ 148
+ ]
+ ]
+ },
+ {
+ "path": "app/integrations/ses/gateway.rb",
+ "sha256": "104a605a54ba8582dd37f5ad40b0250e91bd8b364a39e006e60b488c119c861b",
+ "bytes": 8040,
+ "lines": [
+ [
+ 101,
+ 118
+ ],
+ [
+ 182,
+ 192
+ ]
+ ]
+ },
+ {
+ "path": "app/models/mailing/rendering/source.rb",
+ "sha256": "be885326eeb89c871d78fe9d36aba063d880148b96a3f72afcbd3c5ee6e4be54",
+ "bytes": 22239,
+ "lines": [
+ [
+ 32,
+ 34
+ ],
+ [
+ 85,
+ 89
+ ]
+ ]
+ },
+ {
+ "path": "app/models/mailing/renderer/html.rb",
+ "sha256": "040f431815a214183bffccf6a9c6a3222bd3628198460e4011060b80af82221f",
+ "bytes": 27001,
+ "lines": [
+ [
+ 160,
+ 180
+ ]
+ ]
+ },
+ {
+ "path": "app/models/mailing/renderer/plain_text.rb",
+ "sha256": "9955468fa0f42fcb736aab85ff2b47daff33ae4099743513f91e925b923e1bec",
+ "bytes": 5781,
+ "lines": [
+ [
+ 25,
+ 35
+ ]
+ ]
+ },
+ {
+ "path": "app/mailers/ses/mailer.rb",
+ "sha256": "eda3bf5bddf5680a5fa80ebdc301b213eb5ccca5d5c6f85a6abec8aba1d6709a",
+ "bytes": 2822,
+ "lines": [
+ [
+ 20,
+ 40
+ ],
+ [
+ 59,
+ 67
+ ]
+ ]
+ }
+ ],
+ "native_pixel_evidence": "audit/email-completion-preparation-20261011/capture/sources/email-inline-preview-es-desktop.png",
+ "native_pixel_sha256": "ae9e9d3f21beddb2229904372173431a833acc8771fcceefa2779042dc78036e",
+ "checks": {
+ "exact_added_paragraph_only": true,
+ "prior_article_bytes_restored_by_reverse_delta": true,
+ "eleven_source_bytes_rehashed_against_immutable_manifest": true,
+ "source_ranges_read": true,
+ "preview_shared_footer_source_verified": true,
+ "gateway_manual_message_unsubscribe_url_nil": true,
+ "renderers_require_url_or_preview_for_unsubscribe": true,
+ "native_es_preview_individually_viewed": true
+ },
+ "findings": [],
+ "limits": [
+ "Copy/source review only; no delivery, provider or mailbox test.",
+ "Original full independent review remains immutable; this receipt binds only the precise new paragraph and current article hashes.",
+ "Rendered Help QA and root source admission remain separate."
+ ],
+ "help_edits": 0,
+ "external_writes": 0
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/copy-source-register.json b/docs/editorial-work/captures/email-completion-20261011/copy-source-register.json
new file mode 100644
index 00000000..eefb6c43
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/copy-source-register.json
@@ -0,0 +1,171 @@
+{
+ "status": "source_facts_checked_native_pixels_and_independent_copy_review_pending",
+ "at": "2026-10-11T15:49:50.677692+00:00",
+ "source_revision": "8e27a524a1a1354385c7d2fd22de8e568c2112cb",
+ "compared_revision": "afacda5636225888e44666da2e6d76fdd6a1425f",
+ "manifest": {
+ "path": "audit/journeys-workflow-local-20261010/source-files.json",
+ "sha256": "d28b8d6b6975cc08fa885adf7157af117863987f1e5ff427ca9671a68a8a576c"
+ },
+ "compare": {
+ "path": "audit/journeys-workflow-local-20261010/scoped-currency-compare.json",
+ "sha256": "7c6e23bc24c5e0e6e03bbbf3bf18fedbdb865d4b9f8b288358c2cb5e5c19e81c"
+ },
+ "copy_adjustment": {
+ "path": "audit/email-help-preparation-20261011/copy-adjustment.json",
+ "sha256": "9be905fbc24d623ffd431ce4101b8b10eaef012e548b3b76d13fa38a45849172"
+ },
+ "facts": [
+ {
+ "claim": "Email editor availability is grade >=3; current package seeds identify Pro=3 and Enterprise=4, both with email_channel.",
+ "paths": [
+ "app/helpers/email_compose_helper.rb",
+ "db/seeds/packages.rb"
+ ]
+ },
+ {
+ "claim": "The Email menu can be visible before sending is ready. Actual route requires an address and an active channel; menu presence does not prove these prerequisites.",
+ "paths": [
+ "app/components/compose/destination_component.html.erb",
+ "app/components/conversation/footer_component.rb",
+ "app/javascript/controllers/compose/inbox_email_controller.js"
+ ]
+ },
+ {
+ "claim": "Inbox has its own Subject control and sends subject from the current editor state. Authored Email subject validates a maximum of998 characters.",
+ "paths": [
+ "app/components/compose/email_subject_component.html.erb",
+ "app/javascript/controllers/compose/inbox_email_controller.js",
+ "app/models/message/email_content.rb",
+ "config/locales/views/compose/es.yml"
+ ]
+ },
+ {
+ "claim": "Current inline Email designer edits blocks and previews desktop/mobile. Its image input accepts PNG/JPEG/GIF/WebP; JS caps one image at5*1024*1024 bytes, presented as5MB in native UI.",
+ "paths": [
+ "app/controllers/conversation/email_designers_controller.rb",
+ "app/components/compose/email_design_component.html.erb",
+ "app/javascript/controllers/compose/email_design_controller.js",
+ "app/components/compose/email_preview_devices_component.html.erb",
+ "config/locales/views/compose/email_design/es.yml"
+ ]
+ },
+ {
+ "claim": "Email document permits30 root blocks; text HTML has100000 bytes per block and combined canonical JSON1MiB. These byte budgets are not a whole-email character count; uploaded asset bytes are separate. Public prose uses practical simplification advice instead of false character units.",
+ "paths": [
+ "app/models/mailing/document.rb",
+ "app/models/mailing/blocks/text.rb",
+ "app/models/message/email_content.rb"
+ ]
+ },
+ {
+ "claim": "Design image blocks render in the email body. The inline Email composer serializes owned design resources and does not forward native legacy attachments. General attachment upload is not offered by the current inline design.",
+ "paths": [
+ "app/javascript/controllers/compose/inbox_email_controller.js",
+ "app/components/compose/email_design_component.html.erb",
+ "app/mailers/ses/mailer.rb",
+ "app/models/message/email_content.rb"
+ ]
+ },
+ {
+ "claim": "Email delivery renders design HTML and plain text; branding/footer derive from appearance independently of the sending identity.",
+ "paths": [
+ "app/mailers/ses/mailer.rb",
+ "app/models/mailing/rendering/source.rb"
+ ]
+ }
+ ],
+ "source_bindings": [
+ {
+ "path": "app/components/compose/destination_component.html.erb",
+ "sha256": "596a8e4889cb85fe4acc0591a0c6ab150a9d1800803b54ca2c8346acb35eb3eb",
+ "bytes": 12267
+ },
+ {
+ "path": "app/components/compose/email_design_component.html.erb",
+ "sha256": "c8b80169649a191e7bae0f03d8a6e8a2b923883737c6bad1d4ecbaf6aca78064",
+ "bytes": 37084
+ },
+ {
+ "path": "app/components/compose/email_preview_devices_component.html.erb",
+ "sha256": "6a95d7fdd03f0f342314a068775bca8c4156dd9212561a35978e28dd3c6146f0",
+ "bytes": 530
+ },
+ {
+ "path": "app/components/compose/email_subject_component.html.erb",
+ "sha256": "421c2aa921f93e79a8f013883db0db5eb4d0dff5357c1013e2285756c9f4ddf1",
+ "bytes": 530
+ },
+ {
+ "path": "app/components/conversation/footer_component.rb",
+ "sha256": "43e80de4cb6c5b957b7c60654b943ca6ee22e4235163c27c27eeb4f919a7662c",
+ "bytes": 5021
+ },
+ {
+ "path": "app/controllers/conversation/email_designers_controller.rb",
+ "sha256": "8f335974cb20c0c110a820f9b2856709abc096d1c2c3447573b372642346d562",
+ "bytes": 517
+ },
+ {
+ "path": "app/helpers/email_compose_helper.rb",
+ "sha256": "8a5fdeedacc5c36a63b2f75429df574a5def8df54ff83230b2b5d4e00e246697",
+ "bytes": 356
+ },
+ {
+ "path": "app/javascript/controllers/compose/email_design_controller.js",
+ "sha256": "72bd388d9d041fbe95830ce6c78c30ccd5263eefa77857de474badbc14228aee",
+ "bytes": 266777
+ },
+ {
+ "path": "app/javascript/controllers/compose/inbox_email_controller.js",
+ "sha256": "a7cd122352d10ea8e1f658c9a99ed64bb6a8d393d1f77f456a1415ca73e4f5a7",
+ "bytes": 39968
+ },
+ {
+ "path": "app/mailers/ses/mailer.rb",
+ "sha256": "eda3bf5bddf5680a5fa80ebdc301b213eb5ccca5d5c6f85a6abec8aba1d6709a",
+ "bytes": 2822
+ },
+ {
+ "path": "app/models/mailing/blocks/text.rb",
+ "sha256": "223e3ffcf09aea8b81a47a9566ba8bd24721fb386e01525559c946e7108d5c2b",
+ "bytes": 3941
+ },
+ {
+ "path": "app/models/mailing/document.rb",
+ "sha256": "aafcb5c130bcf6d956166db173e2371a9bdf54a16ddf6124c79428a2e0ef5dd1",
+ "bytes": 12944
+ },
+ {
+ "path": "app/models/mailing/rendering/source.rb",
+ "sha256": "be885326eeb89c871d78fe9d36aba063d880148b96a3f72afcbd3c5ee6e4be54",
+ "bytes": 22239
+ },
+ {
+ "path": "app/models/message/email_content.rb",
+ "sha256": "a6541c28e23f3bf2bd3864318b90d9645fede8c910c18175ca979c838dcb59cf",
+ "bytes": 4808
+ },
+ {
+ "path": "config/locales/views/compose/email_design/es.yml",
+ "sha256": "375fd7ad42095569e3410dda8dca093be25eca0a46c17175c710da4179a4b331",
+ "bytes": 8092
+ },
+ {
+ "path": "config/locales/views/compose/es.yml",
+ "sha256": "17d6c64baa6442fc642fd1ee7323decf8ad4ca33088449c25b8224c7dfe4c845",
+ "bytes": 3743
+ },
+ {
+ "path": "db/seeds/packages.rb",
+ "sha256": "47ea3e4feb70a889ba3f89c51bf3261c42953e0dd0aec71550dde28858808e0d",
+ "bytes": 20782
+ }
+ ],
+ "changed_path_intersection": [],
+ "limits": [
+ "Scoped source continuity only; not deployed rendering or global CSS/asset parity.",
+ "No delivery, provider registration, DNS verification, upload or consent transition executed.",
+ "Native source pixels and independent review must confirm article-facing controls before publication."
+ ]
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/evidence-index.json b/docs/editorial-work/captures/email-completion-20261011/evidence-index.json
new file mode 100644
index 00000000..1a926043
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/evidence-index.json
@@ -0,0 +1,833 @@
+{
+ "status": "frozen_local_qa_evidence",
+ "scope": "Capture-directory evidence available before final-review and subsequent local-verification/commit receipts; historical pending states keep their original meaning. Index excludes itself and final-review to avoid cycles.",
+ "artifact_count": 164,
+ "artifacts": [
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/accepted-source-manifest.json",
+ "sha256": "619e0dade81ea362bcd56ff327953e20288972ecefd16c9f46b37f99d788903b",
+ "bytes": 9348
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-adjustment.json",
+ "sha256": "9be905fbc24d623ffd431ce4101b8b10eaef012e548b3b76d13fa38a45849172",
+ "bytes": 21060
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-independent-review.json",
+ "sha256": "eb546f45864d8e4e12e0dcd0c3296a617926783c617ee764d537a726e3a25dc3",
+ "bytes": 8083
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-review-for-integration.json",
+ "sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6",
+ "bytes": 4984
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-source-register.json",
+ "sha256": "792de8b4b23ee4b9c82a0f4cd121b2fbd448c4d3b72192facc786058922c58af",
+ "bytes": 7176
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/final-insertion-plan.json",
+ "sha256": "55f4a5f7cf1e5684b419e8afeac3a101aa93b011663b2d528396002706476528",
+ "bytes": 14828
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/integration-build-independent-review.json",
+ "sha256": "5165feeca21a497a86ad88f41eaeb09ee27a9513fad0ebd24c302be06ae2c7e1",
+ "bytes": 2037
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/integration-inputs.json",
+ "sha256": "3cf4ea9e3b8b39403ecd1ec35d704bb41cedcda7bd157d8dd264d8efd6623c2c",
+ "bytes": 753
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/integration-record.json",
+ "sha256": "3c6dbb5673d2dbffb5308d210b25c59d94af8cd9582db55b3bbec8df4fbec4d3",
+ "bytes": 7001
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/message-example.json",
+ "sha256": "d553d26f0ca05b43e7084bc13b82a606368b158a571b27db2bebbb015384e44a",
+ "bytes": 659
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/originals/_i18n/en/numbers/email-channel-fundamentals.md",
+ "sha256": "d275f2a5a47e7ca89c08da4697ff9303d066382ab79dbedbb6e9f0d06939e444",
+ "bytes": 18779
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/originals/_i18n/es/numbers/email-channel-fundamentals.md",
+ "sha256": "f845b81cbdac3308558c30321f17ca9fa7cf8ec3bbf0a7c52af8b2daacf2d953",
+ "bytes": 21363
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/originals/_numbers/email-channel-fundamentals.md",
+ "sha256": "6b73b939bcabee35bb67b996de6270cbad210ceaaf1128c80c00e315d06f292e",
+ "bytes": 633
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/originals/docs/editorial-work/progress.csv",
+ "sha256": "28bb3c6450425e0c7a48c63e29eead7eed61d7a6c70e35e3e267510692024192",
+ "bytes": 18403
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/pre-integration/en.md",
+ "sha256": "29ed9c667abcc334e4e9618a8a9dc68f4d036731b166158ef6c899678ec3a0aa",
+ "bytes": 18867
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/pre-integration/es.md",
+ "sha256": "beb9cf44197a248bb49efce30f52e41ed4690294762507a9d2dc5cff0182e007",
+ "bytes": 21292
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/precommit-main-inventory-snapshot.json",
+ "sha256": "6ed6778e2bb5d3729a01697af9276a0aa6f37d45580369ee466041e10c4f9bf5",
+ "bytes": 2414
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preparation-main-inventory-snapshot.json",
+ "sha256": "a50512ab16c63df220ea25094afc2c5881e5f221c7193af17a55e1df69a67f8d",
+ "bytes": 2414
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preserved-inputs.json",
+ "sha256": "df5fcc90d9bca35ee84bafaf286be8c54323c7d1fea89f6585ffbb907cc7994e",
+ "bytes": 1203
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preview-footer-copy-adjustment.json",
+ "sha256": "b3684ac03a5a55521c5a3d7b83ffc027c8563d8571c89b2c34de55a3f3e4a861",
+ "bytes": 7591
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preview-footer-copy-independent-review.json",
+ "sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6",
+ "bytes": 4984
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/reply-copy-adjustment.json",
+ "sha256": "d453e0a08989ebc685963232832ab70c41a7c23e58c558defee1737f59d03c6b",
+ "bytes": 5357
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/root-current-source-review.json",
+ "sha256": "03d65462ce5e2ecde760e5d534c14e200a1e3c81b070f58b03671136ea1fee84",
+ "bytes": 2457
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/root-preview-footer-copy-review.json",
+ "sha256": "98f0fc6471d9d2f0e8daece38d0f6f749c8f77adbed964d524d8cf7a1312b0fd",
+ "bytes": 4251
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/section-coverage.json",
+ "sha256": "f0b2b05d54d0e36a02ef864077c520b48177703e1c9f3da15c6ce9eba4fb8ba3",
+ "bytes": 7629
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-admission.json",
+ "sha256": "df01e909f3073b5ec85d2f6c326c6aca96eac89e899837fb062bff9627eeb38a",
+ "bytes": 12597
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/01-native_ui_proof.json",
+ "sha256": "f0a778dfacaff42282947e6e819c8a1f3c5d03c2eed4d7e3d016e712ac9eb102",
+ "bytes": 9416
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/02-source_pixel_review.json",
+ "sha256": "b2ff9e4dd45d265d0c8eba53c122a2a8b01aac5619ea3a116e712c215a2bb130",
+ "bytes": 7336
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/03-source_pixel_review.json",
+ "sha256": "5e4de595f65ed8575bfb4bb691fddf75e7cf52343163cdd1f131f9b5d9d70d94",
+ "bytes": 6990
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/04-runtime_closure.json",
+ "sha256": "35d14eb16c31a338bb6df30599e433bfca9e86a2a70fb9d3bce8fc26e03f51e4",
+ "bytes": 3692
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/05-capture_closure.json",
+ "sha256": "7ae0560cdcd766884ed651ae5c10d4222f8f4f85203eaaf2071c6698944f6a68",
+ "bytes": 1724
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/06-network_summary.json",
+ "sha256": "c042501e12a95bf5a6308aa07650a3f41a1a6f0adec4ef3b9a39cf097d45db39",
+ "bytes": 3212
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/07-capture_provenance.json",
+ "sha256": "7f859a695e2edc453262aa83269a524b51ff1c0e3ce14c2158767409f480a621",
+ "bytes": 4121
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/08-source_currency.json",
+ "sha256": "60781a1cc38a1c00b3ff63059f7bd66940dedf557608d00dc3795c886b6ef1bb",
+ "bytes": 2228
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/09-source_bytes.json",
+ "sha256": "81a26bcbf7dd8c31acdabf92ddadc51a32981f6c689f6440566c7866166f059e",
+ "bytes": 626
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/10-source_metadata_review.json",
+ "sha256": "dd99afd4df832a839ceccc79b968687cc898658d5411d6362c7f90763c787f83",
+ "bytes": 7159
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-register.json",
+ "sha256": "956dce071a2d2c979bc6aa6778191d53d9f81739183c737b1dba772d650d0595",
+ "bytes": 14607
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/build-execution.json",
+ "sha256": "a3ea16e6cb3f03fc5a8a57bd76715985c6576cd6f789f4d67a85f0cf08aa7063",
+ "bytes": 340
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/build.log",
+ "sha256": "46ddcab36c34357b1cd015c54173327dbff0d89e9bd0a91b06cee943eb6253f3",
+ "bytes": 1577
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/checkpoint.json",
+ "sha256": "e0d55dce8b3a72bb6eee08d854d8a99a221a89aed9e9230f87548c8d59f1963e",
+ "bytes": 15390
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/help-process-closure.json",
+ "sha256": "f6ee07286bcf4fc68e8bf1aea48c328dd9ae55834723dc9292c6506c51d85234",
+ "bytes": 966
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/help-processes-stopped.json",
+ "sha256": "23807432110dfda2d3c950c308408610ed27df9e54a2a03f2ca3e2084abe9947",
+ "bytes": 605
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/http-checks.json",
+ "sha256": "2a103b1a97b21dc47a1f2e4ee097273f9f1f842374457fb92c75a70ba2826c3b",
+ "bytes": 18815
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-1440-independent-review.json",
+ "sha256": "ba4ec0a7ea7cca39c85ed9c8c710bf7b503c3ee56f4fd113bd7532ac567d986f",
+ "bytes": 6740
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-390-independent-review.json",
+ "sha256": "adfbc38acf1527b7efa5ea5fc24f7cd65fa78a40ccfbac4610ae60d6edff404b",
+ "bytes": 10504
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-390-primary-review-pending-supplement.json",
+ "sha256": "4a24b9962a8b00e523238c612940fc99dead495d7bb1a9dae227fca447496ece",
+ "bytes": 8672
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-580-independent-review.json",
+ "sha256": "1e707e585bffc4f82f1721ceb33d7de056c98d296b1e4c283667077cad69a592",
+ "bytes": 7385
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-1440-independent-review.json",
+ "sha256": "71c055bdeeabf891136c83bc4b8017047b598f3d90a853980ceeca93fc555185",
+ "bytes": 10325
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-390-independent-review.json",
+ "sha256": "4e6610b32f56013f9c44a3cfb9ef125f3a900d592a7d474fcc573e4b3f68376d",
+ "bytes": 13028
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-580-independent-review.json",
+ "sha256": "ddbe3e7b7fee16bb64bbf7f97577aa940c0c5158aabe4ed55af09c6602716446",
+ "bytes": 10672
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/capture-receipt.json",
+ "sha256": "771a80767d71d384890f3f661f586491d90eb104ac19404d146a9ab71269ccfe",
+ "bytes": 192424
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-email-compose.png",
+ "sha256": "c0f5a9d0b849b5013363e69ebb0811cceb8274aba853559d66236ef1341a14ca",
+ "bytes": 69923
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-email-inline-preview.png",
+ "sha256": "79d3bcd10e5dd875fa7a131a8145a1c388c072a72d3c505e3e6f08438e3700ad",
+ "bytes": 74104
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-email-recipient-menu.png",
+ "sha256": "3f08f2bdb80ba752f493d0ac7a7832deb30283bffe6e1bb6ac0828e2aac396f5",
+ "bytes": 62506
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part1.png",
+ "sha256": "a4b3f30a22e89f0de56368f8005e861340f9e71be8da779704f8af35936cbc86",
+ "bytes": 772747
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part10.png",
+ "sha256": "d281204854ab6f8ae677f94b6dac235ac0513adf2b135938d247717d7152e63e",
+ "bytes": 935731
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part11.png",
+ "sha256": "3aa9e9b735f32a0aa9e1cacdb8134ff3e8b4555792ea563f17101f3d010cbe35",
+ "bytes": 697616
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part2.png",
+ "sha256": "3244e6470d1cc240e4f86cb6a472813b0e64700649f8c019f3db85c986f94263",
+ "bytes": 889644
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part3.png",
+ "sha256": "d3e52d354e8dc14a13bba86ca2ae59edf3bb1df85cd2e6064584abda7e7d0999",
+ "bytes": 840744
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part4.png",
+ "sha256": "30ed5eaca681cb05a1cb1890a97f7fc0465274ca6f7bed52c0561309823d6ebd",
+ "bytes": 840298
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part5.png",
+ "sha256": "ede43fac6c61dad76e7154fd0e7406972d0e397bc2e13ca9cd1c446e4d0f67b9",
+ "bytes": 711853
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part6.png",
+ "sha256": "513bfa3144d2e1457753f5d079a9c27401878f5aa0cc87f0a1b35aef93a76272",
+ "bytes": 831075
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part7.png",
+ "sha256": "54781bed1ffe326e79c14c69b75059fa283394c25a439db353f428f6b3b84f72",
+ "bytes": 939276
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part8.png",
+ "sha256": "1641d631e2cab4a75c0cc2965184e2204acf2e5f7778bf7838a0424e6169db9f",
+ "bytes": 920204
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-1440-full-part9.png",
+ "sha256": "26d83deb23e93f173eff06479c97cd06be4b48553d66db4c992fcfbe6a583b44",
+ "bytes": 882479
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-email-compose.png",
+ "sha256": "6bb0c317b00272b6d5a322dd117395ed634322d8cbeadd0a6b61e4276e64de94",
+ "bytes": 65024
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-email-inline-preview.png",
+ "sha256": "f344bc6f488e2a2cabe36fb01a81364227840483a662342dda8615bfa0bdfccc",
+ "bytes": 73880
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-email-recipient-menu.png",
+ "sha256": "e003cff280d990969d89c23cdf583dea56444af1f155a90c704ccf7ec36d3116",
+ "bytes": 43657
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part1.png",
+ "sha256": "3adf588b7af936b8dd270bff6139169a2c22fc71f870733360952b08ae3ee8d0",
+ "bytes": 264513
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part10.png",
+ "sha256": "1d47f56bf07d34b23c04315ac75b26abbf8117d63030c7c9ed64ea2b53d025f5",
+ "bytes": 376462
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part11.png",
+ "sha256": "dbe6edd2c40cfc01645ba05cba5af98927f7b37039e6cc17485d698bb82cb793",
+ "bytes": 401254
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part12.png",
+ "sha256": "a4021cb09b55dbf5a8e9179c3794b31422665ea82cd546ea8c59e61819b1e003",
+ "bytes": 313473
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part13.png",
+ "sha256": "d3830620f9d0b7740c8e0452551d9684947d8748cf7640ec0c1a5828bd857aa8",
+ "bytes": 336664
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part14.png",
+ "sha256": "11738e3a64843139493580fa098024b98d9b6d8401864a57bc3b4d609cee8864",
+ "bytes": 360440
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part15.png",
+ "sha256": "b8aaeecbbe58370b92f2b317c3f93446e0b4b8a08d52d0aa95d15f4037cf0576",
+ "bytes": 354585
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part16.png",
+ "sha256": "8f1bbd678c58c910b77d53b656336615c0af2848560a1b9111721c5a2689be5c",
+ "bytes": 199281
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part2.png",
+ "sha256": "7cbaebf245ff193096cbe94aba3050896c459c908fa038a0490164614ac9b90b",
+ "bytes": 333481
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part3.png",
+ "sha256": "d156b6ad53e9fca2f319752dc97101091e63965e24c76f329ef4b440b3f61d81",
+ "bytes": 320480
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part4.png",
+ "sha256": "bd1095245fa2324dba1708f2211a2d61881640a66ccad550aec04112e55fd21a",
+ "bytes": 286086
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part5.png",
+ "sha256": "f41ba66bd8b6245773cecb85d691d980e0780dfbd05998801ee6d96288e98bea",
+ "bytes": 344470
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part6.png",
+ "sha256": "2a70d5566e5fae4deb1a8cbf1ff2856d5b787b68ffd4b5c84f0b3dd382466ae7",
+ "bytes": 347826
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part7.png",
+ "sha256": "491f3f05f3ba610461c72a79928618df9d8de9f7e9848be43ac2c9064b16a0a3",
+ "bytes": 282583
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part8.png",
+ "sha256": "af68235e9c7203f71e8b5d7c5ecd1a58e55fe81f6109ff7acbab866003e99653",
+ "bytes": 296378
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-390-full-part9.png",
+ "sha256": "e489edcef8bd1ab3ad898bf3d279b35c41681adf85a392203d63e660c3d9a27d",
+ "bytes": 360944
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-email-compose.png",
+ "sha256": "b3d1413b002e5f4b546f3c006989c2d9fb1bf15fa7d604c038517d18ee05c0e7",
+ "bytes": 67339
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-email-inline-preview.png",
+ "sha256": "50573416d71d5edc06738b8673995c473774ee2e3d4280de28cd5cdb483cca4f",
+ "bytes": 73961
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-email-recipient-menu.png",
+ "sha256": "753213cf9436b7eabd4374286622c4416b21b05818e1d3359d98c4894de9c66d",
+ "bytes": 67735
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part1.png",
+ "sha256": "d557376b62c95718cc7cd1589192192224c8421df7163e250654b0ef3a578cef",
+ "bytes": 326721
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part10.png",
+ "sha256": "999da8e52ccdddc8c085a63695639000ffc1e602744400f92d034cc4d7aa839e",
+ "bytes": 391135
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part11.png",
+ "sha256": "53a263a16986153f17ea8c685442f097bf8308ff60676d14ca72ee364d6865ca",
+ "bytes": 466855
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part12.png",
+ "sha256": "ae5580d263c2f69dd8ce9fc7978870d7961d03c6cfb97a7f0056ebcdae7effd6",
+ "bytes": 331142
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part13.png",
+ "sha256": "a5b0a86079e5d2942e586ed916371d5ae5aac6c898209c62586c580e98627a62",
+ "bytes": 232808
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part2.png",
+ "sha256": "ad4517811fb2a9d693c6253cf75d05560a72d15d39aace604f7d8b40d6eed316",
+ "bytes": 440278
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part3.png",
+ "sha256": "66397a6d4a5fff03fc1839c6609da177becec2a69e01f02437bd3212a7f10654",
+ "bytes": 373180
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part4.png",
+ "sha256": "c4fbbca4a96dd89ed79bf021f2b3e6bdaa2bba312ce5c0daaf2254dfedfe30e6",
+ "bytes": 372035
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part5.png",
+ "sha256": "497c4454c19ed3ab07c1806c95d4eba0bb15cfe0132d4d005a23958078e6e058",
+ "bytes": 418299
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part6.png",
+ "sha256": "9c50658f7a5a3ec37d09d8125bb883d609ef3644ac0c0eec78746d6c7619e964",
+ "bytes": 238839
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part7.png",
+ "sha256": "4881d8d14c245e9fdfaa7af884ecd1dccc05e4658a02a3c3a2304a42af5da486",
+ "bytes": 399736
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part8.png",
+ "sha256": "70d47d8975b4cc4a7a33b9266e5be2cd05ee2cedf90c8aa1da40384ab5f4f93a",
+ "bytes": 479859
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-en-580-full-part9.png",
+ "sha256": "a68ed2177e3688c91ee64dbf3d350a9497ddd8ed8883265d08892e901bb621e2",
+ "bytes": 440259
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-email-compose.png",
+ "sha256": "bbd18b4a2c7e8cae20dcfc2b5f0dac667a800f29005f9a65a27f9bc1cf9ae868",
+ "bytes": 69487
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-email-inline-preview.png",
+ "sha256": "12a30364329ff83e32771ae10941dd290bb2347423f2fd767e5ded6ab29d2e43",
+ "bytes": 77384
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-email-recipient-menu.png",
+ "sha256": "e085e4e939aae9f22575ecb3c1c0e20d616b3c81090061651a9fa778776749ea",
+ "bytes": 62034
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part1.png",
+ "sha256": "127d1b89e4f1589f56e2ccbeb9408d19cb004d0bbc5d294b280cefc93e660543",
+ "bytes": 791557
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part10.png",
+ "sha256": "b8b8dd10a45a4123f4522e8ae74f8922cb37d1de5ec78b8fae50a038d63e87e0",
+ "bytes": 957928
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part11.png",
+ "sha256": "b3c23bd7257863c4180244ff9765ef912794109183cd95f9e0f0ecb26457d41c",
+ "bytes": 930848
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part12.png",
+ "sha256": "1590df4e743a9488c7689d09207f0498a8d48072c62018ce94318cdaf86a87b6",
+ "bytes": 754332
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part2.png",
+ "sha256": "85f650ab098098be85d8ae96d4856b4b7b8b354a0494a8df8e85b4ed2886b2d8",
+ "bytes": 937876
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part3.png",
+ "sha256": "d42820ae0ab959412d67ff732f5d80f4e4d658cf87fbd9f871c63052db21f375",
+ "bytes": 946931
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part4.png",
+ "sha256": "d8269546e071b529af791a4737f641661dcccfbe9cc95db0cb6423a213ba8ab9",
+ "bytes": 875702
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part5.png",
+ "sha256": "e5b1bc7c4676b5a7bc23bcfa8ca750fbcfe25176d04980ff5593822a2581d459",
+ "bytes": 891999
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part6.png",
+ "sha256": "c7917ec6a1158cd17281cd9ce41e19c5b57cb365e9cc7481df58076041bd9ffa",
+ "bytes": 792889
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part7.png",
+ "sha256": "a415c783dabd2fd1aa7e0bc5207ffc780e9fc595e5e35b0e7f13be6e31450c85",
+ "bytes": 985284
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part8.png",
+ "sha256": "d8643a7fb20aeec46cc99943be49205f0e51870325498c1b46c97451a8fb131a",
+ "bytes": 1000121
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-1440-full-part9.png",
+ "sha256": "f206430568488314bafa0f966edbdc445c0c09d84dcc514cf5f4905ac41adbe0",
+ "bytes": 905177
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-email-compose.png",
+ "sha256": "d07dcd4edc03eb22feda46cfbb8325c189ac2fabf59d710e9b84c2220eaf07b7",
+ "bytes": 67426
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-email-inline-preview.png",
+ "sha256": "1ccdbcff24333efa35453203258486a1a6a71b43683bc544852115040245de92",
+ "bytes": 77743
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-email-recipient-menu.png",
+ "sha256": "8d8a938360a0e873312a803be50fc408091825041d1051477904c5037f846e2c",
+ "bytes": 43649
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part1.png",
+ "sha256": "141e1e536a7fe75f6b4aca051715ebbb73c3277a86045f134d9fbb3af095821d",
+ "bytes": 279605
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part10.png",
+ "sha256": "f7d11ddb375a0a2620ac2a3290f451b8a38b4b7c8110a4c5f3f0f220a1454ec5",
+ "bytes": 346967
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part11.png",
+ "sha256": "57fffbed673cc8ad8f4cb8a1b5cdaadc3d2616d1de304923a35da56ac8744446",
+ "bytes": 386461
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part12.png",
+ "sha256": "136680fa26e0cf412b77c7b7db20316e3b07b4099580974dc2456e3c243e92bd",
+ "bytes": 385739
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part13.png",
+ "sha256": "7b6b06ad45507d8a8e336e14b89d75f8601efa06f8ba6d43865c825cadef5dce",
+ "bytes": 310861
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part14.png",
+ "sha256": "09a778a16ffb6cdf5f201a3923092ebbfdb7ee72517be072bff3e4140f5c7b14",
+ "bytes": 336691
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part15.png",
+ "sha256": "446f907cfaefdd74d398d976e15dd09808252067fe8c2ba6a73de10e9f63e585",
+ "bytes": 369982
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part16.png",
+ "sha256": "893c18752d18dce0a4904a49c11a37013f7865fc4443180f12b8384d45284c87",
+ "bytes": 354647
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part17.png",
+ "sha256": "2ed5551858db2e1592940db98143d7838de689de459388d986c85b7f32ee8229",
+ "bytes": 251418
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part18.png",
+ "sha256": "9ffa4f608b345aa320e23900c8724445b3dc2accba6616d6ed9b2a927d967746",
+ "bytes": 221814
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part2.png",
+ "sha256": "f8832c4da035c620bb6f3630178492d95f03628ed793327373c80d5ab39c73a7",
+ "bytes": 303834
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part3.png",
+ "sha256": "fec3aaecc753c0645771828670598d5af452f77b5dabdc297b2eda357b948cd2",
+ "bytes": 396862
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part4.png",
+ "sha256": "c08c2677ec648a43f51753ecce19cb740311c945ad117f7472a8a8852fa7c4d3",
+ "bytes": 253392
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part5.png",
+ "sha256": "e696aacc62f377bcf038ec84348605a5115f322bc93efd2e25beef12f2dc55a4",
+ "bytes": 361988
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part6.png",
+ "sha256": "74887047ac9d46522f94b52198c189a2a753cf58977ebaae6b59dcac594c9038",
+ "bytes": 374630
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part7.png",
+ "sha256": "3c21bedf36f559e4b53644222786c42db533a9359a9d1edaa084e1f531861d2b",
+ "bytes": 369176
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part8.png",
+ "sha256": "ae480ac9a0a50ea66151bffc43c3fc9772d99d34902a53aa29da3c2ac4561f30",
+ "bytes": 274420
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-390-full-part9.png",
+ "sha256": "9d42806c7be8945e4e0a64d6fa6ee95a62d7f33c03b967349f595963af8b5e7e",
+ "bytes": 336296
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-email-compose.png",
+ "sha256": "1e9439a4eb21bd4cfeb825fa03fc814d5ae02bffdc7257a0ca205e84d90fd99e",
+ "bytes": 67499
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-email-inline-preview.png",
+ "sha256": "fd9260e697704dda271d917d60c1a9f9689860991cffd9390697d61adc37c8fd",
+ "bytes": 77524
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-email-recipient-menu.png",
+ "sha256": "798dadc3c60e420ef04eb2a241d616f1fd3c40682b22aeeffd735e0e2b4f17b3",
+ "bytes": 67563
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part1.png",
+ "sha256": "291a543c6d44f402a5c8e9f97fe9bd2ef5112008d94f38e8c9d580de4afa563b",
+ "bytes": 308710
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part10.png",
+ "sha256": "d35fc46e5b8672ed7594942b66c3a3a4ab555ae3a91e5133ada038e0e21eb733",
+ "bytes": 420762
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part11.png",
+ "sha256": "761b29e5708df879591d8a28e5e85f2c6315d74557274469d7be57a0a0d52b4d",
+ "bytes": 414212
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part12.png",
+ "sha256": "584020e639bfe094a2afcbccdfa8494540c2c9affc9e9d816f0a0f36d7798cd3",
+ "bytes": 479362
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part13.png",
+ "sha256": "1f99c3e5599296858abe114857ca1375da6486f53eb5165f1b81d072b74be7e8",
+ "bytes": 310640
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part14.png",
+ "sha256": "0079f4e544be767c476a802a6804ffe78b3302b7e6a8f54b88c8c1f62cea1d4e",
+ "bytes": 256745
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part2.png",
+ "sha256": "bd6394e090154ff7afff372ad17d7665ccb728d0d06b65e8e0dcdb1031c7e1d7",
+ "bytes": 407597
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part3.png",
+ "sha256": "9695940fe1fed329cfa1eeae488f7fe61c7de3bc6053994c22b7ac577cb64ffb",
+ "bytes": 426244
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part4.png",
+ "sha256": "6384f965905e29240127bcdf3850d0f28b840d7a00ad3fbe5c4a94dc92d25e67",
+ "bytes": 437519
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part5.png",
+ "sha256": "0981727c3c3314b6de9878bb0cbd777dcb5bd8c64b1c11b3bcbde488c91611f1",
+ "bytes": 393910
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part6.png",
+ "sha256": "867d8cb52c1153afb29727b7714807bc1a8d34756c9bbf4a0bca85128562bac8",
+ "bytes": 292691
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part7.png",
+ "sha256": "baa0c34b4daf37194643cc00e53b02675782a4c6349ae4d0c79c4d7d4d53b5bf",
+ "bytes": 387111
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part8.png",
+ "sha256": "192ee22d4244f8fc379214df23c66609339b1d3dd157abc0f8cb6f2451e0d666",
+ "bytes": 430590
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/email-es-580-full-part9.png",
+ "sha256": "27307c6cd61b803e93ddad4684242290ebc60a582a685a6f44a86a91092da5ea",
+ "bytes": 483033
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-1440.json",
+ "sha256": "ea096f94cb8df262b647a10a560a05b411daa6ae81419f259c4f3a903d228630",
+ "bytes": 26139
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-390.json",
+ "sha256": "25476a4f2ba4f61129a29a4e8f4fc3103f5a5e11af832359a33cc2232f2b1985",
+ "bytes": 30810
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-580.json",
+ "sha256": "8750931c25e7d61dfa5ac740abaf5cc12a161cc944aff4ccb4f9c0af4117e09c",
+ "bytes": 27836
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-1440.json",
+ "sha256": "183a6c4e008ca0ef09ac21c756c0427950e74a4e4bd1db2a45af1cb840fa7ec1",
+ "bytes": 27908
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-390.json",
+ "sha256": "85624a638c0c9221cf0753d33c6e32d31e686aaa782ef25414cc1af2259f016d",
+ "bytes": 33785
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-580.json",
+ "sha256": "bc36d210484ab668478ffd92da37f6c443572e7223775509068f3937001a835a",
+ "bytes": 29683
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-es-review.json",
+ "sha256": "c28d43ac43080bbe31d09ba9ff13c7906d4853f97593e46d0813ed393a120786",
+ "bytes": 2123
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-helper-independent-review.json",
+ "sha256": "061efc69f7d5af6c4ef16c75aa0bf9a79869e192932674fc1cb957cf853cb7f9",
+ "bytes": 1346
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-review/capture-receipt.json",
+ "sha256": "7fbf3f3999c4b82893e56c607104e904253b931ff4452d38dabd23d4dcddd663",
+ "bytes": 13877
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-review/email-table-es-390-table1-x1-part1.png",
+ "sha256": "f610a83f3c772cdd83fdc288065174a345504708633b85f352a1a9726093cc19",
+ "bytes": 280693
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-review/email-table-es-390-table1-x2-part1.png",
+ "sha256": "a33db11ce7a012cc86bef7263dcec508ec6eeb0d2847153fc8922741aeb0420f",
+ "bytes": 280431
+ }
+ ],
+ "excluded_later_receipts": [
+ "final-review.json",
+ "evidence-index.json",
+ "local-verification.json",
+ "local-verification-committed.json"
+ ]
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/final-insertion-plan.json b/docs/editorial-work/captures/email-completion-20261011/final-insertion-plan.json
new file mode 100644
index 00000000..70dc749c
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/final-insertion-plan.json
@@ -0,0 +1,397 @@
+{
+ "schema": "email-final-insertion-plan-v1",
+ "status": "approved_for_integration",
+ "at": "2026-10-11T16:41:26.504661+00:00",
+ "copy_review": {
+ "path": "audit/email-completion-preparation-20261011/preview-footer-copy-independent-review.json",
+ "sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6"
+ },
+ "copy_baseline_records": [
+ {
+ "locale": "es",
+ "path": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "after_sha256": "beb9cf44197a248bb49efce30f52e41ed4690294762507a9d2dc5cff0182e007"
+ },
+ {
+ "locale": "en",
+ "path": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "after_sha256": "29ed9c667abcc334e4e9618a8a9dc68f4d036731b166158ef6c899678ec3a0aa"
+ }
+ ],
+ "native_scene_plan": {
+ "path": "audit/email-completion-preparation-20261011/capture/scene-plan.json",
+ "sha256": "7608a44828b7eb0ac183fa4feda8a318f800d6e93371a96226d75cba1f2bd4b3"
+ },
+ "section_coverage": {
+ "path": "audit/email-help-preparation-20261011/section-coverage.json",
+ "sha256": "f0b2b05d54d0e36a02ef864077c520b48177703e1c9f3da15c6ce9eba4fb8ba3"
+ },
+ "insertions": [
+ {
+ "id": "email-recipient-menu",
+ "locale": "es",
+ "anchor": "El menú de destino muestra las direcciones de correo del cliente. No es una lista de los remitentes de tu negocio. Cuando eliges una dirección, Hellotext usa el remitente activo de la conversación de correo existente, si está disponible, o un canal de correo electrónico disponible para un destino nuevo.",
+ "position": "after",
+ "copy": {
+ "aria": "Elige la dirección del destinatario",
+ "alt": "Menú Email del Inbox con dos direcciones de correo del mismo cliente de ejemplo.",
+ "caption": "Interfaz real con datos ficticios: elige en Email la dirección del cliente que recibirá el mensaje."
+ },
+ "sources": {
+ "desktop": "email-recipient-menu-es-desktop.png",
+ "mobile": "email-recipient-menu-es-mobile.png"
+ },
+ "native_geometry": {
+ "desktop": {
+ "pixel_size": [
+ 2672,
+ 628
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 668,
+ 157
+ ],
+ "maximum_css_width": 668,
+ "sha256": "b461acbaa46e2ba4c5377b5b3af6f1d440772f0470dee697de1a098931ec9dc0"
+ },
+ "mobile": {
+ "pixel_size": [
+ 2000,
+ 736
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 500,
+ 184
+ ],
+ "maximum_css_width": 500,
+ "sha256": "dc2b15f06ed0fe8f1b81171e0844f47bf30669bc59d7bb90b8ebc34795bdf8d5"
+ },
+ "frame_maximum_css_width": 686
+ },
+ "status": "approved_for_integration",
+ "required_source_coverage": [
+ "Email group label and destination-menu context",
+ "Both fictional customer addresses fully readable",
+ "No business sender or delivery claim"
+ ]
+ },
+ {
+ "id": "email-compose",
+ "locale": "es",
+ "anchor": "8. Envía el mensaje y revisa su información de envío o entrega en la conversación.",
+ "position": "after",
+ "copy": {
+ "aria": "Prepara el asunto y el cuerpo del correo",
+ "alt": "Editor de correo del Inbox con el asunto y el cuerpo de un borrador sobre el retiro de un pedido de ejemplo.",
+ "caption": "Borrador con datos ficticios: revisa el asunto y el cuerpo del correo antes de enviarlo."
+ },
+ "sources": {
+ "desktop": "email-compose-es-desktop.png",
+ "mobile": "email-compose-es-mobile.png"
+ },
+ "native_geometry": {
+ "desktop": {
+ "pixel_size": [
+ 2068,
+ 980
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 517,
+ 245
+ ],
+ "maximum_css_width": 517,
+ "sha256": "50ae22dbdeb28f4f30a96805fc9624700f49a1251c28914a9a234c2a200a68ad"
+ },
+ "mobile": {
+ "pixel_size": [
+ 1560,
+ 1108
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 390,
+ 277
+ ],
+ "maximum_css_width": 390,
+ "sha256": "c412d9d24f985e746715e0d6f7f5244ce9221c311c57a56d88e6aec75c89ec09"
+ },
+ "frame_maximum_css_width": 535
+ },
+ "status": "approved_for_integration",
+ "required_source_coverage": [
+ "Subject label and complete localized subject",
+ "Complete authored body and Inbox Email editor context",
+ "Recipient control and relevant editor boundaries, as supported by actual geometry",
+ "Unsent draft; no sending or received-message claim"
+ ]
+ },
+ {
+ "id": "email-inline-preview",
+ "locale": "es",
+ "anchor": "El pie de la vista previa puede mostrar **Cancelar suscripción**. En un correo manual del Inbox ese enlace no se agrega automáticamente al envío.",
+ "position": "after",
+ "copy": {
+ "aria": "Revisa el diseño en Vista previa",
+ "alt": "Vista previa del borrador de Casa Lila, con el mensaje de ejemplo, el pie y el selector de escritorio y móvil.",
+ "caption": "Vista previa del borrador con datos ficticios. Alterna entre escritorio y móvil para revisar cómo se distribuye el contenido."
+ },
+ "sources": {
+ "desktop": "email-inline-preview-es-desktop.png",
+ "mobile": "email-inline-preview-es-mobile.png"
+ },
+ "native_geometry": {
+ "desktop": {
+ "pixel_size": [
+ 2464,
+ 2280
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 616,
+ 570
+ ],
+ "maximum_css_width": 616,
+ "sha256": "ae9e9d3f21beddb2229904372173431a833acc8771fcceefa2779042dc78036e"
+ },
+ "mobile": {
+ "pixel_size": [
+ 1464,
+ 2280
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 366,
+ 570
+ ],
+ "maximum_css_width": 366,
+ "sha256": "56b6093709e1f54f77b6118015826593ec17e297f0a2aa56f2a0c612809b0212"
+ },
+ "frame_maximum_css_width": 634
+ },
+ "status": "approved_for_integration",
+ "required_source_coverage": [
+ "Native Preview dialog boundaries and device-selector state",
+ "Example body, brand and footer, with the unsubscribe distinction in adjacent prose",
+ "No new-page preview action or received-message claim"
+ ]
+ },
+ {
+ "id": "email-recipient-menu",
+ "locale": "en",
+ "anchor": "The destination menu lists the customer's email addresses. It is not a list of your business's senders. When you choose an address, Hellotext uses the existing Email conversation's active sender when available, or an available Email channel for a new destination.",
+ "position": "after",
+ "copy": {
+ "aria": "Choose the recipient address",
+ "alt": "Inbox Email menu showing two email addresses for the same example customer.",
+ "caption": "Real interface with fictional data: choose the customer's intended recipient address under Email."
+ },
+ "sources": {
+ "desktop": "email-recipient-menu-en-desktop.png",
+ "mobile": "email-recipient-menu-en-mobile.png"
+ },
+ "native_geometry": {
+ "desktop": {
+ "pixel_size": [
+ 2672,
+ 632
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 668,
+ 158
+ ],
+ "maximum_css_width": 668,
+ "sha256": "f074689a94aa3609ab02c70a080ae5031ffe6e309ada819d4fbd4e629b9b34f0"
+ },
+ "mobile": {
+ "pixel_size": [
+ 2000,
+ 736
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 500,
+ 184
+ ],
+ "maximum_css_width": 500,
+ "sha256": "19a5fee49bed8e470ad9e95739a4f6142a8d424890f6d37251a39c09ffb41d48"
+ },
+ "frame_maximum_css_width": 686
+ },
+ "status": "approved_for_integration",
+ "required_source_coverage": [
+ "Email group label and destination-menu context",
+ "Both fictional customer addresses fully readable",
+ "No business sender or delivery claim"
+ ]
+ },
+ {
+ "id": "email-compose",
+ "locale": "en",
+ "anchor": "8. Send the message and review its sending or delivery information in the conversation.",
+ "position": "after",
+ "copy": {
+ "aria": "Prepare the email subject and body",
+ "alt": "Inbox Email editor showing the subject and body of an unsent draft about picking up an example order.",
+ "caption": "Draft with fictional data: review the email subject and body before sending."
+ },
+ "sources": {
+ "desktop": "email-compose-en-desktop.png",
+ "mobile": "email-compose-en-mobile.png"
+ },
+ "native_geometry": {
+ "desktop": {
+ "pixel_size": [
+ 2068,
+ 980
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 517,
+ 245
+ ],
+ "maximum_css_width": 517,
+ "sha256": "dca9d83767687997ffedfdd68a5cce6987ee3769af13c854b0e87aa776533653"
+ },
+ "mobile": {
+ "pixel_size": [
+ 1560,
+ 1108
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 390,
+ 277
+ ],
+ "maximum_css_width": 390,
+ "sha256": "1633bb19ace6e63796708337cea4c59dab9cb0b2ed5157e74103efa972349096"
+ },
+ "frame_maximum_css_width": 535
+ },
+ "status": "approved_for_integration",
+ "required_source_coverage": [
+ "Subject label and complete localized subject",
+ "Complete authored body and Inbox Email editor context",
+ "Recipient control and relevant editor boundaries, as supported by actual geometry",
+ "Unsent draft; no sending or received-message claim"
+ ]
+ },
+ {
+ "id": "email-inline-preview",
+ "locale": "en",
+ "anchor": "The preview footer may show **Unsubscribe**. That link is not automatically added when you send a manual email from the Inbox.",
+ "position": "after",
+ "copy": {
+ "aria": "Review the design in Preview",
+ "alt": "Preview of the Casa Lila draft with the example message, footer, and desktop and mobile selector.",
+ "caption": "Preview of the draft with fictional data. Switch between desktop and mobile to check how the content is arranged."
+ },
+ "sources": {
+ "desktop": "email-inline-preview-en-desktop.png",
+ "mobile": "email-inline-preview-en-mobile.png"
+ },
+ "native_geometry": {
+ "desktop": {
+ "pixel_size": [
+ 2464,
+ 2280
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 616,
+ 570
+ ],
+ "maximum_css_width": 616,
+ "sha256": "084ba9845b9ea1cb0be692eda804d2ba21d60017d8a5dca6392159490728e9ca"
+ },
+ "mobile": {
+ "pixel_size": [
+ 1464,
+ 2280
+ ],
+ "native_density": 4,
+ "native_logical_size": [
+ 366,
+ 570
+ ],
+ "maximum_css_width": 366,
+ "sha256": "f6e2e1b7d5b30c20f88a8e19dc196937fcf36ec5dd91fce22f200d6cf7b8ec53"
+ },
+ "frame_maximum_css_width": 634
+ },
+ "status": "approved_for_integration",
+ "required_source_coverage": [
+ "Native Preview dialog boundaries and device-selector state",
+ "Example body, brand and footer, with the unsubscribe distinction in adjacent prose",
+ "No new-page preview action or received-message claim"
+ ]
+ }
+ ],
+ "figure_order": {
+ "es": [
+ "email-recipient-menu",
+ "email-compose",
+ "email-inline-preview"
+ ],
+ "en": [
+ "email-recipient-menu",
+ "email-compose",
+ "email-inline-preview"
+ ]
+ },
+ "source_count": 12,
+ "source_manifest": {
+ "path": "audit/email-completion-preparation-20261011/capture/source-manifest.json",
+ "sha256": "619e0dade81ea362bcd56ff327953e20288972ecefd16c9f46b37f99d788903b"
+ },
+ "source_root": "audit/email-completion-preparation-20261011/capture/sources",
+ "pending": [],
+ "limits": [
+ "All12 exact native sources are mapped; final source admission and rendered Help acceptance remain separate.",
+ "Figure prose describes the recipient menu, unsent composer and native preview only.",
+ "Native CSS caps derive from original crop dimensions; images remain unchanged."
+ ],
+ "preservation": {
+ "headings_per_locale": 22,
+ "ordered_liquid_links_per_locale": 20,
+ "stub_sha256": "6b73b939bcabee35bb67b996de6270cbad210ceaaf1128c80c00e315d06f292e",
+ "inventory_sha256": "28bb3c6450425e0c7a48c63e29eead7eed61d7a6c70e35e3e267510692024192"
+ },
+ "help_changes_in_this_plan": false,
+ "external_writes": false,
+ "historical_draft": {
+ "path": "audit/email-help-preparation-20261011/source-insertion-plan.json",
+ "sha256": "6f03d10bb607bee11fa217969423f99cb86f4603da378136ea242f8aa358f7f7"
+ },
+ "historical_pending_copy_baseline": {
+ "path": "audit/email-help-preparation-20261011/copy-baseline-preview-footer-pending.json",
+ "sha256": "9e539f663a44a78f9ff17a762567abe859a98644295e70880308cfb39839ad93"
+ },
+ "reviewed_copy_baseline": {
+ "path": "audit/email-help-preparation-20261011/copy-baseline-reviewed.json",
+ "sha256": "b50e3851ab2a2c340d6d95e20e631153509e619d1d9a770a8c0fa7a80f8470cf"
+ },
+ "root_copy_review": {
+ "path": "audit/email-help-preparation-20261011/root-preview-footer-copy-review.json",
+ "sha256": "98f0fc6471d9d2f0e8daece38d0f6f749c8f77adbed964d524d8cf7a1312b0fd"
+ },
+ "historical_copy_reviewed_draft": {
+ "path": "audit/email-help-preparation-20261011/source-insertion-plan-copy-reviewed.json",
+ "sha256": "39196ad102be266f6b8b7e242ec4bed0a6299d52c6a268637e2e814868b273d0"
+ },
+ "source_layout_limits": [
+ "Recipient-menu mobile captures use a native580CSS viewport and500CSS crop; Help390 readability requires complete rendered inspection.",
+ "Composer mobile uses390CSS crop; inline preview mobile uses366CSS crop and570CSS height.",
+ "The8CSS-pixel dimmed backdrop around preview panels is native capture context, not an image transformation."
+ ],
+ "root_review": {
+ "reviewer": "root",
+ "at": "2026-10-11T16:50:19.283648+00:00",
+ "all_12_native_pixels_individually_viewed": true,
+ "precise_mappings_caps_and_copy_approved": true,
+ "runtime_closure_required_by_separate_admission": true
+ }
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/final-review.json b/docs/editorial-work/captures/email-completion-20261011/final-review.json
new file mode 100644
index 00000000..0ab688e0
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/final-review.json
@@ -0,0 +1,463 @@
+{
+ "status": "passed",
+ "recorded_at": "2026-10-11T17:16:14.478375+00:00",
+ "ready_for_local_verifying_commit": true,
+ "findings": [],
+ "articles": [
+ {
+ "locale": "es",
+ "source": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "source_sha256": "3114208e2f27837e1d1a3b068f450fba23f086f351d2150ec96198e17d8ffb3a",
+ "built_html": "_site/es/fundamentos-canal-correo-electronico.html",
+ "built_html_sha256": "b08fd8f45f4366718ffb83f3639412506ce92f1e3e16a4dbf6cb8cafaf65c961",
+ "route": "/es/fundamentos-canal-correo-electronico.html",
+ "figure_sources": {
+ "email-recipient-menu": {
+ "mobile": "/images/editorial/email-completion-20261011/email-recipient-menu-es-mobile.png",
+ "desktop": "/images/editorial/email-completion-20261011/email-recipient-menu-es-desktop.png"
+ },
+ "email-compose": {
+ "mobile": "/images/editorial/email-completion-20261011/email-compose-es-mobile.png",
+ "desktop": "/images/editorial/email-completion-20261011/email-compose-es-desktop.png"
+ },
+ "email-inline-preview": {
+ "mobile": "/images/editorial/email-completion-20261011/email-inline-preview-es-mobile.png",
+ "desktop": "/images/editorial/email-completion-20261011/email-inline-preview-es-desktop.png"
+ }
+ },
+ "ordered_links": [
+ "_integrations/set-up-email-sending.md",
+ "_audience/customer-profiles.md",
+ "_audience/consent-and-subscriber-status.md",
+ "_integrations/set-up-email-sending.md",
+ "_numbers/message-editor-overview.md",
+ "_analytics-reporting-attribution/tracked-links.md",
+ "_audience/personalization-tags.md",
+ "_troubleshooting-deliverability/contact-hellotext-support.md",
+ "_team/conversation-lifecycle.md",
+ "_team/assigning-conversations.md",
+ "_audience/consent-and-subscriber-status.md",
+ "_troubleshooting-deliverability/why-a-message-did-not-send.md",
+ "_integrations/set-up-email-sending.md",
+ "_numbers/messaging-overview.md",
+ "_team/inbox-overview.md",
+ "_numbers/message-editor-overview.md",
+ "_audience/customer-profiles.md",
+ "_audience/consent-and-subscriber-status.md",
+ "_analytics-reporting-attribution/tracked-links.md",
+ "_troubleshooting-deliverability/why-a-message-did-not-send.md"
+ ],
+ "heading_count": 22
+ },
+ {
+ "locale": "en",
+ "source": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "source_sha256": "19175d63f4cd706e2442f3081dda2455f1751a393aa5900261fb5d4d23490995",
+ "built_html": "_site/email-channel-fundamentals.html",
+ "built_html_sha256": "1d68672df4cf56cee93ba3bd6a16055a5eb7437bfeac6672f1091ee1654ab85f",
+ "route": "/email-channel-fundamentals.html",
+ "figure_sources": {
+ "email-recipient-menu": {
+ "mobile": "/images/editorial/email-completion-20261011/email-recipient-menu-en-mobile.png",
+ "desktop": "/images/editorial/email-completion-20261011/email-recipient-menu-en-desktop.png"
+ },
+ "email-compose": {
+ "mobile": "/images/editorial/email-completion-20261011/email-compose-en-mobile.png",
+ "desktop": "/images/editorial/email-completion-20261011/email-compose-en-desktop.png"
+ },
+ "email-inline-preview": {
+ "mobile": "/images/editorial/email-completion-20261011/email-inline-preview-en-mobile.png",
+ "desktop": "/images/editorial/email-completion-20261011/email-inline-preview-en-desktop.png"
+ }
+ },
+ "ordered_links": [
+ "_integrations/set-up-email-sending.md",
+ "_audience/customer-profiles.md",
+ "_audience/consent-and-subscriber-status.md",
+ "_integrations/set-up-email-sending.md",
+ "_numbers/message-editor-overview.md",
+ "_analytics-reporting-attribution/tracked-links.md",
+ "_audience/personalization-tags.md",
+ "_troubleshooting-deliverability/contact-hellotext-support.md",
+ "_team/conversation-lifecycle.md",
+ "_team/assigning-conversations.md",
+ "_audience/consent-and-subscriber-status.md",
+ "_troubleshooting-deliverability/why-a-message-did-not-send.md",
+ "_integrations/set-up-email-sending.md",
+ "_numbers/messaging-overview.md",
+ "_team/inbox-overview.md",
+ "_numbers/message-editor-overview.md",
+ "_audience/customer-profiles.md",
+ "_audience/consent-and-subscriber-status.md",
+ "_analytics-reporting-attribution/tracked-links.md",
+ "_troubleshooting-deliverability/why-a-message-did-not-send.md"
+ ],
+ "heading_count": 22
+ }
+ ],
+ "evidence": [
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/accepted-source-manifest.json",
+ "sha256": "619e0dade81ea362bcd56ff327953e20288972ecefd16c9f46b37f99d788903b"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-adjustment.json",
+ "sha256": "9be905fbc24d623ffd431ce4101b8b10eaef012e548b3b76d13fa38a45849172"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-independent-review.json",
+ "sha256": "eb546f45864d8e4e12e0dcd0c3296a617926783c617ee764d537a726e3a25dc3"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-review-for-integration.json",
+ "sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/copy-source-register.json",
+ "sha256": "792de8b4b23ee4b9c82a0f4cd121b2fbd448c4d3b72192facc786058922c58af"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/evidence-index.json",
+ "sha256": "dbc56cbb800c0f3c2b3155a127ebb8da2afae92ca1a78da7b7a5dbf5717e5bdc"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/final-insertion-plan.json",
+ "sha256": "55f4a5f7cf1e5684b419e8afeac3a101aa93b011663b2d528396002706476528"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/integration-build-independent-review.json",
+ "sha256": "5165feeca21a497a86ad88f41eaeb09ee27a9513fad0ebd24c302be06ae2c7e1"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/integration-inputs.json",
+ "sha256": "3cf4ea9e3b8b39403ecd1ec35d704bb41cedcda7bd157d8dd264d8efd6623c2c"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/integration-record.json",
+ "sha256": "3c6dbb5673d2dbffb5308d210b25c59d94af8cd9582db55b3bbec8df4fbec4d3"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/message-example.json",
+ "sha256": "d553d26f0ca05b43e7084bc13b82a606368b158a571b27db2bebbb015384e44a"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/precommit-main-inventory-snapshot.json",
+ "sha256": "6ed6778e2bb5d3729a01697af9276a0aa6f37d45580369ee466041e10c4f9bf5"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preparation-main-inventory-snapshot.json",
+ "sha256": "a50512ab16c63df220ea25094afc2c5881e5f221c7193af17a55e1df69a67f8d"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preserved-inputs.json",
+ "sha256": "df5fcc90d9bca35ee84bafaf286be8c54323c7d1fea89f6585ffbb907cc7994e"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preview-footer-copy-adjustment.json",
+ "sha256": "b3684ac03a5a55521c5a3d7b83ffc027c8563d8571c89b2c34de55a3f3e4a861"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/preview-footer-copy-independent-review.json",
+ "sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/reply-copy-adjustment.json",
+ "sha256": "d453e0a08989ebc685963232832ab70c41a7c23e58c558defee1737f59d03c6b"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/root-current-source-review.json",
+ "sha256": "03d65462ce5e2ecde760e5d534c14e200a1e3c81b070f58b03671136ea1fee84"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/root-preview-footer-copy-review.json",
+ "sha256": "98f0fc6471d9d2f0e8daece38d0f6f749c8f77adbed964d524d8cf7a1312b0fd"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/section-coverage.json",
+ "sha256": "f0b2b05d54d0e36a02ef864077c520b48177703e1c9f3da15c6ce9eba4fb8ba3"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-admission.json",
+ "sha256": "df01e909f3073b5ec85d2f6c326c6aca96eac89e899837fb062bff9627eeb38a"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/01-native_ui_proof.json",
+ "sha256": "f0a778dfacaff42282947e6e819c8a1f3c5d03c2eed4d7e3d016e712ac9eb102"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/02-source_pixel_review.json",
+ "sha256": "b2ff9e4dd45d265d0c8eba53c122a2a8b01aac5619ea3a116e712c215a2bb130"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/03-source_pixel_review.json",
+ "sha256": "5e4de595f65ed8575bfb4bb691fddf75e7cf52343163cdd1f131f9b5d9d70d94"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/04-runtime_closure.json",
+ "sha256": "35d14eb16c31a338bb6df30599e433bfca9e86a2a70fb9d3bce8fc26e03f51e4"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/05-capture_closure.json",
+ "sha256": "7ae0560cdcd766884ed651ae5c10d4222f8f4f85203eaaf2071c6698944f6a68"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/06-network_summary.json",
+ "sha256": "c042501e12a95bf5a6308aa07650a3f41a1a6f0adec4ef3b9a39cf097d45db39"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/07-capture_provenance.json",
+ "sha256": "7f859a695e2edc453262aa83269a524b51ff1c0e3ce14c2158767409f480a621"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/08-source_currency.json",
+ "sha256": "60781a1cc38a1c00b3ff63059f7bd66940dedf557608d00dc3795c886b6ef1bb"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/09-source_bytes.json",
+ "sha256": "81a26bcbf7dd8c31acdabf92ddadc51a32981f6c689f6440566c7866166f059e"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/10-source_metadata_review.json",
+ "sha256": "dd99afd4df832a839ceccc79b968687cc898658d5411d6362c7f90763c787f83"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-register.json",
+ "sha256": "956dce071a2d2c979bc6aa6778191d53d9f81739183c737b1dba772d650d0595"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/build-execution.json",
+ "sha256": "a3ea16e6cb3f03fc5a8a57bd76715985c6576cd6f789f4d67a85f0cf08aa7063"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/checkpoint.json",
+ "sha256": "e0d55dce8b3a72bb6eee08d854d8a99a221a89aed9e9230f87548c8d59f1963e"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/help-process-closure.json",
+ "sha256": "f6ee07286bcf4fc68e8bf1aea48c328dd9ae55834723dc9292c6506c51d85234"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/help-processes-stopped.json",
+ "sha256": "23807432110dfda2d3c950c308408610ed27df9e54a2a03f2ca3e2084abe9947"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/http-checks.json",
+ "sha256": "2a103b1a97b21dc47a1f2e4ee097273f9f1f842374457fb92c75a70ba2826c3b"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-1440-independent-review.json",
+ "sha256": "ba4ec0a7ea7cca39c85ed9c8c710bf7b503c3ee56f4fd113bd7532ac567d986f"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-390-independent-review.json",
+ "sha256": "adfbc38acf1527b7efa5ea5fc24f7cd65fa78a40ccfbac4610ae60d6edff404b"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-390-primary-review-pending-supplement.json",
+ "sha256": "4a24b9962a8b00e523238c612940fc99dead495d7bb1a9dae227fca447496ece"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-580-independent-review.json",
+ "sha256": "1e707e585bffc4f82f1721ceb33d7de056c98d296b1e4c283667077cad69a592"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-1440-independent-review.json",
+ "sha256": "71c055bdeeabf891136c83bc4b8017047b598f3d90a853980ceeca93fc555185"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-390-independent-review.json",
+ "sha256": "4e6610b32f56013f9c44a3cfb9ef125f3a900d592a7d474fcc573e4b3f68376d"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-580-independent-review.json",
+ "sha256": "ddbe3e7b7fee16bb64bbf7f97577aa940c0c5158aabe4ed55af09c6602716446"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/capture-receipt.json",
+ "sha256": "771a80767d71d384890f3f661f586491d90eb104ac19404d146a9ab71269ccfe"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-1440.json",
+ "sha256": "ea096f94cb8df262b647a10a560a05b411daa6ae81419f259c4f3a903d228630"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-390.json",
+ "sha256": "25476a4f2ba4f61129a29a4e8f4fc3103f5a5e11af832359a33cc2232f2b1985"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-580.json",
+ "sha256": "8750931c25e7d61dfa5ac740abaf5cc12a161cc944aff4ccb4f9c0af4117e09c"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-1440.json",
+ "sha256": "183a6c4e008ca0ef09ac21c756c0427950e74a4e4bd1db2a45af1cb840fa7ec1"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-390.json",
+ "sha256": "85624a638c0c9221cf0753d33c6e32d31e686aaa782ef25414cc1af2259f016d"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-580.json",
+ "sha256": "bc36d210484ab668478ffd92da37f6c443572e7223775509068f3937001a835a"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-es-review.json",
+ "sha256": "c28d43ac43080bbe31d09ba9ff13c7906d4853f97593e46d0813ed393a120786"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-helper-independent-review.json",
+ "sha256": "061efc69f7d5af6c4ef16c75aa0bf9a79869e192932674fc1cb957cf853cb7f9"
+ },
+ {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/table-scroll-review/capture-receipt.json",
+ "sha256": "7fbf3f3999c4b82893e56c607104e904253b931ff4452d38dabd23d4dcddd663"
+ }
+ ],
+ "page_review": {
+ "checkpoint_sha256": "e0d55dce8b3a72bb6eee08d854d8a99a221a89aed9e9230f87548c8d59f1963e",
+ "capture_receipt_sha256": "771a80767d71d384890f3f661f586491d90eb104ac19404d146a9ab71269ccfe",
+ "segments": 84,
+ "details": 18,
+ "views": [
+ {
+ "locale": "es",
+ "width": 1440,
+ "status": "passed",
+ "document_height_css": 12888,
+ "segments": 12,
+ "details": 3,
+ "packet": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-1440.json",
+ "sha256": "183a6c4e008ca0ef09ac21c756c0427950e74a4e4bd1db2a45af1cb840fa7ec1"
+ },
+ "complete_page_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-1440-independent-review.json",
+ "sha256": "71c055bdeeabf891136c83bc4b8017047b598f3d90a853980ceeca93fc555185"
+ },
+ "figure_detail_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-1440-independent-review.json",
+ "sha256": "71c055bdeeabf891136c83bc4b8017047b598f3d90a853980ceeca93fc555185"
+ }
+ },
+ {
+ "locale": "es",
+ "width": 580,
+ "status": "passed",
+ "document_height_css": 14695,
+ "segments": 14,
+ "details": 3,
+ "packet": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-580.json",
+ "sha256": "bc36d210484ab668478ffd92da37f6c443572e7223775509068f3937001a835a"
+ },
+ "complete_page_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-580-independent-review.json",
+ "sha256": "ddbe3e7b7fee16bb64bbf7f97577aa940c0c5158aabe4ed55af09c6602716446"
+ },
+ "figure_detail_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-580-independent-review.json",
+ "sha256": "ddbe3e7b7fee16bb64bbf7f97577aa940c0c5158aabe4ed55af09c6602716446"
+ }
+ },
+ {
+ "locale": "es",
+ "width": 390,
+ "status": "passed",
+ "document_height_css": 18922,
+ "segments": 18,
+ "details": 3,
+ "packet": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/es-390.json",
+ "sha256": "85624a638c0c9221cf0753d33c6e32d31e686aaa782ef25414cc1af2259f016d"
+ },
+ "complete_page_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-390-independent-review.json",
+ "sha256": "4e6610b32f56013f9c44a3cfb9ef125f3a900d592a7d474fcc573e4b3f68376d"
+ },
+ "figure_detail_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-es-390-independent-review.json",
+ "sha256": "4e6610b32f56013f9c44a3cfb9ef125f3a900d592a7d474fcc573e4b3f68376d"
+ }
+ },
+ {
+ "locale": "en",
+ "width": 1440,
+ "status": "passed",
+ "document_height_css": 11935,
+ "segments": 11,
+ "details": 3,
+ "packet": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-1440.json",
+ "sha256": "ea096f94cb8df262b647a10a560a05b411daa6ae81419f259c4f3a903d228630"
+ },
+ "complete_page_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-1440-independent-review.json",
+ "sha256": "ba4ec0a7ea7cca39c85ed9c8c710bf7b503c3ee56f4fd113bd7532ac567d986f"
+ },
+ "figure_detail_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-1440-independent-review.json",
+ "sha256": "ba4ec0a7ea7cca39c85ed9c8c710bf7b503c3ee56f4fd113bd7532ac567d986f"
+ }
+ },
+ {
+ "locale": "en",
+ "width": 580,
+ "status": "passed",
+ "document_height_css": 13643,
+ "segments": 13,
+ "details": 3,
+ "packet": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-580.json",
+ "sha256": "8750931c25e7d61dfa5ac740abaf5cc12a161cc944aff4ccb4f9c0af4117e09c"
+ },
+ "complete_page_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-580-independent-review.json",
+ "sha256": "1e707e585bffc4f82f1721ceb33d7de056c98d296b1e4c283667077cad69a592"
+ },
+ "figure_detail_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-580-independent-review.json",
+ "sha256": "1e707e585bffc4f82f1721ceb33d7de056c98d296b1e4c283667077cad69a592"
+ }
+ },
+ {
+ "locale": "en",
+ "width": 390,
+ "status": "passed",
+ "document_height_css": 17656,
+ "segments": 16,
+ "details": 3,
+ "packet": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-review/views/en-390.json",
+ "sha256": "25476a4f2ba4f61129a29a4e8f4fc3103f5a5e11af832359a33cc2232f2b1985"
+ },
+ "complete_page_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-390-independent-review.json",
+ "sha256": "adfbc38acf1527b7efa5ea5fc24f7cd65fa78a40ccfbac4610ae60d6edff404b"
+ },
+ "figure_detail_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/page-en-390-independent-review.json",
+ "sha256": "adfbc38acf1527b7efa5ea5fc24f7cd65fa78a40ccfbac4610ae60d6edff404b"
+ }
+ }
+ ]
+ },
+ "http": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/http-checks.json",
+ "sha256": "2a103b1a97b21dc47a1f2e4ee097273f9f1f842374457fb92c75a70ba2826c3b"
+ },
+ "owned_services": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/validation/help-process-closure.json",
+ "sha256": "f6ee07286bcf4fc68e8bf1aea48c328dd9ae55834723dc9292c6506c51d85234"
+ },
+ "source_counts": {
+ "source_pngs": 12,
+ "selected_pngs": 12,
+ "retained_pngs": 0,
+ "retained_selected_pngs": 0,
+ "new_pngs": 12,
+ "views": 6
+ },
+ "inventory_changed_by_this_qa": false,
+ "commits_created_by_this_qa": false,
+ "publication": false
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/integration-build-independent-review.json b/docs/editorial-work/captures/email-completion-20261011/integration-build-independent-review.json
new file mode 100644
index 00000000..0834b70e
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/integration-build-independent-review.json
@@ -0,0 +1,43 @@
+{
+ "status": "passed_for_frozen_integration_and_build_bytes",
+ "at": "2026-10-11T17:01:25.058103+00:00",
+ "checkpoint_sha256": "e0d55dce8b3a72bb6eee08d854d8a99a221a89aed9e9230f87548c8d59f1963e",
+ "integration_sha256": "3c6dbb5673d2dbffb5308d210b25c59d94af8cd9582db55b3bbec8df4fbec4d3",
+ "source_register_sha256": "956dce071a2d2c979bc6aa6778191d53d9f81739183c737b1dba772d650d0595",
+ "native_manifest_sha256": "619e0dade81ea362bcd56ff327953e20288972ecefd16c9f46b37f99d788903b",
+ "new_sources_preserved": 12,
+ "built_png_copies_preserved": 24,
+ "articles": [
+ {
+ "locale": "es",
+ "path": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "sha256": "3114208e2f27837e1d1a3b068f450fba23f086f351d2150ec96198e17d8ffb3a",
+ "copy_baseline_sha256": "beb9cf44197a248bb49efce30f52e41ed4690294762507a9d2dc5cff0182e007",
+ "figures_removed_restore_copy_exactly": true,
+ "headings": 22,
+ "liquid_links": 20
+ },
+ {
+ "locale": "en",
+ "path": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "sha256": "19175d63f4cd706e2442f3081dda2455f1751a393aa5900261fb5d4d23490995",
+ "copy_baseline_sha256": "29ed9c667abcc334e4e9618a8a9dc68f4d036731b166158ef6c899678ec3a0aa",
+ "figures_removed_restore_copy_exactly": true,
+ "headings": 22,
+ "liquid_links": 20
+ }
+ ],
+ "source_evidence_copies_exact": 10,
+ "build_execution_sha256": "a3ea16e6cb3f03fc5a8a57bd76715985c6576cd6f789f4d67a85f0cf08aa7063",
+ "build_log_sha256": "46ddcab36c34357b1cd015c54173327dbff0d89e9bd0a91b06cee943eb6253f3",
+ "build_exit_code": 0,
+ "stub_and_inventory_preserved": true,
+ "tracked_delta_only_bilingual_article": true,
+ "untracked_paths_within_expected_assets_docs": true,
+ "raw_capture_sidecars_or_runtime_private_files_imported": false,
+ "findings": [],
+ "limits": [
+ "Visual page acceptance is separate and pending its real complete-page and figure receipts.",
+ "No build rerun, browser launch, database access, git index write or Help edit was performed by this review."
+ ]
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/integration-inputs.json b/docs/editorial-work/captures/email-completion-20261011/integration-inputs.json
new file mode 100644
index 00000000..3663c756
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/integration-inputs.json
@@ -0,0 +1,18 @@
+{
+ "schema": "email-integration-inputs-v1",
+ "status": "ready_for_integration",
+ "admission": {
+ "path": "audit/email-help-preparation-20261011/source-admission.json",
+ "sha256": "df01e909f3073b5ec85d2f6c326c6aca96eac89e899837fb062bff9627eeb38a"
+ },
+ "insertion_plan": {
+ "path": "audit/email-help-preparation-20261011/final-insertion-plan.json",
+ "sha256": "55f4a5f7cf1e5684b419e8afeac3a101aa93b011663b2d528396002706476528"
+ },
+ "copy_review": {
+ "path": "audit/email-completion-preparation-20261011/preview-footer-copy-independent-review.json",
+ "sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6"
+ },
+ "source_root": "audit/email-completion-preparation-20261011/capture/sources",
+ "pending": []
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/integration-record.json b/docs/editorial-work/captures/email-completion-20261011/integration-record.json
new file mode 100644
index 00000000..70905810
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/integration-record.json
@@ -0,0 +1,161 @@
+{
+ "status": "integrated_sources_and_preservation_passed_local_qa_pending",
+ "at": "2026-10-11T16:56:17.799242+00:00",
+ "base": "83709b00e107739ba3679d7ce8a80388f804eecf",
+ "inputs_sha256": "3cf4ea9e3b8b39403ecd1ec35d704bb41cedcda7bd157d8dd264d8efd6623c2c",
+ "insertion_plan_sha256": "55f4a5f7cf1e5684b419e8afeac3a101aa93b011663b2d528396002706476528",
+ "admission_sha256": "df01e909f3073b5ec85d2f6c326c6aca96eac89e899837fb062bff9627eeb38a",
+ "accepted_manifest_sha256": "619e0dade81ea362bcd56ff327953e20288972ecefd16c9f46b37f99d788903b",
+ "source_register_sha256": "956dce071a2d2c979bc6aa6778191d53d9f81739183c737b1dba772d650d0595",
+ "baseline_review_sha256": "a867d459a33352a2fe32c2db501ff067db2bfe27921f83a887b89f50c552d1a6",
+ "shared_source_figures": {
+ "es": [],
+ "en": []
+ },
+ "counts": {
+ "retained": 0,
+ "new": 12,
+ "sources": 12,
+ "selected": 12,
+ "figures_per_locale": {
+ "es": 3,
+ "en": 3
+ }
+ },
+ "articles": [
+ {
+ "locale": "es",
+ "source": "_i18n/es/numbers/email-channel-fundamentals.md",
+ "source_sha256": "3114208e2f27837e1d1a3b068f450fba23f086f351d2150ec96198e17d8ffb3a",
+ "before_integration_sha256": "beb9cf44197a248bb49efce30f52e41ed4690294762507a9d2dc5cff0182e007",
+ "headings_preserved": 22,
+ "ordered_links_preserved": 20,
+ "figure_count": 3,
+ "figure_order": [
+ "email-recipient-menu",
+ "email-compose",
+ "email-inline-preview"
+ ]
+ },
+ {
+ "locale": "en",
+ "source": "_i18n/en/numbers/email-channel-fundamentals.md",
+ "source_sha256": "19175d63f4cd706e2442f3081dda2455f1751a393aa5900261fb5d4d23490995",
+ "before_integration_sha256": "29ed9c667abcc334e4e9618a8a9dc68f4d036731b166158ef6c899678ec3a0aa",
+ "headings_preserved": 22,
+ "ordered_links_preserved": 20,
+ "figure_count": 3,
+ "figure_order": [
+ "email-recipient-menu",
+ "email-compose",
+ "email-inline-preview"
+ ]
+ }
+ ],
+ "source_evidence": [
+ {
+ "role": "native_ui_proof",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/01-native_ui_proof.json",
+ "sha256": "f0a778dfacaff42282947e6e819c8a1f3c5d03c2eed4d7e3d016e712ac9eb102",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/native-ui-proof.json",
+ "sha256": "f0a778dfacaff42282947e6e819c8a1f3c5d03c2eed4d7e3d016e712ac9eb102",
+ "role": "native_ui_proof"
+ }
+ },
+ {
+ "role": "source_pixel_review",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/02-source_pixel_review.json",
+ "sha256": "b2ff9e4dd45d265d0c8eba53c122a2a8b01aac5619ea3a116e712c215a2bb130",
+ "original": {
+ "path": "audit/email-help-preparation-20261011/root-source-pixels-es.json",
+ "sha256": "b2ff9e4dd45d265d0c8eba53c122a2a8b01aac5619ea3a116e712c215a2bb130",
+ "role": "source_pixel_review"
+ }
+ },
+ {
+ "role": "source_pixel_review",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/03-source_pixel_review.json",
+ "sha256": "5e4de595f65ed8575bfb4bb691fddf75e7cf52343163cdd1f131f9b5d9d70d94",
+ "original": {
+ "path": "audit/email-help-preparation-20261011/root-source-pixels-en.json",
+ "sha256": "5e4de595f65ed8575bfb4bb691fddf75e7cf52343163cdd1f131f9b5d9d70d94",
+ "role": "source_pixel_review"
+ }
+ },
+ {
+ "role": "runtime_closure",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/04-runtime_closure.json",
+ "sha256": "35d14eb16c31a338bb6df30599e433bfca9e86a2a70fb9d3bce8fc26e03f51e4",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/runtime-completion-summary.json",
+ "sha256": "35d14eb16c31a338bb6df30599e433bfca9e86a2a70fb9d3bce8fc26e03f51e4",
+ "role": "runtime_closure"
+ }
+ },
+ {
+ "role": "capture_closure",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/05-capture_closure.json",
+ "sha256": "7ae0560cdcd766884ed651ae5c10d4222f8f4f85203eaaf2071c6698944f6a68",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/capture-closure.json",
+ "sha256": "7ae0560cdcd766884ed651ae5c10d4222f8f4f85203eaaf2071c6698944f6a68",
+ "role": "capture_closure"
+ }
+ },
+ {
+ "role": "network_summary",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/06-network_summary.json",
+ "sha256": "c042501e12a95bf5a6308aa07650a3f41a1a6f0adec4ef3b9a39cf097d45db39",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/network-summary.json",
+ "sha256": "c042501e12a95bf5a6308aa07650a3f41a1a6f0adec4ef3b9a39cf097d45db39",
+ "role": "network_summary"
+ }
+ },
+ {
+ "role": "capture_provenance",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/07-capture_provenance.json",
+ "sha256": "7f859a695e2edc453262aa83269a524b51ff1c0e3ce14c2158767409f480a621",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/capture-provenance.json",
+ "sha256": "7f859a695e2edc453262aa83269a524b51ff1c0e3ce14c2158767409f480a621",
+ "role": "capture_provenance"
+ }
+ },
+ {
+ "role": "source_currency",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/08-source_currency.json",
+ "sha256": "60781a1cc38a1c00b3ff63059f7bd66940dedf557608d00dc3795c886b6ef1bb",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/source-currency-final.json",
+ "sha256": "60781a1cc38a1c00b3ff63059f7bd66940dedf557608d00dc3795c886b6ef1bb",
+ "role": "source_currency"
+ }
+ },
+ {
+ "role": "source_bytes",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/09-source_bytes.json",
+ "sha256": "81a26bcbf7dd8c31acdabf92ddadc51a32981f6c689f6440566c7866166f059e",
+ "original": {
+ "path": "audit/email-completion-preparation-20261011/capture/source-bytes-final.json",
+ "sha256": "81a26bcbf7dd8c31acdabf92ddadc51a32981f6c689f6440566c7866166f059e",
+ "role": "source_bytes"
+ }
+ },
+ {
+ "role": "source_metadata_review",
+ "path": "docs/editorial-work/captures/email-completion-20261011/source-evidence/10-source_metadata_review.json",
+ "sha256": "dd99afd4df832a839ceccc79b968687cc898658d5411d6362c7f90763c787f83",
+ "original": {
+ "path": "audit/email-help-preparation-20261011/root-png-byte-inspection.json",
+ "sha256": "dd99afd4df832a839ceccc79b968687cc898658d5411d6362c7f90763c787f83",
+ "role": "source_metadata_review"
+ }
+ }
+ ],
+ "rendered_qa": "pending",
+ "inventory_unchanged": true,
+ "commits_created": false,
+ "external_writes": false
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/local-verification-committed.json b/docs/editorial-work/captures/email-completion-20261011/local-verification-committed.json
new file mode 100644
index 00000000..7a7785b9
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/local-verification-committed.json
@@ -0,0 +1,47 @@
+{
+ "status": "bilingual_article_local_verified",
+ "recorded_at": "2026-10-11T17:19:47.178734+00:00",
+ "article_key": "numbers/email-channel-fundamentals.md",
+ "verifying_commit": "df2b62ca32f148d6058ee02a1ee1973a9c82d380",
+ "remaining_blockers": [],
+ "final_review": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/final-review.json",
+ "sha256": "98598d5d1c554bd5673467bfb99ac396b3e04cff56e6b9146ca708f362b7775a"
+ },
+ "evidence_index_at_verifying_commit": {
+ "path": "docs/editorial-work/captures/email-completion-20261011/evidence-index.json",
+ "sha256": "dbc56cbb800c0f3c2b3155a127ebb8da2afae92ca1a78da7b7a5dbf5717e5bdc"
+ },
+ "source_pngs": 12,
+ "new_pngs": 12,
+ "retained_pngs": 0,
+ "reviewed_views": 6,
+ "full_page_segments": 84,
+ "figure_details": 18,
+ "supplemental_table_pngs": 2,
+ "inventory": {
+ "before": {
+ "local_verified": 119,
+ "pending": 31,
+ "out_of_scope": 1,
+ "in_progress": 2,
+ "visual_pending": 1
+ },
+ "after": {
+ "local_verified": 120,
+ "pending": 30,
+ "out_of_scope": 1,
+ "in_progress": 2,
+ "visual_pending": 1
+ },
+ "unresolved_before": 34,
+ "unresolved_after": 33,
+ "publication_state": "not_yet_published"
+ },
+ "limitations": [
+ "Spanish identity table uses native horizontal scrolling at 390 CSS px; both endpoints reviewed.",
+ "Scoped source continuity does not assert current production app pixels or global asset parity.",
+ "Immutable raw build log retains one trailing space at line 10; all other staged files pass diff --check."
+ ],
+ "publication": false
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/message-example.json b/docs/editorial-work/captures/email-completion-20261011/message-example.json
new file mode 100644
index 00000000..2b18d915
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/message-example.json
@@ -0,0 +1,15 @@
+{
+ "status": "prepared_definition_not_captured_or_sent",
+ "purpose": "Give the customer an immediate next step for an example pickup.",
+ "es": {
+ "subject": "Retiro de tu pedido de ejemplo",
+ "body": "Hola Elena. Revisa los detalles para retirar tu pedido de ejemplo: https://example.com/pickup-demo"
+ },
+ "en": {
+ "subject": "Pickup for your example order",
+ "body": "Hi Elena. Review the pickup details for your example order: https://example.com/pickup-demo"
+ },
+ "renderer": "Existing inline Inbox Email designer and its native preview; no substitute template or hand-built screen.",
+ "delivery": "none",
+ "link_activation": "none"
+}
diff --git a/docs/editorial-work/captures/email-completion-20261011/originals/_i18n/en/numbers/email-channel-fundamentals.md b/docs/editorial-work/captures/email-completion-20261011/originals/_i18n/en/numbers/email-channel-fundamentals.md
new file mode 100644
index 00000000..673584b3
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/originals/_i18n/en/numbers/email-channel-fundamentals.md
@@ -0,0 +1,250 @@
+Use Email when customers need a message they can receive and reply to in their usual email application. Your team sends from an address on your business domain and manages supported replies in the Hellotext Inbox alongside the customer's other conversations.
+
+This guide explains everyday use of the Email channel after you have added a sender. For the sender form, DNS records, and domain verification, follow [Set up email sending]({% link _integrations/set-up-email-sending.md %}).
+
+
+ Email is available on Enterprise. A saved sender must finish domain verification before its channel becomes available for sending.
+
+
+## What Email is best for
+
+Use Email for:
+
+- One-to-one customer conversations from the Inbox.
+- Detailed answers that benefit from paragraphs and a written record.
+- Support and order follow-up with customers who prefer email.
+- Sharing documents, images, and other supported files.
+- Continuing a conversation after the customer replies to an email sent from Hellotext.
+
+Email does not require the customer to install a messaging app or have a phone number on their profile. You do need the correct email address and permission to contact the customer for the purpose of the message.
+
+## Before sending from the Inbox
+
+Before sending an individual Email from the Inbox, confirm that:
+
+- You are working in the correct Hellotext business.
+- The business has Email enabled and at least one verified, active email sender.
+- The customer profile contains the email address you intend to use.
+- You have access to that customer's Inbox conversation.
+- The customer and conversation are available for the intended contact.
+- Someone on your team is responsible for handling replies.
+
+The sender integration and the customer's email address serve different purposes. Adding a sender does not add email addresses to customer profiles. Adding a customer's email address does not verify your sending domain or establish that customer's consent.
+
+Keep reading: [Customer profiles]({% link _audience/customer-profiles.md %}) and [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Where you can use Email
+
+The Inbox provides an Email destination for customers with an email address when the business has an active Email sender.
+
+The campaign creator shows Email as a delivery option, but selecting it does not by itself enable sending. To send an Email campaign, the business needs Email access through its subscription and a verified, active sender. Connecting a sender does not automatically change the delivery channels of an existing campaign.
+
+Journeys can send Email from Message or Question steps configured with an Email design, and compatible proactive playbooks can select this channel. Each send depends on the flow's rules, an eligible recipient, and the business's Email access and sender. Use the Inbox for individual Email conversations and supported replies.
+
+## Understand the sender, recipient, and reply address
+
+An email conversation uses three addresses or identities:
+
+| Detail | What it means | Where it comes from |
+| --- | --- | --- |
+| **Sender** | The name and business email address shown as the sender of the message. | The email sender associated with the active Email channel. |
+| **Recipient** | The customer's address that will receive this message. | The email address you select from the customer's profile in the destination menu. |
+| **Reply address** | The address the customer's email application uses when they choose Reply. | Hellotext supplies it automatically so it can associate the response with the conversation. |
+
+For example, your sender might be `support@acme.com` and your customer might receive the message at `alex@example.com`. The reply address can be different from `support@acme.com`; that is how Hellotext receives the response for the conversation.
+
+The destination menu lists the customer's email addresses. It is not a list of your business's senders. When you choose an address, Hellotext uses the existing Email conversation's active sender when available, or an available Email channel for a new destination.
+
+If your business has several active senders, verify which one is used before relying on a particular From address. The Inbox destination menu does not currently provide a separate Email sender picker.
+
+To change a sender's name or email address, use its **Edit** action in **Settings > Integrations**. Changing its domain requires verification again. See [Set up email sending]({% link _integrations/set-up-email-sending.md %}) before making that change.
+
+## Send an email from the Inbox
+
+1. Open the customer's conversation in the **Inbox**.
+2. Check the customer's profile and confirm the email address is correct. Add or correct the address on the profile if needed.
+3. Open the destination menu beside the message editor.
+4. Find the **Email** group.
+5. Select the customer's intended email address. If the profile has more than one, choose the address that should receive this message.
+6. Write your message. Use clear paragraphs, add any required links, and attach supported files when needed.
+7. Check that Email is selected before sending, especially if you were previously replying over another channel.
+8. Send the message and review its sending or delivery information in the conversation.
+
+Selecting one email address sends to that destination. It does not send copies to every email address on the profile. The Email destination menu does not provide CC or BCC fields.
+
+For a customer whose only available destination is Email, Hellotext can open the composer with Email selected when an active sender is available. Always check the destination when the customer also has phone numbers or other connected channels.
+
+If the Email group is missing, check the profile's email address and the sender's activation before trying to send. A pending domain verification does not provide an active sending channel.
+
+Keep reading: [Message editor overview]({% link _numbers/message-editor-overview.md %}).
+
+## What the customer receives
+
+Hellotext renders the message as an email with the business name, message body, and a footer showing the sender name and email address. It also includes a plain-text version for email applications that use it.
+
+The current email subject uses the business name. The Inbox composer does not provide a separate subject field for each message. The sender name comes from the sender integration; it does not automatically change to the teammate who clicked Send.
+
+The message body uses the text and paragraph breaks from your message. Do not rely on copied styling, custom HTML, or another channel's interactive controls to appear identically in the email. Files are delivered as email attachments, and the customer's email application controls their preview or download experience.
+
+The layout adapts to smaller screens, but email applications can display the same message differently. Check an actual received message when evaluating appearance, line breaks, and attachments.
+
+### Links and personalization
+
+Use the editor's link tool when you need a tracked link, and check its destination before sending. Use personalization tags only when the customer's profile has the values needed to produce a complete message.
+
+Review the final wording with realistic customer data. A missing name, an outdated address, or a link pointing to the wrong product can make a successfully delivered email unhelpful.
+
+Keep reading: [Tracked links]({% link _analytics-reporting-attribution/tracked-links.md %}) and [Personalization tags]({% link _audience/personalization-tags.md %}).
+
+## Text length and attachments
+
+Email allows longer text than a short chat reply, but the editor still applies limits:
+
+| Item | Limit or behavior |
+| --- | --- |
+| **Message text** | Up to 100,000 characters in the Email editor. |
+| **An uploaded image** | Up to 25 MB per file. |
+| **An uploaded document** | Up to 25 MB per file. |
+| **An uploaded audio or video file** | Up to 25 MB per file. |
+| **Several attachments** | Each file must be accepted by the uploader. The complete email must also fit the sending and receiving services' message-size limits. |
+
+An accepted upload is not a guarantee that every recipient's email service will accept the complete message. Several large files can make an email too large even when each file is individually allowed. Use smaller files or share an appropriate download link when a message does not need to carry the full file itself.
+
+Supported file types include:
+
+- **Images:** JPEG, PNG, GIF, WebP, AVIF, HEIC, HEIF, BMP, TIFF, and SVG.
+- **Documents:** PDF, Word, Excel, PowerPoint, OpenDocument files, RTF, plain text, and CSV.
+- **Audio:** supported AAC, MP4 audio, MP3, AMR, Ogg, Opus, WAV, FLAC, and WebM audio files.
+- **Video:** supported MP4, MPEG, 3GP, QuickTime, WebM, and AVI files.
+- **Other files:** supported ZIP, Gzip, EPUB, JSON, XML, HTML, calendar, and contact files.
+
+Choose a supported file type and keep each file within the size limit. If a file is rejected, use a supported export or share a suitable link. Changing only the filename extension does not convert the file.
+
+Use the attachment control in the composer, wait for the upload to finish, and confirm that the intended files are attached before sending. Review filenames and contents so you send the correct version to the correct customer.
+
+## How customer replies reach the Inbox
+
+After receiving an email sent from Hellotext, the customer should:
+
+1. Open the message in their usual email application.
+2. Choose **Reply**.
+3. Keep the reply address supplied by the email application.
+4. Reply from the same email address that received the message.
+
+Hellotext associates a supported reply with the original outgoing email, customer profile, and conversation. Your team can then read and answer it from the Inbox.
+
+A reply can include text and supported attachments. The Inbox shows the reply content and attachments using its usual message presentation. It does not reproduce the customer's complete HTML email layout as a mailbox view.
+
+### Replies from another address
+
+Reply matching expects the original recipient's email address. A customer replying from another account, or forwarding the email to someone else who then replies, may not create a matching Inbox message.
+
+When testing replies, use the same address that received the email and leave the supplied reply address unchanged. The email subject alone is not enough to associate an arbitrary message with the conversation.
+
+### New emails sent to your existing business mailbox
+
+Verifying a sending domain does not move an existing mailbox into Hellotext. A new email written directly to `support@acme.com` continues to follow that address's existing incoming-mail setup.
+
+Sending from that address in Hellotext and receiving replies through the supplied reply address are separate from importing mailbox history or receiving every new email sent to the domain. If you need broader incoming-mail routing, discuss the setup with [Hellotext support]({% link _troubleshooting-deliverability/contact-hellotext-support.md %}).
+
+## Conversation ownership and reply windows
+
+Email conversations use the shared Inbox workflow. Teammates can assign work, add internal notes, close a conversation, and handle subsequent replies with the customer's history available.
+
+Email does not have a 24-hour reply window. The channel does not become unavailable simply because the customer has not written recently. Your sender must still be active, and the customer, conversation, subscription, and other sending conditions must still allow the intended message.
+
+Closing or snoozing an Inbox conversation is a team-workflow action. It is separate from the Email channel's ability to send. A supported new customer reply can bring the conversation back for attention.
+
+Keep reading: [Conversation lifecycle in Inbox]({% link _team/conversation-lifecycle.md %}) and [Assign conversations]({% link _team/assigning-conversations.md %}).
+
+## Subscription status and unsubscribe requests
+
+A customer's email address is a destination, not evidence that the customer wants marketing messages. Review the profile's subscription information and the purpose of the contact before sending.
+
+An ordinary email sent manually from the Inbox does not automatically include an unsubscribe link in its footer. If the customer asks your team to stop marketing messages, record the request using the customer's subscription controls and follow the business's consent process.
+
+For an email that includes an **Unsubscribe** link, the customer opens a confirmation page and presses **Unsubscribe** to submit the request. The page then displays **Request received** while Hellotext processes the preference update. Opening the link alone does not submit the unsubscribe request.
+
+
+ An email unsubscribe updates the customer's subscription status for that Hellotext business across channels. It is not limited to one email address or only the Email channel.
+
+
+Unsubscribing does not delete the customer profile or its conversation history. Do not switch to another channel to bypass the recorded preference.
+
+If Hellotext receives a spam or abuse complaint for a sent email, it records the customer's unsubscribe while preserving the message's existing delivery state. A bounced or rejected email is handled as a delivery failure; it is not the same as an unsubscribe request.
+
+Keep reading: [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Understand sending, delivery, and read information
+
+The conversation can show several kinds of message information as updates arrive:
+
+| Information | What it tells you |
+| --- | --- |
+| **Sending** | Hellotext is processing the outbound message. |
+| **Sent** | The message has been handed off for sending. This alone does not confirm delivery to the recipient. |
+| **Delivered** | The recipient's mail service has accepted the message. It does not guarantee placement in the primary inbox. |
+| **Seen or read information** | An email-open notification was reported. It does not prove the customer read or understood the message. |
+| **Failed** | Sending could not be completed, or a rejection or bounce was reported. |
+| **Received** | A supported customer reply was recorded in the conversation. |
+
+Delivery and open information can arrive separately. An absent read timestamp does not prove that the customer has not opened the email. Treat the customer's reply or another explicit action as stronger evidence of engagement.
+
+Inspect the message's information and any available failure reason before sending it again. Some failures provide only a general error, so do not expect a detailed mailbox diagnosis for every unsuccessful email.
+
+Keep reading: [Why a message did not send]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %}).
+
+## Troubleshoot an Email conversation
+
+### Email is missing from the destination menu
+
+Check that the customer's profile has an email address and that the business has a verified, active sender. If the sender was recently added or its domain was changed, follow its DNS instructions and allow verification to complete.
+
+If the only destination on the profile is Email and no Email sender is active, the conversation cannot offer a usable Email composer. Review the sender setup rather than repeatedly adding the same customer address.
+
+### The message used an unexpected sender or subject
+
+The destination menu chooses the recipient. The sender comes from the Email channel, and the current subject comes from the business name.
+
+Review the sender's name and address in **Settings > Integrations**. If you have several senders, check which channel the conversation used. Contact support if you need help identifying the sender before sending further messages.
+
+### The customer cannot find a sent email
+
+Confirm the exact recipient address and review whether the message has delivery information or a failure. Ask the customer to check their spam or junk folder as well as their usual inbox.
+
+If the email is still sending, give processing time to complete. If it failed, review the available reason, correct the destination or content when appropriate, and check the total attachment size before retrying.
+
+### The customer's reply does not appear
+
+Confirm that the customer replied to an email sent from Hellotext, used the supplied reply address, and replied from the original recipient address. Check that the sending channel is still active and that the customer or conversation has not been blocked or removed.
+
+Incoming replies must also pass the receiving checks. If a reply still does not appear, contact support with the original message, recipient address, approximate reply time, and whether the reply included attachments. There is no need to recreate the sender just to investigate a missing reply.
+
+### An attachment fails or looks different
+
+Check the accepted file type and size, confirm that the upload finished, and try a smaller supported export when necessary. A file's appearance in the customer's email application may differ from its preview in Hellotext.
+
+For a large document or media file, consider sharing an appropriate download link. Keep access to the linked file suitable for the intended customer.
+
+## First Email conversation checklist
+
+Before your team relies on Email conversations in the Inbox, confirm that:
+
+1. The intended sender is verified and active in the correct business.
+2. A test customer's email address is saved correctly on the profile.
+3. Selecting that address sends through Email.
+4. The received message shows the expected sender, business name, text, and attachments.
+5. A reply from the same recipient address appears in the correct Inbox conversation.
+6. The right teammate or team takes responsibility for the reply.
+7. Your team understands sender selection, delivery information, and the scope of unsubscribe requests.
+
+## Related guides
+
+- [Set up email sending]({% link _integrations/set-up-email-sending.md %})
+- [Messaging channels overview]({% link _numbers/messaging-overview.md %})
+- [Inbox and conversations overview]({% link _team/inbox-overview.md %})
+- [Message editor overview]({% link _numbers/message-editor-overview.md %})
+- [Customer profiles]({% link _audience/customer-profiles.md %})
+- [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %})
+- [Tracked links]({% link _analytics-reporting-attribution/tracked-links.md %})
+- [Why a message did not send]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %})
diff --git a/docs/editorial-work/captures/email-completion-20261011/originals/_i18n/es/numbers/email-channel-fundamentals.md b/docs/editorial-work/captures/email-completion-20261011/originals/_i18n/es/numbers/email-channel-fundamentals.md
new file mode 100644
index 00000000..33b9fd5f
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/originals/_i18n/es/numbers/email-channel-fundamentals.md
@@ -0,0 +1,250 @@
+Usa Correo electrónico cuando tus clientes necesiten un mensaje que puedan recibir y responder desde su aplicación de correo habitual. Tu equipo envía desde una dirección del dominio de tu negocio y gestiona las respuestas compatibles en el Inbox de Hellotext, junto a las demás conversaciones del cliente.
+
+Esta guía explica el uso diario del canal de correo electrónico después de agregar un remitente. Para conocer el formulario del remitente, los registros DNS y la verificación del dominio, sigue [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %}).
+
+
+ Correo electrónico está disponible en Enterprise. El dominio de un remitente guardado debe terminar de verificarse antes de que su canal esté disponible para enviar.
+
+
+## Para qué sirve mejor el correo electrónico
+
+Usa Correo electrónico para:
+
+- Conversaciones individuales con clientes desde el Inbox.
+- Respuestas detalladas que necesitan párrafos y un registro escrito.
+- Soporte y seguimiento de pedidos con clientes que prefieren el correo.
+- Compartir documentos, imágenes y otros archivos compatibles.
+- Continuar una conversación después de que el cliente responda a un correo enviado desde Hellotext.
+
+El correo electrónico no requiere que el cliente instale una aplicación de mensajería ni que tenga un número de teléfono en su perfil. Sí necesitas la dirección correcta y permiso para contactar al cliente con el propósito del mensaje.
+
+## Antes de enviar desde el Inbox
+
+Antes de enviar un correo individual desde el Inbox, confirma que:
+
+- Estás trabajando en el negocio correcto de Hellotext.
+- El negocio tiene Correo electrónico habilitado y al menos un remitente de correo verificado y activo.
+- El perfil del cliente contiene la dirección de correo que quieres usar.
+- Tienes acceso a la conversación de ese cliente en el Inbox.
+- El cliente y la conversación están disponibles para el contacto que quieres realizar.
+- Alguien de tu equipo es responsable de gestionar las respuestas.
+
+La integración del remitente y la dirección de correo del cliente cumplen funciones distintas. Agregar un remitente no agrega direcciones de correo a los perfiles de clientes. Agregar la dirección de un cliente no verifica tu dominio de envío ni establece el consentimiento de ese cliente.
+
+Sigue leyendo: [Cómo funcionan los perfiles de clientes]({% link _audience/customer-profiles.md %}) y [A quién puedo escribirle: consentimiento y estado de suscripción]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Dónde puedes usar correo electrónico
+
+El Inbox ofrece un destino de correo electrónico para los clientes que tienen una dirección de correo cuando el negocio cuenta con un remitente de correo activo.
+
+El creador de campañas muestra Correo electrónico como opción de entrega, pero seleccionarla por sí sola no habilita el envío. Para enviar una campaña por correo, el negocio necesita acceso al canal según su suscripción y un remitente verificado y activo. Conectar un remitente no cambia automáticamente los canales de una campaña existente.
+
+Las rutas pueden enviar correos desde pasos de Mensaje o Pregunta configurados con un diseño de correo, y las misiones proactivas compatibles pueden seleccionar este canal. Cada envío depende de las reglas del flujo, de un destinatario apto y del acceso y remitente del negocio. Usa el Inbox para conversaciones individuales por correo y para gestionar las respuestas compatibles.
+
+## Entiende el remitente, el destinatario y la dirección de respuesta
+
+Una conversación por correo utiliza tres direcciones o identidades:
+
+| Dato | Qué significa | De dónde proviene |
+| --- | --- | --- |
+| **Remitente** | El nombre y la dirección de correo del negocio que aparecen como remitente del mensaje. | El remitente de correo asociado al canal de correo electrónico activo. |
+| **Destinatario** | La dirección del cliente que recibirá este mensaje. | La dirección de correo que eliges del perfil del cliente en el menú de destino. |
+| **Dirección de respuesta** | La dirección que utiliza la aplicación de correo del cliente cuando elige Responder. | Hellotext la proporciona automáticamente para asociar la respuesta con la conversación. |
+
+Por ejemplo, tu remitente puede ser `support@acme.com` y tu cliente puede recibir el mensaje en `alex@example.com`. La dirección de respuesta puede ser distinta de `support@acme.com`; así recibe Hellotext la respuesta para la conversación.
+
+El menú de destino muestra las direcciones de correo del cliente. No es una lista de los remitentes de tu negocio. Cuando eliges una dirección, Hellotext usa el remitente activo de la conversación de correo existente, si está disponible, o un canal de correo electrónico disponible para un destino nuevo.
+
+Si tu negocio tiene varios remitentes activos, verifica cuál se utiliza antes de depender de una dirección de origen específica. El menú de destino del Inbox no ofrece actualmente un selector separado de remitentes de correo.
+
+Para cambiar el nombre o la dirección de un remitente, usa su acción **Editar** en **Ajustes > Integraciones**. Cambiar su dominio requiere una nueva verificación. Consulta [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %}) antes de realizar ese cambio.
+
+## Envía un correo desde el Inbox
+
+1. Abre la conversación del cliente en el **Inbox**.
+2. Revisa el perfil del cliente y confirma que la dirección de correo sea correcta. Agrega o corrige la dirección en el perfil si es necesario.
+3. Abre el menú de destino junto al editor de mensajes.
+4. Busca el grupo **Correo electrónico**.
+5. Selecciona la dirección del cliente a la que quieres enviar. Si el perfil tiene más de una, elige la que debe recibir este mensaje.
+6. Escribe tu mensaje. Usa párrafos claros, agrega los links necesarios y adjunta archivos compatibles cuando haga falta.
+7. Comprueba que Correo electrónico esté seleccionado antes de enviar, especialmente si antes estabas respondiendo por otro canal.
+8. Envía el mensaje y revisa su información de envío o entrega en la conversación.
+
+Seleccionar una dirección de correo envía el mensaje a ese destino. No envía copias a todas las direcciones del perfil. El menú de destino de correo electrónico no ofrece campos CC ni CCO.
+
+Si Correo electrónico es el único destino disponible del cliente, Hellotext puede abrir el editor con ese canal seleccionado cuando hay un remitente activo. Revisa siempre el destino si el cliente también tiene números de teléfono u otros canales conectados.
+
+Si falta el grupo Correo electrónico, revisa la dirección del perfil y la activación del remitente antes de intentar enviar. Un dominio pendiente de verificación no ofrece un canal de envío activo.
+
+Sigue leyendo: [Resumen del editor de mensajes]({% link _numbers/message-editor-overview.md %}).
+
+## Qué recibe el cliente
+
+Hellotext presenta el mensaje como un correo con el nombre del negocio, el cuerpo del mensaje y un pie que muestra el nombre y la dirección del remitente. También incluye una versión de texto sin formato para las aplicaciones de correo que la utilizan.
+
+El asunto actual del correo usa el nombre del negocio. El editor del Inbox no ofrece un campo de asunto separado para cada mensaje. El nombre del remitente proviene de su integración; no cambia automáticamente al nombre de la persona del equipo que hizo clic en enviar.
+
+El cuerpo usa el texto y los saltos de párrafo de tu mensaje. No dependas de que los estilos copiados, el HTML personalizado o los controles interactivos de otro canal se vean exactamente igual en el correo. Los archivos se entregan como adjuntos y la aplicación de correo del cliente controla cómo se previsualizan o descargan.
+
+El diseño se adapta a pantallas más pequeñas, pero distintas aplicaciones de correo pueden mostrar el mismo mensaje de manera diferente. Revisa un mensaje recibido real para evaluar la apariencia, los saltos de línea y los adjuntos.
+
+### Links y personalización
+
+Usa la herramienta de links del editor cuando necesites un link con seguimiento y comprueba su destino antes de enviar. Usa etiquetas de personalización solo cuando el perfil del cliente tenga los valores necesarios para producir un mensaje completo.
+
+Revisa el texto final con datos realistas de clientes. Un nombre faltante, una dirección desactualizada o un link que lleva al producto equivocado pueden hacer que un correo entregado correctamente no resulte útil.
+
+Sigue leyendo: [Links con tracking]({% link _analytics-reporting-attribution/tracked-links.md %}) y [Etiquetas de personalización]({% link _audience/personalization-tags.md %}).
+
+## Longitud del texto y archivos adjuntos
+
+El correo electrónico permite textos más largos que una respuesta breve de chat, pero el editor sigue aplicando límites:
+
+| Elemento | Límite o comportamiento |
+| --- | --- |
+| **Texto del mensaje** | Hasta 100.000 caracteres en el editor de correo electrónico. |
+| **Una imagen cargada** | Hasta 25 MB por archivo. |
+| **Un documento cargado** | Hasta 25 MB por archivo. |
+| **Un archivo de audio o video cargado** | Hasta 25 MB por archivo. |
+| **Varios adjuntos** | Cada archivo debe ser aceptado al cargarlo. El correo completo también debe respetar los límites de tamaño de mensaje de los servicios de envío y recepción. |
+
+Que la carga de un archivo se acepte no garantiza que el servicio de correo de cada destinatario acepte el mensaje completo. Varios archivos grandes pueden hacer que el correo sea demasiado pesado, aunque cada archivo esté permitido por separado. Usa archivos más pequeños o comparte un link de descarga adecuado cuando no sea necesario incluir el archivo completo en el mensaje.
+
+Los tipos de archivo compatibles incluyen:
+
+- **Imágenes:** JPEG, PNG, GIF, WebP, AVIF, HEIC, HEIF, BMP, TIFF y SVG.
+- **Documentos:** PDF, Word, Excel, PowerPoint, archivos OpenDocument, RTF, texto sin formato y CSV.
+- **Audio:** archivos compatibles AAC, audio MP4, MP3, AMR, Ogg, Opus, WAV, FLAC y audio WebM.
+- **Video:** archivos compatibles MP4, MPEG, 3GP, QuickTime, WebM y AVI.
+- **Otros archivos:** archivos compatibles ZIP, Gzip, EPUB, JSON, XML, HTML, de calendario y de contactos.
+
+Elige un tipo de archivo compatible y mantén cada archivo dentro del límite de tamaño. Si se rechaza un archivo, usa una exportación compatible o comparte un link adecuado. Cambiar solo la extensión del nombre no convierte el archivo.
+
+Usa el control de adjuntos del editor, espera a que termine la carga y confirma que los archivos correctos estén adjuntos antes de enviar. Revisa sus nombres y contenidos para enviar la versión correcta al cliente correcto.
+
+## Cómo llegan las respuestas del cliente al Inbox
+
+Después de recibir un correo enviado desde Hellotext, el cliente debe:
+
+1. Abrir el mensaje en su aplicación de correo habitual.
+2. Elegir **Responder**.
+3. Mantener la dirección de respuesta que proporciona la aplicación de correo.
+4. Responder desde la misma dirección que recibió el mensaje.
+
+Hellotext asocia una respuesta compatible con el correo saliente original, el perfil del cliente y la conversación. Tu equipo puede leerla y responder desde el Inbox.
+
+Una respuesta puede incluir texto y adjuntos compatibles. El Inbox muestra el contenido y los archivos con su presentación habitual de mensajes. No reproduce el diseño HTML completo del correo del cliente como una vista de su casilla.
+
+### Respuestas desde otra dirección
+
+Para asociar una respuesta se espera la dirección del destinatario original. Si el cliente responde desde otra cuenta, o reenvía el correo a otra persona que luego responde, es posible que no se cree un mensaje asociado en el Inbox.
+
+Cuando pruebes las respuestas, usa la misma dirección que recibió el correo y no cambies la dirección de respuesta proporcionada. El asunto del correo por sí solo no alcanza para asociar cualquier mensaje con la conversación.
+
+### Correos nuevos enviados a la casilla existente de tu negocio
+
+Verificar un dominio de envío no traslada una casilla existente a Hellotext. Un correo nuevo escrito directamente a `support@acme.com` sigue la configuración de recepción que ya tenga esa dirección.
+
+Enviar desde esa dirección en Hellotext y recibir respuestas mediante la dirección de respuesta proporcionada son funciones distintas de importar el historial de una casilla o recibir todos los correos nuevos enviados al dominio. Si necesitas una configuración más amplia de recepción, consúltala con el [soporte de Hellotext]({% link _troubleshooting-deliverability/contact-hellotext-support.md %}).
+
+## Responsables de la conversación y ventanas de respuesta
+
+Las conversaciones de correo usan el flujo de trabajo compartido del Inbox. El equipo puede asignar el trabajo, agregar notas internas, cerrar una conversación y gestionar las respuestas posteriores con el historial del cliente disponible.
+
+El correo electrónico no tiene una ventana de respuesta de 24 horas. El canal no deja de estar disponible simplemente porque el cliente no haya escrito recientemente. El remitente debe seguir activo, y el cliente, la conversación, la suscripción y las demás condiciones de envío deben permitir el mensaje que quieres enviar.
+
+Cerrar o posponer una conversación del Inbox es una acción del flujo de trabajo del equipo. Es independiente de la capacidad de envío del canal de correo electrónico. Una nueva respuesta compatible del cliente puede devolver la conversación a la atención del equipo.
+
+Sigue leyendo: [Ciclo de una conversación en el Inbox]({% link _team/conversation-lifecycle.md %}) y [Asigna conversaciones]({% link _team/assigning-conversations.md %}).
+
+## Estado de suscripción y solicitudes de baja
+
+La dirección de correo de un cliente es un destino, no una prueba de que quiera recibir mensajes de marketing. Revisa la información de suscripción del perfil y el propósito del contacto antes de enviar.
+
+Un correo habitual enviado manualmente desde el Inbox no incluye automáticamente un link para cancelar la suscripción en su pie. Si el cliente pide al equipo dejar de recibir mensajes de marketing, registra la solicitud con los controles de suscripción del cliente y sigue el proceso de consentimiento del negocio.
+
+En un correo que incluye un link **Cancelar suscripción**, el cliente abre una página de confirmación y presiona **Cancelar suscripción** para enviar la solicitud. Luego, la página muestra **Solicitud recibida** mientras Hellotext procesa la actualización de preferencias. Abrir el link por sí solo no envía la solicitud de baja.
+
+
+ Una baja por correo actualiza el estado de suscripción del cliente para ese negocio de Hellotext en todos los canales. No se limita a una dirección de correo ni solamente al canal de correo electrónico.
+
+
+Cancelar la suscripción no elimina el perfil del cliente ni su historial de conversaciones. No cambies a otro canal para evitar la preferencia registrada.
+
+Si Hellotext recibe una queja de spam o abuso por un correo enviado, registra la baja del cliente y conserva el estado de entrega existente del mensaje. Un correo rebotado o rechazado se trata como un fallo de entrega; no equivale a una solicitud de baja.
+
+Sigue leyendo: [A quién puedo escribirle: consentimiento y estado de suscripción]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Entiende la información de envío, entrega y lectura
+
+La conversación puede mostrar varios tipos de información del mensaje a medida que llegan las actualizaciones:
+
+| Información | Qué indica |
+| --- | --- |
+| **Enviando** | Hellotext está procesando el mensaje saliente. |
+| **Enviado** | El mensaje se pasó al servicio de envío. Esto por sí solo no confirma la entrega al destinatario. |
+| **Entregado** | El servicio de correo del destinatario aceptó el mensaje. No garantiza que aparezca en la bandeja de entrada principal. |
+| **Leído** | Se recibió una notificación de apertura del correo. No demuestra que el cliente haya leído o entendido el mensaje. |
+| **Fallo al enviar** | No se pudo completar el envío o se informó un rechazo o rebote. |
+| **Recibido** | Se registró una respuesta compatible del cliente en la conversación. |
+
+La información de entrega y apertura puede llegar por separado. Que no haya una hora de lectura no demuestra que el cliente no haya abierto el correo. Una respuesta del cliente u otra acción explícita son señales más claras de interacción.
+
+Revisa la información del mensaje y cualquier motivo de fallo disponible antes de volver a enviarlo. Algunos fallos solo proporcionan un error general, por lo que no debes esperar un diagnóstico detallado de la casilla para cada correo que no se entrega.
+
+Sigue leyendo: [Por qué no se envió un mensaje]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %}).
+
+## Soluciona problemas de una conversación por correo
+
+### Correo electrónico no aparece en el menú de destino
+
+Comprueba que el perfil del cliente tenga una dirección de correo y que el negocio tenga un remitente verificado y activo. Si el remitente se agregó recientemente o se cambió su dominio, sigue sus instrucciones DNS y espera a que termine la verificación.
+
+Si Correo electrónico es el único destino del perfil y no hay un remitente de correo activo, la conversación no puede ofrecer un editor de correo utilizable. Revisa la configuración del remitente en lugar de agregar repetidamente la misma dirección del cliente.
+
+### El mensaje usó un remitente o un asunto inesperados
+
+El menú de destino elige el destinatario. El remitente proviene del canal de correo electrónico y el asunto actual proviene del nombre del negocio.
+
+Revisa el nombre y la dirección del remitente en **Ajustes > Integraciones**. Si tienes varios remitentes, comprueba qué canal usó la conversación. Contacta al soporte si necesitas ayuda para identificar el remitente antes de enviar más mensajes.
+
+### El cliente no encuentra un correo enviado
+
+Confirma la dirección exacta del destinatario y revisa si el mensaje tiene información de entrega o un fallo. Pide al cliente que revise la carpeta de spam o correo no deseado, además de su bandeja de entrada habitual.
+
+Si el correo todavía se está enviando, espera a que termine el procesamiento. Si falló, revisa el motivo disponible, corrige el destino o el contenido cuando corresponda y comprueba el tamaño total de los adjuntos antes de volver a intentarlo.
+
+### La respuesta del cliente no aparece
+
+Confirma que el cliente haya respondido a un correo enviado desde Hellotext, que haya usado la dirección de respuesta proporcionada y que haya respondido desde la dirección del destinatario original. Revisa que el canal de envío siga activo y que el cliente o la conversación no se hayan bloqueado o eliminado.
+
+Las respuestas entrantes también deben superar las comprobaciones de recepción. Si una respuesta sigue sin aparecer, contacta al soporte con el mensaje original, la dirección del destinatario, la hora aproximada de la respuesta y si incluía adjuntos. No necesitas volver a crear el remitente solo para investigar una respuesta faltante.
+
+### Un adjunto falla o se ve diferente
+
+Revisa el tipo y el tamaño de archivo aceptados, confirma que la carga haya terminado y prueba una exportación compatible más pequeña cuando sea necesario. La apariencia del archivo en la aplicación de correo del cliente puede diferir de su vista previa en Hellotext.
+
+Para un documento o archivo multimedia grande, considera compartir un link de descarga adecuado. Mantén el acceso al archivo enlazado apropiado para el cliente al que se dirige.
+
+## Checklist para la primera conversación por correo
+
+Antes de que tu equipo dependa de las conversaciones por correo en el Inbox, confirma que:
+
+1. El remitente elegido esté verificado y activo en el negocio correcto.
+2. La dirección de un cliente de prueba esté guardada correctamente en su perfil.
+3. Seleccionar esa dirección envíe a través de Correo electrónico.
+4. El mensaje recibido muestre el remitente, el nombre del negocio, el texto y los adjuntos esperados.
+5. Una respuesta desde la misma dirección del destinatario aparezca en la conversación correcta del Inbox.
+6. La persona o el equipo adecuados se hagan responsables de la respuesta.
+7. Tu equipo entienda la selección del remitente, la información de entrega y el alcance de las solicitudes de baja.
+
+## Guías relacionadas
+
+- [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %})
+- [Resumen de canales de mensajería]({% link _numbers/messaging-overview.md %})
+- [Resumen de inbox y conversaciones]({% link _team/inbox-overview.md %})
+- [Resumen del editor de mensajes]({% link _numbers/message-editor-overview.md %})
+- [Cómo funcionan los perfiles de clientes]({% link _audience/customer-profiles.md %})
+- [A quién puedo escribirle: consentimiento y estado de suscripción]({% link _audience/consent-and-subscriber-status.md %})
+- [Links con tracking]({% link _analytics-reporting-attribution/tracked-links.md %})
+- [Por qué no se envió un mensaje]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %})
diff --git a/docs/editorial-work/captures/email-completion-20261011/originals/_numbers/email-channel-fundamentals.md b/docs/editorial-work/captures/email-completion-20261011/originals/_numbers/email-channel-fundamentals.md
new file mode 100644
index 00000000..441a1076
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/originals/_numbers/email-channel-fundamentals.md
@@ -0,0 +1,19 @@
+---
+languages: ["en", "es"]
+
+en:
+ title: Email channel fundamentals
+ description: Learn how to send emails from the Inbox, receive customer replies, share attachments, and understand delivery and subscription status.
+es:
+ title: Fundamentos del canal de correo electrónico
+ description: Aprende a enviar correos desde el Inbox, recibir respuestas de clientes, compartir archivos y entender los estados de entrega y suscripción.
+
+permalink: email-channel-fundamentals
+permalink_es: fundamentos-canal-correo-electronico
+
+layout: guide
+topic: numbers
+popular: false
+---
+
+{% translate_file numbers/email-channel-fundamentals.md %}
diff --git a/docs/editorial-work/captures/email-completion-20261011/originals/docs/editorial-work/progress.csv b/docs/editorial-work/captures/email-completion-20261011/originals/docs/editorial-work/progress.csv
new file mode 100644
index 00000000..11c6138b
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/originals/docs/editorial-work/progress.csv
@@ -0,0 +1,155 @@
+article_key,editorial_status,local_verified_commit,work_record
+analytics-reporting-attribution/analytics-overview.md,local_verified,a395a2b,docs/editorial-work/analytics-overview.md
+analytics-reporting-attribution/campaign-reporting.md,local_verified,60b8625e78fe36b394d23b67135a9d80d792f2d1,docs/editorial-work/campaign-reporting.md
+analytics-reporting-attribution/dashboard-guide.md,local_verified,c0043c8e66f3127ccd037e73ee079dcc1ab3290c,docs/editorial-work/dashboard-guide.md
+analytics-reporting-attribution/data-completeness-and-reporting-gaps.md,local_verified,dc8159b3e2cf39eba913c6ed048e60aff72345f0,docs/editorial-work/data-completeness-and-reporting-gaps.md
+analytics-reporting-attribution/demand-insights-guide.md,local_verified,2fc96f2b5347afa9f0d93b45a1ae486320f6725c,docs/editorial-work/demand-insights-guide.md
+analytics-reporting-attribution/performance-report-guide.md,local_verified,3ef31ecaf306c1d46475cb13a970f1f6fd9e2b39,docs/editorial-work/performance-report-guide.md
+analytics-reporting-attribution/playbook-reporting.md,local_verified,389869fd74279e2c861b0cfb3da2eb52f84f37ea,docs/editorial-work/playbook-reporting.md
+analytics-reporting-attribution/revenue-report-guide.md,local_verified,dfa050108af7f6f3490404466677768f96878b3b,docs/editorial-work/revenue-report-guide.md
+analytics-reporting-attribution/sales-attribution.md,local_verified,fece70b,docs/editorial-work/sales-attribution.md
+analytics-reporting-attribution/service-quality-report-guide.md,local_verified,ef7a8d6da9ef2504135b9a171a14c27f8c8df17b,docs/editorial-work/service-quality-report-guide.md
+analytics-reporting-attribution/tracked-links.md,local_verified,2f5f47011d199f25a55895452558e041dbcb7921,docs/editorial-work/tracked-links.md
+analytics-reporting-attribution/workload-capacity-report-guide.md,local_verified,0246e0c8c304cf8d7e7e2d7e06a70ed95d766dfc,docs/editorial-work/workload-capacity-report-guide.md
+audience/audience-overview.md,local_verified,9deb417eb970a3039e59522a1d50e53bd61498af,docs/editorial-work/audience-overview.md
+audience/consent-and-subscriber-status.md,local_verified,50c987492608662a26e6b2bbfe2482ddbc4ec2ad,docs/editorial-work/consent-and-subscriber-status.md
+audience/custom-properties-and-events.md,local_verified,f452252,docs/editorial-work/custom-properties-and-events.md
+audience/customer-profiles.md,local_verified,b5eeff5,docs/editorial-work/customer-profiles.md
+audience/data-privacy-requests.md,local_verified,3fd70851c4e27ff74d15433582b682ce28798ab5,docs/editorial-work/data-privacy-requests.md
+audience/exporting-data.md,local_verified,0d32f2b9cb9da29821d276c5732900e1705031f6,docs/editorial-work/exporting-data.md
+audience/import-customer-profiles.md,local_verified,4926ef256078e1884e5623a425bb3577d4afe6a8,docs/editorial-work/import-customer-profiles.md
+audience/lists-and-segments.md,local_verified,c94f3cb3aa683d0394d00b0427c136916a512f4e,docs/editorial-work/lists-and-segments.md
+audience/lists.md,local_verified,d499c8bdb4c6032635f5c94e12e0559c1584f94a,docs/editorial-work/lists.md
+audience/personalization-tags.md,local_verified,5ca1587e,docs/editorial-work/personalization-tags.md
+audience/segments.md,local_verified,21f0e69,docs/editorial-work/segments-chooser-clean-crop.md
+billing/billing-overview.md,local_verified,89ea8bcb,docs/editorial-work/billing-overview.md
+billing/billing-settings-and-invoices.md,local_verified,43be3253,docs/editorial-work/billing-settings-and-invoices.md
+billing/billing-troubleshooting.md,local_verified,1df2f0d2,docs/editorial-work/billing-troubleshooting.md
+billing/change-or-cancel-your-plan.md,local_verified,b5ff3e23ba4d60249ba3840b6214441616f4c148,docs/editorial-work/change-or-cancel-plan.md
+billing/fair-use-message-policy.md,local_verified,2f5b9a1952e8b7d53a7b41eb2b8b118d293d3603,docs/editorial-work/fair-use-message-policy.md
+billing/how-pricing-works.md,local_verified,295ebb80,docs/editorial-work/how-pricing-works.md
+billing/performance-fee-calculation.md,local_verified,767f6f33a54c95f77a56b60889d29fead5110858,docs/editorial-work/performance-fee-calculation.md
+billing/sms-pricing-and-number-types.md,local_verified,295ebb80,docs/editorial-work/sms-pricing-and-number-types.md
+billing/understanding-plan-quotas.md,local_verified,c4e988ccec1d6ff3e43bdd5731e40f85db0045ff,docs/editorial-work/understanding-plan-quotas.md
+billing/whatsapp-fees.md,local_verified,c004d2bb3ee0d8a4cca6117036413e2579042165,docs/editorial-work/whatsapp-fees.md
+campaigns/campaign-best-practices.md,local_verified,022cc577,docs/editorial-work/campaign-best-practices.md
+campaigns/campaigns-overview.md,local_verified,cffe95ee,docs/editorial-work/campaigns-overview.md
+campaigns/creating-a-campaign.md,pending,,
+captures/capture-overview.md,local_verified,724549d93d1c574fb5823da44ced2da12ab4236a,docs/editorial-work/capture-overview.md
+captures/forms.md,local_verified,68ea8fc4e9071a73b4e745d9aaf4726848cd4328,docs/editorial-work/forms.md
+captures/property-collector-playbook.md,local_verified,2059d23c1b762a94e0ef23ad6f5ee7dc8e4c0cfb,docs/editorial-work/property-collector-playbook.md
+captures/qr-codes.md,local_verified,724549d93d1c574fb5823da44ced2da12ab4236a,docs/editorial-work/qr-codes.md
+captures/shareable-link.md,local_verified,9e66ca41ee3396cc60f434593961a1590b9c2ba2,docs/editorial-work/shareable-link.md
+captures/shopify-checkout.md,pending,,docs/editorial-work/shopify-checkout-layout.md
+captures/subscriber-booster-playbook.md,local_verified,fcf70608d29d66d12c5c2b016da115a9d140f35b,docs/editorial-work/subscriber-booster-playbook.md
+captures/webchat-widget-playbook.md,local_verified,f5404c53925c46fee470a57fc3d970db571ccd2e,docs/editorial-work/webchat-widget-playbook.md
+captures/website-popup.md,local_verified,fbb366c649e695ec68d0f16ff7cc3d860e8d5b51,docs/editorial-work/website-popup.md
+captures/wix-checkout.md,pending,,
+developers/api.md,out_of_scope,,
+developers/coupons-with-api.md,local_verified,6b3a13e24dd21fd39052b63a7381396d9ee9a354,docs/editorial-work/coupons-api.md
+developers/custom-actions.md,local_verified,1c3c7e8503ad69ee70d1839ef349985c86c843a0,docs/editorial-work/custom-actions.md
+developers/custom-store-integration.md,local_verified,573d8215d4ca05c358114483ed50e1413d73b6f2,docs/editorial-work/custom-store-integration.md
+developers/developers-overview.md,local_verified,a04fa378b70dac940493d2182ff78b0779a0b2d7,docs/editorial-work/developers-overview.md
+developers/external-tracking.md,local_verified,879fb1bedaded0f5e451bb2105a3595ac3f4bb4c,docs/editorial-work/external-tracking.md
+developers/objects.md,local_verified,c90187d02bd72980c8a400a465e9f9dee88cf223,docs/editorial-work/objects.md
+developers/orders-with-api.md,local_verified,12cd42398e6e0c96e21dbf4c943c2fc4c8992b1d,docs/editorial-work/orders-with-api.md
+developers/products-and-inventory-with-api.md,local_verified,9eb84f0ce33bc1b4550c9d4bdcc5c85d8cbc6a2c,docs/editorial-work/products-and-inventory-with-api.md
+developers/send-messages-with-api.md,local_verified,6e7ae88260f08f767f92b5fc7f7d63f2305cc227,docs/editorial-work/send-messages-with-api.md
+developers/send-sms-with-api.md,local_verified,8bed47fac86a9f0bf6007ee6223d355aa372d638,docs/editorial-work/send-sms-with-api.md
+developers/setup-push-with-hellotext-js.md,local_verified,fabd2f840c5df5aad690318436899be2c5aeb688,docs/editorial-work/setup-push-with-hellotext-js.md
+developers/templates-with-api.md,local_verified,ba704efc47015c09fe601055146083794b6ba2bb,docs/editorial-work/templates-with-api.md
+developers/tracking-events.md,local_verified,636f7d5e9c178b47af82a0ef6f9d9ed710443c1e,docs/editorial-work/tracking-events.md
+developers/tracking-on-campaigns-and-journeys.md,local_verified,2dca1a3801e7b645954348543f471337666a7add,docs/editorial-work/tracking-on-campaigns-and-journeys.md
+developers/tracking-unidentified-customers.md,local_verified,e729eb459de8478966fd2f0871d1dfa156c655fb,docs/editorial-work/tracking-unidentified-customers.md
+developers/troubleshoot-custom-integration.md,local_verified,2c862e33f65e4690613c586987f0dea9bb757677,docs/editorial-work/troubleshoot-custom-integration.md
+getting-started/first-wins-starter-pack.md,local_verified,6ef072e7,docs/editorial-work/first-wins-starter-pack.md
+getting-started/frequent-questions.md,local_verified,c8bb3e33668e075b532521120060b77a78ba1c7e,docs/editorial-work/frequent-questions.md
+getting-started/go-live-checklist.md,local_verified,2af0d8f720089cb0c3747ff90ec5d5179a0f9963,docs/editorial-work/go-live-checklist.md
+getting-started/how-hellotext-works.md,local_verified,dd237037fa7387704e78bdd917481d3ec27b7ab8,docs/editorial-work/how-hellotext-works.md
+getting-started/implementation-paths.md,local_verified,e0dc5cadf816044cb5d7705cead91e9f52f7681a,docs/editorial-work/implementation-paths.md
+getting-started/launch-checklist.md,local_verified,02ab46afec935bbdc77c2dd76e1d69620fcfa5a7,docs/editorial-work/launch-checklist.md
+getting-started/measure-success-first-7-days.md,local_verified,f35070b3dcd8bc8639382937e6cd7c0b213df0e0,docs/editorial-work/measure-success-first-7-days.md
+getting-started/setting-up-your-business.md,local_verified,5ff2269fdfdd73edb91b8d4e779954354ceff859,docs/editorial-work/setting-up-your-business.md
+getting-started/tips-and-best-practices.md,local_verified,c5fcdf75b8938baa08223518bc874f45ea152d41,docs/editorial-work/tips-and-best-practices.md
+getting-started/what-is-hellotext.md,local_verified,44df74ef1a250a6ada8a8eba6c4111759963c9cc,docs/editorial-work/what-is-hellotext.md
+integrations/connect-catalog-to-whatsapp.md,pending,,
+integrations/connect-facebook-messenger.md,pending,,
+integrations/connect-fenicio.md,local_verified,b4d8dcea091cd3f09a4c6651c7fe51b92981cc48,docs/editorial-work/connect-fenicio.md
+integrations/connect-instagram-dm.md,pending,,
+integrations/connect-mercado-libre.md,pending,,
+integrations/connect-shopify.md,pending,,
+integrations/connect-vtex.md,pending,,
+integrations/connect-whatsapp.md,pending,,
+integrations/connect-wix.md,pending,,
+integrations/connect-woo.md,pending,,
+integrations/custom-domain-for-short-links.md,local_verified,75252a1f5bc4662d5522e0974c56842caaff04f5,docs/editorial-work/custom-domain-for-short-links.md
+integrations/product-catalog-sync.md,local_verified,50dfa4510af32d1a51d47eb4639c477bea509d4d,docs/editorial-work/product-catalog-sync.md
+integrations/set-up-email-sending.md,pending,,
+integrations/setup-overview.md,local_verified,f7e828253f1987a03587f7cf6a0e17c01bf86c01,docs/editorial-work/setup-overview.md
+integrations/setup-push-notifications.md,local_verified,0a3eac822ac85f351b4ed4ec1978aa81af663e15,docs/editorial-work/setup-push-notifications.md
+integrations/transferring-ownership.md,local_verified,cde33e9ab37d683f9e90360a8c8808407836ae81,docs/editorial-work/transferring-ownership.md
+integrations/verify-data-and-signals.md,local_verified,299131d94e2040c023d19d5792c867d02de8839c,docs/editorial-work/verify-data-and-signals.md
+journeys/abandoned-cart-route-vs-ai-playbook.md,local_verified,71b191cf44dd3414c11757141392342b0db1d198,docs/editorial-work/abandoned-cart-route-vs-ai-playbook.md
+journeys/ai-cart-saver-playbook.md,pending,,
+journeys/anniversary-surprise-playbook.md,pending,,
+journeys/back-in-stock-pounce.md,pending,,
+journeys/birthday-bash-playbook.md,pending,,
+journeys/browse-recovery-playbook.md,pending,,
+journeys/cart-saver-route.md,pending,,
+journeys/choose-your-first-playbook.md,local_verified,1419af6f,docs/editorial-work/choose-your-first-playbook.md
+journeys/complete-the-look-playbook.md,pending,,
+journeys/cross-sell-driver-playbook.md,pending,,
+journeys/csat-pulse-playbook.md,local_verified,f9b3231d1d4b68faadedec2c296d23180c6c678a,docs/editorial-work/csat-completion-20261011.md
+journeys/custom-agent-playbook.md,local_verified,c9c77bc46cb5abcdce68febcbb7a74504c73e373,docs/editorial-work/journeys-followup-revalidation-20261010.md
+journeys/custom-journey.md,local_verified,efcdcb963f6f23984f45a6c86e94e90eb2f2f5f8,docs/editorial-work/custom-journey.md
+journeys/dormant-revival-playbook.md,pending,,
+journeys/first-purchase-driver-playbook.md,pending,,
+journeys/getting-started-with-journeys.md,local_verified,efcdcb963f6f23984f45a6c86e94e90eb2f2f5f8,docs/editorial-work/getting-started-with-journeys.md
+journeys/how-hellotext-decides-whether-a-playbook-can-send.md,local_verified,211a6e145ab49b1199cc2faccbfd39a98163f4d6,docs/editorial-work/how-hellotext-decides-whether-a-playbook-can-send.md
+journeys/how-to-customize-a-playbook-safely.md,local_verified,76dfd6364331a16100696ade6d44e27ce60dc9c3,docs/editorial-work/customize-safely-completion.md
+journeys/how-to-enable-a-playbook.md,local_verified,4b60266d55c5af508192df9be25b1bc6552deff8,docs/editorial-work/how-to-enable-a-playbook.md
+journeys/how-to-write-a-great-prompt.md,local_verified,bafcb99742bd5b3185f7c5cd20cf33752bf2ab64,docs/editorial-work/how-to-write-a-great-prompt.md
+journeys/instant-answers-playbook.md,local_verified,c9c77bc46cb5abcdce68febcbb7a74504c73e373,docs/editorial-work/journeys-followup-revalidation-20261010.md
+journeys/nps-pulse-playbook.md,local_verified,c38c69518c0b80cac09f7c85db53db58d3e38679,docs/editorial-work/nps-pulse-visuals-20261011.md
+journeys/order-cancellation-assistant-playbook.md,in_progress,,docs/editorial-work/playbook-followup.md
+journeys/order-update-playbook.md,in_progress,,docs/editorial-work/playbook-followup.md
+journeys/playbook-library-by-mission.md,local_verified,5d4fb25be8d01b033efc85e4207c67f14f23e9fe,docs/editorial-work/playbook-library-by-mission.md
+journeys/playbooks-overview.md,local_verified,c5df3e21133e540ee792dd5049852b9463e1f59b,docs/editorial-work/playbooks-overview.md
+journeys/price-drop-pouncer.md,pending,,
+journeys/replenishment-driver-playbook.md,pending,,
+journeys/return-and-exchange-helper-playbook.md,local_verified,c9c77bc46cb5abcdce68febcbb7a74504c73e373,docs/editorial-work/journeys-followup-revalidation-20261010.md
+journeys/review-builder-playbook.md,pending,,
+journeys/smart-recommender-playbook.md,local_verified,5c25235e38e1defe08c17359a5de5d3a7e5872bf,docs/editorial-work/smart-recommender-playbook.md
+journeys/soft-reactivation-playbook.md,pending,,
+journeys/sunset-saver-playbook.md,pending,,
+journeys/troubleshoot-a-playbook-that-did-not-trigger-or-send.md,local_verified,95ff05bdae0f7b5a5402dae49fd47f005dfbf108,docs/editorial-work/troubleshoot-a-playbook-that-did-not-trigger-or-send.md
+journeys/what-are-signals.md,local_verified,4a36f7cacf225f5de1c2ad1a4ee2611880744d2e,docs/editorial-work/what-are-signals.md
+numbers/email-channel-fundamentals.md,pending,,
+numbers/exclusive-short-codes.md,local_verified,9251b8e6dc577e3642d0a3a03cd0105c5003fb6a,docs/editorial-work/exclusive-short-codes.md
+numbers/facebook-messenger-fundamentals.md,local_verified,2c71d7b6db11ed57836af245e376d51119d92fba,docs/editorial-work/facebook-messenger-fundamentals.md
+numbers/instagram-dm-fundamentals.md,local_verified,4a707bd63db12e5e91b311fe66e2c5c71c8a960f,docs/editorial-work/instagram-dm-fundamentals.md
+numbers/message-editor-basics.md,local_verified,08b588f6786c857070e350aeaa6396d85bcc004c,docs/editorial-work/message-editor-basics.md
+numbers/message-editor-overview.md,local_verified,7069de6a41a5082291dc259ab6cb19aabc7fdd38,docs/editorial-work/message-editor-overview.md
+numbers/messaging-overview.md,local_verified,e04f9413,docs/editorial-work/messaging-overview.md
+numbers/share-a-location.md,pending,,
+numbers/sms-channel-fundamentals.md,local_verified,99ccf2d7c78105da8c244c3a1473469c9a4b5175,docs/editorial-work/sms-channel-fundamentals.md
+numbers/whatsapp-channel-fundamentals.md,local_verified,1c50ccd00ce4fc17377e89cf270f6791351a6a56,docs/editorial-work/whatsapp-channel-fundamentals.md
+team/ai-handoff-to-inbox.md,local_verified,cd1666d163b4e3ffed11f6c7518db5915d6e2152,docs/editorial-work/ai-handoff-to-inbox.md
+team/assigning-conversations.md,local_verified,2c38d2f90748564ef859e8f5e3d0b84d2f78b310,docs/editorial-work/assigning-conversations.md
+team/conversation-lifecycle.md,local_verified,10cc0ce7ab004ad4f3ee3a008b9259e389f2e1f6,docs/editorial-work/conversation-lifecycle.md
+team/filter-and-search-inbox.md,visual_pending,d6d37946bd150ac95f45f0f75dcf6d816ea87a4e,docs/editorial-work/filter-and-search-inbox.md
+team/inbox-browser-notifications.md,local_verified,351bdaed92afed9059af748025dc1e753c708040,docs/editorial-work/inbox-browser-notifications.md
+team/inbox-overview.md,local_verified,d6d37946bd150ac95f45f0f75dcf6d816ea87a4e,docs/editorial-work/inbox-overview.md
+team/teams-and-inbox-capacity.md,local_verified,c0d8b63e1068eae01b028fb8d2d4d1f67d263101,docs/editorial-work/teams-and-inbox-capacity.md
+team/understanding-response-times.md,local_verified,f1783514787c2dc79dcf869dd46d56ca0db359dc,docs/editorial-work/understanding-response-times.md
+team/understanding-team-roles.md,local_verified,5318587939065b406f31aab600a5b992373c00c8,docs/editorial-work/understanding-team-roles.md
+troubleshooting-deliverability/contact-hellotext-support.md,local_verified,d11c5e102d42e9f46635eeb6ced8c7936612382b,docs/editorial-work/contact-hellotext-support.md
+troubleshooting-deliverability/sms-sending-limits-for-new-businesses.md,local_verified,f320c013205a26374093c51e4c56fe510959eb4a,docs/editorial-work/sms-sending-limits.md
+troubleshooting-deliverability/troubleshoot-a-capture.md,local_verified,876184f5a152e7e4f67c1b21cc776a2ca70855f1,docs/editorial-work/troubleshoot-a-capture.md
+troubleshooting-deliverability/troubleshoot-missing-signals-or-activity.md,local_verified,be76a7fd942d8fd504171fdc576b02fd89f6f52a,docs/editorial-work/troubleshoot-missing-signals-or-activity.md
+troubleshooting-deliverability/troubleshoot-pages-that-do-not-load.md,local_verified,97b816b80feea0d89b6726ed5d9aa3e0bd5f707b,docs/editorial-work/troubleshoot-pages-that-do-not-load.md
+troubleshooting-deliverability/troubleshoot-push-notifications.md,local_verified,aa27f339576a56ac1d3e644e7529c341185c6739,docs/editorial-work/troubleshoot-push-notifications.md
+troubleshooting-deliverability/troubleshoot-whatsapp-templates.md,pending,,
+troubleshooting-deliverability/troubleshooting-checklist.md,local_verified,9c3d37e94321f15ae405ee620855c85f244a25d5,docs/editorial-work/troubleshooting-checklist.md
+troubleshooting-deliverability/troubleshooting-overview.md,local_verified,02a10bff7618912fb3b733d067f8de1120d80d7c,docs/editorial-work/troubleshooting-overview.md
+troubleshooting-deliverability/why-a-message-did-not-send.md,local_verified,52a3db1b5911f2c869a4804c5e0d831392a7a7ea,docs/editorial-work/why-a-message-did-not-send.md
diff --git a/docs/editorial-work/captures/email-completion-20261011/pre-integration/en.md b/docs/editorial-work/captures/email-completion-20261011/pre-integration/en.md
new file mode 100644
index 00000000..b66e6ed8
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/pre-integration/en.md
@@ -0,0 +1,244 @@
+Use Email when customers need a message they can receive and reply to in their usual email application. Your team sends from an address on your business domain and manages supported replies in the Hellotext Inbox alongside the customer's other conversations.
+
+This guide explains everyday use of the Email channel after you have added a sender. For the sender form, DNS records, and domain verification, follow [Set up email sending]({% link _integrations/set-up-email-sending.md %}).
+
+
+ Email is available on Pro and Enterprise. A saved sender must finish domain verification before its channel becomes available for sending.
+
+
+## What Email is best for
+
+Use Email for:
+
+- One-to-one customer conversations from the Inbox.
+- Detailed answers that benefit from paragraphs and a written record.
+- Support and order follow-up with customers who prefer email.
+- Sharing images and information, with links to documents when needed.
+- Continuing a conversation after the customer replies to an email sent from Hellotext.
+
+Email does not require the customer to install a messaging app or have a phone number on their profile. You do need the correct email address and permission to contact the customer for the purpose of the message.
+
+## Before sending from the Inbox
+
+Before sending an individual Email from the Inbox, confirm that:
+
+- You are working in the correct Hellotext business.
+- The business has Email enabled and at least one verified, active email sender.
+- The customer profile contains the email address you intend to use.
+- You have access to that customer's Inbox conversation.
+- The customer and conversation are available for the intended contact.
+- Someone on your team is responsible for handling replies.
+
+The sender integration and the customer's email address serve different purposes. Adding a sender does not add email addresses to customer profiles. Adding a customer's email address does not verify your sending domain or establish that customer's consent.
+
+Keep reading: [Customer profiles]({% link _audience/customer-profiles.md %}) and [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Where you can use Email
+
+The Inbox destination menu can show **Email** before sending is ready. To send, you need an address on the customer profile, channel access, and an active sender; seeing the option does not confirm those requirements.
+
+The campaign creator shows Email as a delivery option, but selecting it does not by itself enable sending. To send an Email campaign, the business needs Email access through its subscription and a verified, active sender. Connecting a sender does not automatically change the delivery channels of an existing campaign.
+
+Journeys can send Email from Message or Question steps configured with an Email design, and compatible proactive playbooks can select this channel. Each send depends on the flow's rules, an eligible recipient, and the business's Email access and sender. Use the Inbox for individual Email conversations and supported replies.
+
+## Understand the sender, recipient, and reply address
+
+An email conversation uses three addresses or identities:
+
+| Detail | What it means | Where it comes from |
+| --- | --- | --- |
+| **Sender** | The name and business email address shown as the sender of the message. | The email sender associated with the active Email channel. |
+| **Recipient** | The customer's address that will receive this message. | The email address you select from the customer's profile in the destination menu. |
+| **Reply address** | The address the customer's email application uses when they choose Reply. | Hellotext supplies it automatically so it can associate the response with the conversation. |
+
+For example, your sender might be `support@example.com` and your customer might receive the message at `alex@example.com`. The reply address can be different from `support@example.com`; that is how Hellotext receives the response for the conversation.
+
+The destination menu lists the customer's email addresses. It is not a list of your business's senders. When you choose an address, Hellotext uses the existing Email conversation's active sender when available, or an available Email channel for a new destination.
+
+If your business has several active senders, verify which one is used before relying on a particular From address. The Inbox destination menu does not currently provide a separate Email sender picker.
+
+To change a sender's name or email address, use its **Edit** action in **Settings > Integrations**. Changing its domain requires verification again. See [Set up email sending]({% link _integrations/set-up-email-sending.md %}) before making that change.
+
+## Send an email from the Inbox
+
+1. Open the customer's conversation in the **Inbox**.
+2. Check the customer's profile and confirm the email address is correct. Add or correct the address on the profile if needed.
+3. Open the destination menu beside the message editor.
+4. Find the **Email** group.
+5. Select the customer's intended email address. If the profile has more than one, choose the address that should receive this message.
+6. Write the **Subject** and prepare the body in the Email editor. Organize the content into text blocks, adding images or actions when they help the customer.
+7. Open **Preview** to review the desktop and mobile layouts. Check the recipient, subject, text, and links before sending, especially if you were previously replying over another channel.
+8. Send the message and review its sending or delivery information in the conversation.
+
+When you send, only the selected address is used. No copies are sent to the other addresses on the profile. The Email destination menu does not provide CC or BCC fields.
+
+For a customer whose only available destination is Email, Hellotext can open the composer with Email selected when an active sender is available. Always check the destination when the customer also has phone numbers or other connected channels.
+
+If you cannot send through Email, check the profile's address, your plan access, and the sender's activation. A pending domain verification does not provide an active sending channel, even if the menu lets you explore the Email option.
+
+Keep reading: [Message editor overview]({% link _numbers/message-editor-overview.md %}).
+
+## What the customer receives
+
+Hellotext prepares the email from the design you edited. The selected appearance supplies its branding and footer; the sender name and address come from the Email channel. A plain-text version is also included for email applications that use it.
+
+Use **Subject** to write the email title. It is separate from the body and sender name; the sender name does not automatically change to the teammate who clicked Send.
+
+The body retains the design's blocks, such as text, images, and buttons. Images added to the design appear within the email; they are not automatically offered as downloadable file attachments. Do not rely on copied styling or another channel's controls to appear identically.
+
+Use **Preview** to review the unsent draft and switch between desktop and mobile layouts. Email applications can display the same design differently; a received test message lets you check the final appearance, line breaks, and links.
+
+The preview footer may show **Unsubscribe**. That link is not automatically added when you send a manual email from the Inbox.
+
+### Links and personalization
+
+Use the editor's link tool when you need a tracked link, and check its destination before sending. Use personalization tags only when the customer's profile has the values needed to produce a complete message.
+
+Review the final wording with realistic customer data. A missing name, an outdated address, or a link pointing to the wrong product can make a successfully delivered email unhelpful.
+
+Keep reading: [Tracked links]({% link _analytics-reporting-attribution/tracked-links.md %}) and [Personalization tags]({% link _audience/personalization-tags.md %}).
+
+## Text length and attachments
+
+The Email editor organizes content into blocks. Use its image controls; the file list for other channels does not describe what you can add to this design.
+
+| Item | Limit or behavior |
+| --- | --- |
+| **Subject** | Up to 998 characters. |
+| **Formatted text** | Validated per block; formatting also uses space. Simplify or split a block if the editor rejects its length. |
+| **Top-level blocks** | Up to 30 in the design. |
+| **An uploaded image** | PNG, JPEG, GIF, or WebP up to 5 MB. It becomes part of the email body. |
+| **Documents, audio, or video** | Share an appropriate link; the current Email editor does not offer the general file uploader for these attachments. |
+
+The formatted-text limit is not a fixed character count for the entire email. The combined design size is also validated. Keep the message concise and split information into useful blocks without repeating content.
+
+Wait for each image to finish loading and check its content in **Preview**. An accepted image does not guarantee that every email service will accept the complete message. Use smaller images when possible.
+
+To share a document or a large file, add a download link and check that the customer has access. Changing only a filename extension does not convert the file to a supported format.
+
+## How customer replies reach the Inbox
+
+After receiving an email sent from Hellotext, the customer should:
+
+1. Open the message in their usual email application.
+2. Choose **Reply**.
+3. Keep the reply address supplied by the email application.
+4. Reply from the same email address that received the message.
+
+Hellotext associates a supported reply with the original outgoing email, customer profile, and conversation. Your team can then read and answer it from the Inbox.
+
+A reply can include text and supported attachments. The Inbox retains supported elements of the received email, such as images, tables, and lists, and can group quoted text from earlier messages. Some styles or elements of the original email may appear differently.
+
+### Replies from another address
+
+Reply matching expects the original recipient's email address. A customer replying from another account, or forwarding the email to someone else who then replies, may not create a matching Inbox message.
+
+When testing replies, use the same address that received the email and leave the supplied reply address unchanged. The email subject alone is not enough to associate an arbitrary message with the conversation.
+
+### New emails sent to your existing business mailbox
+
+Verifying a sending domain does not move an existing mailbox into Hellotext. A new email written directly to `support@example.com` continues to follow that address's existing incoming-mail setup.
+
+Sending from that address in Hellotext and receiving replies through the supplied reply address are separate from importing mailbox history or receiving every new email sent to the domain. If you need broader incoming-mail routing, discuss the setup with [Hellotext support]({% link _troubleshooting-deliverability/contact-hellotext-support.md %}).
+
+## Conversation ownership and reply windows
+
+Email conversations use the shared Inbox workflow. Teammates can assign work, add internal notes, close a conversation, and handle subsequent replies with the customer's history available.
+
+Email does not have a 24-hour reply window. The channel does not become unavailable simply because the customer has not written recently. Your sender must still be active, and the customer, conversation, subscription, and other sending conditions must still allow the intended message.
+
+Closing or snoozing an Inbox conversation is a team-workflow action. It is separate from the Email channel's ability to send. A supported new customer reply can bring the conversation back for attention.
+
+Keep reading: [Conversation lifecycle in Inbox]({% link _team/conversation-lifecycle.md %}) and [Assign conversations]({% link _team/assigning-conversations.md %}).
+
+## Subscription status and unsubscribe requests
+
+A customer's email address is a destination, not evidence that the customer wants marketing messages. Review the profile's subscription information and the purpose of the contact before sending.
+
+An ordinary email sent manually from the Inbox does not automatically include an unsubscribe link in its footer. If the customer asks your team to stop marketing messages, record the request using the customer's subscription controls and follow the business's consent process.
+
+For an email that includes an **Unsubscribe** link, the customer opens a confirmation page and presses **Unsubscribe** to submit the request. The page then displays **Request received** while Hellotext processes the preference update. Opening the link alone does not submit the unsubscribe request.
+
+
+ An email unsubscribe updates the customer's subscription status for that Hellotext business across channels. It is not limited to one email address or only the Email channel.
+
+
+Unsubscribing does not delete the customer profile or its conversation history. Do not switch to another channel to bypass the recorded preference.
+
+If Hellotext receives a spam or abuse complaint for a sent email, it records the customer's unsubscribe while preserving the message's existing delivery state. A bounced or rejected email is handled as a delivery failure; it is not the same as an unsubscribe request.
+
+Keep reading: [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Understand sending, delivery, and read information
+
+The conversation can show several kinds of message information as updates arrive:
+
+| Information | What it tells you |
+| --- | --- |
+| **Sending** | Hellotext is processing the outbound message. |
+| **Sent** | The message has been handed off for sending. This alone does not confirm delivery to the recipient. |
+| **Delivered** | The recipient's mail service has accepted the message. It does not guarantee placement in the primary inbox. |
+| **Seen or read information** | An email-open notification was reported. It does not prove the customer read or understood the message. |
+| **Failed** | Sending could not be completed, or a rejection or bounce was reported. |
+| **Received** | A supported customer reply was recorded in the conversation. |
+
+Delivery and open information can arrive separately. An absent read timestamp does not prove that the customer has not opened the email. Treat the customer's reply or another explicit action as stronger evidence of engagement.
+
+Inspect the message's information and any available failure reason before sending it again. Some failures provide only a general error, so do not expect a detailed mailbox diagnosis for every unsuccessful email.
+
+Keep reading: [Why a message did not send]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %}).
+
+## Troubleshoot an Email conversation
+
+### Email is missing from the destination menu
+
+Check that the customer's profile has an email address and that the business has a verified, active sender. If the sender was recently added or its domain was changed, follow its DNS instructions and allow verification to complete.
+
+If the only destination on the profile is Email and no Email sender is active, the conversation cannot offer a usable Email composer. Review the sender setup rather than repeatedly adding the same customer address.
+
+### The message used an unexpected sender or subject
+
+The destination menu chooses the recipient. The sender comes from the Email channel; you write the subject in **Subject**. Check that field before sending, including when replying to an earlier email.
+
+Review the sender's name and address in **Settings > Integrations**. If you have several senders, check which channel the conversation used. Contact support if you need help identifying the sender before sending further messages.
+
+### The customer cannot find a sent email
+
+Confirm the exact recipient address and review whether the message has delivery information or a failure. Ask the customer to check their spam or junk folder as well as their usual inbox.
+
+If the email is still sending, give processing time to complete. If it failed, review the available reason, correct the destination or content when appropriate, and reduce images or simplify the design if its size prevents sending.
+
+### The customer's reply does not appear
+
+Confirm that the customer replied to an email sent from Hellotext, used the supplied reply address, and replied from the original recipient address. Check that the sending channel is still active and that the customer or conversation has not been blocked or removed.
+
+Incoming replies must also pass the receiving checks. If a reply still does not appear, contact support with the original message, recipient address, approximate reply time, and whether the reply included attachments. There is no need to recreate the sender just to investigate a missing reply.
+
+### An attachment fails or looks different
+
+In the Email editor, add images through its image blocks. Check that they are PNG, JPEG, GIF, or WebP files up to 5 MB and wait for the upload to finish. A design image appears within the email; its appearance can vary between email applications.
+
+For a large document or media file, consider sharing an appropriate download link. Keep access to the linked file suitable for the intended customer.
+
+## First Email conversation checklist
+
+Before your team relies on Email conversations in the Inbox, confirm that:
+
+1. The intended sender is verified and active in the correct business.
+2. A test customer's email address is saved correctly on the profile.
+3. The selected destination is Email and shows the correct address.
+4. The received test message shows the expected sender, subject, design, images, and links.
+5. A reply from the same recipient address appears in the correct Inbox conversation.
+6. The right teammate or team takes responsibility for the reply.
+7. Your team understands sender selection, delivery information, and the scope of unsubscribe requests.
+
+## Related guides
+
+- [Set up email sending]({% link _integrations/set-up-email-sending.md %})
+- [Messaging channels overview]({% link _numbers/messaging-overview.md %})
+- [Inbox and conversations overview]({% link _team/inbox-overview.md %})
+- [Message editor overview]({% link _numbers/message-editor-overview.md %})
+- [Customer profiles]({% link _audience/customer-profiles.md %})
+- [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %})
+- [Tracked links]({% link _analytics-reporting-attribution/tracked-links.md %})
+- [Why a message did not send]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %})
diff --git a/docs/editorial-work/captures/email-completion-20261011/pre-integration/es.md b/docs/editorial-work/captures/email-completion-20261011/pre-integration/es.md
new file mode 100644
index 00000000..e00c22f4
--- /dev/null
+++ b/docs/editorial-work/captures/email-completion-20261011/pre-integration/es.md
@@ -0,0 +1,244 @@
+Usa Correo electrónico cuando tus clientes necesiten un mensaje que puedan recibir y responder desde su aplicación de correo habitual. Tu equipo envía desde una dirección del dominio de tu negocio y gestiona las respuestas compatibles en el Inbox de Hellotext, junto a las demás conversaciones del cliente.
+
+Esta guía explica el uso diario del canal de correo electrónico después de agregar un remitente. Para conocer el formulario del remitente, los registros DNS y la verificación del dominio, sigue [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %}).
+
+
+ Correo electrónico está disponible en Pro y Enterprise. El dominio de un remitente guardado debe terminar de verificarse antes de que su canal esté disponible para enviar.
+
+
+## Para qué sirve mejor el correo electrónico
+
+Usa Correo electrónico para:
+
+- Conversaciones individuales con clientes desde el Inbox.
+- Respuestas detalladas que necesitan párrafos y un registro escrito.
+- Soporte y seguimiento de pedidos con clientes que prefieren el correo.
+- Compartir imágenes e información, con links a documentos cuando haga falta.
+- Continuar una conversación después de que el cliente responda a un correo enviado desde Hellotext.
+
+El correo electrónico no requiere que el cliente instale una aplicación de mensajería ni que tenga un número de teléfono en su perfil. Sí necesitas la dirección correcta y permiso para contactar al cliente con el propósito del mensaje.
+
+## Antes de enviar desde el Inbox
+
+Antes de enviar un correo individual desde el Inbox, confirma que:
+
+- Estás trabajando en el negocio correcto de Hellotext.
+- El negocio tiene Correo electrónico habilitado y al menos un remitente de correo verificado y activo.
+- El perfil del cliente contiene la dirección de correo que quieres usar.
+- Tienes acceso a la conversación de ese cliente en el Inbox.
+- El cliente y la conversación están disponibles para el contacto que quieres realizar.
+- Alguien de tu equipo es responsable de gestionar las respuestas.
+
+La integración del remitente y la dirección de correo del cliente cumplen funciones distintas. Agregar un remitente no agrega direcciones de correo a los perfiles de clientes. Agregar la dirección de un cliente no verifica tu dominio de envío ni establece el consentimiento de ese cliente.
+
+Sigue leyendo: [Cómo funcionan los perfiles de clientes]({% link _audience/customer-profiles.md %}) y [A quién puedo escribirle: consentimiento y estado de suscripción]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Dónde puedes usar correo electrónico
+
+El menú de destino del Inbox puede mostrar **Email** antes de que el envío esté listo. Para enviar necesitas una dirección en el perfil del cliente, acceso al canal y un remitente activo; ver la opción no confirma esos requisitos.
+
+El creador de campañas muestra Correo electrónico como opción de entrega, pero seleccionarla por sí sola no habilita el envío. Para enviar una campaña por correo, el negocio necesita acceso al canal según su suscripción y un remitente verificado y activo. Conectar un remitente no cambia automáticamente los canales de una campaña existente.
+
+Las rutas pueden enviar correos desde pasos de Mensaje o Pregunta configurados con un diseño de correo, y las misiones proactivas compatibles pueden seleccionar este canal. Cada envío depende de las reglas del flujo, de un destinatario apto y del acceso y remitente del negocio. Usa el Inbox para conversaciones individuales por correo y para gestionar las respuestas compatibles.
+
+## Entiende el remitente, el destinatario y la dirección de respuesta
+
+Una conversación por correo utiliza tres direcciones o identidades:
+
+| Dato | Qué significa | De dónde proviene |
+| --- | --- | --- |
+| **Remitente** | El nombre y la dirección de correo del negocio que aparecen como remitente del mensaje. | El remitente de correo asociado al canal de correo electrónico activo. |
+| **Destinatario** | La dirección del cliente que recibirá este mensaje. | La dirección de correo que eliges del perfil del cliente en el menú de destino. |
+| **Dirección de respuesta** | La dirección que utiliza la aplicación de correo del cliente cuando elige Responder. | Hellotext la proporciona automáticamente para asociar la respuesta con la conversación. |
+
+Por ejemplo, tu remitente puede ser `support@example.com` y tu cliente puede recibir el mensaje en `alex@example.com`. La dirección de respuesta puede ser distinta de `support@example.com`; así recibe Hellotext la respuesta para la conversación.
+
+El menú de destino muestra las direcciones de correo del cliente. No es una lista de los remitentes de tu negocio. Cuando eliges una dirección, Hellotext usa el remitente activo de la conversación de correo existente, si está disponible, o un canal de correo electrónico disponible para un destino nuevo.
+
+Si tu negocio tiene varios remitentes activos, verifica cuál se utiliza antes de depender de una dirección de origen específica. El menú de destino del Inbox no ofrece actualmente un selector separado de remitentes de correo.
+
+Para cambiar el nombre o la dirección de un remitente, usa su acción **Editar** en **Ajustes > Integraciones**. Cambiar su dominio requiere una nueva verificación. Consulta [Configura el envío de correos]({% link _integrations/set-up-email-sending.md %}) antes de realizar ese cambio.
+
+## Envía un correo desde el Inbox
+
+1. Abre la conversación del cliente en el **Inbox**.
+2. Revisa el perfil del cliente y confirma que la dirección de correo sea correcta. Agrega o corrige la dirección en el perfil si es necesario.
+3. Abre el menú de destino junto al editor de mensajes.
+4. Busca la opción **Email**.
+5. Selecciona la dirección del cliente a la que quieres enviar. Si el perfil tiene más de una, elige la que debe recibir este mensaje.
+6. Escribe el **Asunto** y prepara el cuerpo en el editor de correo. Organiza el contenido en bloques de texto y agrega imágenes o acciones cuando ayuden al cliente.
+7. Abre **Vista previa** para revisar el diseño en escritorio y móvil. Comprueba el destinatario, el asunto, el texto y los links antes de enviar, especialmente si antes estabas respondiendo por otro canal.
+8. Envía el mensaje y revisa su información de envío o entrega en la conversación.
+
+Al enviar, se usa únicamente la dirección seleccionada. No se envían copias a todas las direcciones del perfil. El menú de destino de correo electrónico no ofrece campos CC ni CCO.
+
+Si Correo electrónico es el único destino disponible del cliente, Hellotext puede abrir el editor con ese canal seleccionado cuando hay un remitente activo. Revisa siempre el destino si el cliente también tiene números de teléfono u otros canales conectados.
+
+Si no puedes enviar por Email, revisa la dirección del perfil, el acceso de tu plan y la activación del remitente. Un dominio pendiente de verificación no ofrece un canal de envío activo, aunque el menú permita explorar la opción Email.
+
+Sigue leyendo: [Resumen del editor de mensajes]({% link _numbers/message-editor-overview.md %}).
+
+## Qué recibe el cliente
+
+Hellotext prepara el correo a partir del diseño que editaste. La apariencia elegida aporta la marca y el pie del mensaje; el nombre y la dirección del remitente provienen del canal de correo. También se incluye una versión de texto sin formato para las aplicaciones de correo que la utilizan.
+
+Usa **Asunto** para escribir el título del correo. Es independiente del cuerpo y del nombre del remitente; este último no cambia automáticamente al nombre de la persona del equipo que hizo clic en enviar.
+
+El cuerpo conserva los bloques del diseño, como texto, imágenes y botones. Las imágenes que agregas al diseño aparecen dentro del correo; no se ofrecen automáticamente como archivos adjuntos descargables. No dependas de que los estilos copiados o los controles de otro canal se vean exactamente igual.
+
+Usa **Vista previa** para revisar el borrador sin enviarlo y alterna entre escritorio y móvil. Distintas aplicaciones de correo pueden mostrar el mismo diseño de manera diferente; una prueba recibida te permite comprobar la apariencia final, los saltos de línea y los links.
+
+El pie de la vista previa puede mostrar **Cancelar suscripción**. En un correo manual del Inbox ese enlace no se agrega automáticamente al envío.
+
+### Links y personalización
+
+Usa la herramienta de links del editor cuando necesites un link con seguimiento y comprueba su destino antes de enviar. Usa etiquetas de personalización solo cuando el perfil del cliente tenga los valores necesarios para producir un mensaje completo.
+
+Revisa el texto final con datos realistas de clientes. Un nombre faltante, una dirección desactualizada o un link que lleva al producto equivocado pueden hacer que un correo entregado correctamente no resulte útil.
+
+Sigue leyendo: [Links con tracking]({% link _analytics-reporting-attribution/tracked-links.md %}) y [Etiquetas de personalización]({% link _audience/personalization-tags.md %}).
+
+## Longitud del texto y archivos adjuntos
+
+El editor de correo organiza el contenido en bloques. Usa sus controles de imagen; la lista de archivos de otros canales no describe lo que puedes agregar a este diseño.
+
+| Elemento | Límite o comportamiento |
+| --- | --- |
+| **Asunto** | Hasta 998 caracteres. |
+| **Texto con formato** | Se valida por bloque; el formato también ocupa espacio. Simplifica o divide un bloque si el editor rechaza su longitud. |
+| **Bloques principales** | Hasta 30 en el diseño. |
+| **Una imagen cargada** | PNG, JPEG, GIF o WebP de hasta 5 MB. Se incorpora al cuerpo del correo. |
+| **Documentos, audio o video** | Comparte un link adecuado; el editor de correo actual no ofrece la carga general de estos archivos como adjuntos. |
+
+El límite del texto con formato no equivale a un número fijo de caracteres para todo el correo. También se valida el tamaño conjunto del diseño. Mantén el mensaje breve y divide la información en bloques útiles, sin repetir contenido.
+
+Espera a que termine la carga de cada imagen y revisa su contenido en **Vista previa**. Que una imagen se acepte no garantiza que todos los servicios de correo acepten el mensaje completo. Usa imágenes más pequeñas cuando sea posible.
+
+Para compartir un documento o un archivo grande, agrega un link de descarga y comprueba que el cliente tenga acceso. Cambiar solo la extensión de un archivo no lo convierte a un formato compatible.
+
+## Cómo llegan las respuestas del cliente al Inbox
+
+Después de recibir un correo enviado desde Hellotext, el cliente debe:
+
+1. Abrir el mensaje en su aplicación de correo habitual.
+2. Elegir **Responder**.
+3. Mantener la dirección de respuesta que proporciona la aplicación de correo.
+4. Responder desde la misma dirección que recibió el mensaje.
+
+Hellotext asocia una respuesta compatible con el correo saliente original, el perfil del cliente y la conversación. Tu equipo puede leerla y responder desde el Inbox.
+
+Una respuesta puede incluir texto y adjuntos compatibles. El Inbox conserva elementos compatibles del correo recibido, como imágenes, tablas y listas, y puede agrupar el texto citado de mensajes anteriores. Algunos estilos o elementos del correo original pueden mostrarse de otra forma.
+
+### Respuestas desde otra dirección
+
+Para asociar una respuesta se espera la dirección del destinatario original. Si el cliente responde desde otra cuenta, o reenvía el correo a otra persona que luego responde, es posible que no se cree un mensaje asociado en el Inbox.
+
+Cuando pruebes las respuestas, usa la misma dirección que recibió el correo y no cambies la dirección de respuesta proporcionada. El asunto del correo por sí solo no alcanza para asociar cualquier mensaje con la conversación.
+
+### Correos nuevos enviados a la casilla existente de tu negocio
+
+Verificar un dominio de envío no traslada una casilla existente a Hellotext. Un correo nuevo escrito directamente a `support@example.com` sigue la configuración de recepción que ya tenga esa dirección.
+
+Enviar desde esa dirección en Hellotext y recibir respuestas mediante la dirección de respuesta proporcionada son funciones distintas de importar el historial de una casilla o recibir todos los correos nuevos enviados al dominio. Si necesitas una configuración más amplia de recepción, consúltala con el [soporte de Hellotext]({% link _troubleshooting-deliverability/contact-hellotext-support.md %}).
+
+## Responsables de la conversación y ventanas de respuesta
+
+Las conversaciones de correo usan el flujo de trabajo compartido del Inbox. El equipo puede asignar el trabajo, agregar notas internas, cerrar una conversación y gestionar las respuestas posteriores con el historial del cliente disponible.
+
+El correo electrónico no tiene una ventana de respuesta de 24 horas. El canal no deja de estar disponible simplemente porque el cliente no haya escrito recientemente. El remitente debe seguir activo, y el cliente, la conversación, la suscripción y las demás condiciones de envío deben permitir el mensaje que quieres enviar.
+
+Cerrar o posponer una conversación del Inbox es una acción del flujo de trabajo del equipo. Es independiente de la capacidad de envío del canal de correo electrónico. Una nueva respuesta compatible del cliente puede devolver la conversación a la atención del equipo.
+
+Sigue leyendo: [Ciclo de una conversación en el Inbox]({% link _team/conversation-lifecycle.md %}) y [Asigna conversaciones]({% link _team/assigning-conversations.md %}).
+
+## Estado de suscripción y solicitudes de baja
+
+La dirección de correo de un cliente es un destino, no una prueba de que quiera recibir mensajes de marketing. Revisa la información de suscripción del perfil y el propósito del contacto antes de enviar.
+
+Un correo habitual enviado manualmente desde el Inbox no incluye automáticamente un link para cancelar la suscripción en su pie. Si el cliente pide al equipo dejar de recibir mensajes de marketing, registra la solicitud con los controles de suscripción del cliente y sigue el proceso de consentimiento del negocio.
+
+En un correo que incluye un link **Cancelar suscripción**, el cliente abre una página de confirmación y presiona **Cancelar suscripción** para enviar la solicitud. Luego, la página muestra **Solicitud recibida** mientras Hellotext procesa la actualización de preferencias. Abrir el link por sí solo no envía la solicitud de baja.
+
+
+ Una baja por correo actualiza el estado de suscripción del cliente para ese negocio de Hellotext en todos los canales. No se limita a una dirección de correo ni solamente al canal de correo electrónico.
+