# Release Notes: 2026 Sprint 6 W2 **Period: April 9, 2026 – April 14, 2026** This week, the MyAlice engineering team focused on quality and reliability — shipping 5 bug fixes across Inbox, Broadcast, and Integrations to sharpen up core workflows. *** ### 🚀 Features and Innovations No new features this week — the team was heads-down on bug fixes and stability improvements. *** ### 🐛 Bug Fixes **Inbox** * Fixed an issue where emails sent from external platforms displayed inconsistent formatting when received in MyAlice. Email content now renders consistently regardless of the sending platform. * Fixed an issue where new email ticket notifications showed raw HTML tags and encoded characters in the message preview. Notifications now display clean, readable plain text as expected. * Fixed an issue where CC and BCC recipient addresses were not appearing when viewing an email conversation in Inbox. All recipients are now correctly displayed. **Integrations** * Fixed an issue where newly connected WhatsApp Business Accounts (WABAs) were having MM Lite automatically enabled without completing the required onboarding flow. The mandatory MM Lite setup process is now correctly enforced for all new connections. **Broadcast** * Fixed multiple data discrepancies in Broadcast export files, including incorrect timestamps, inaccurate cost calculations, and misreported revenue figures. Exported data now accurately reflects actual broadcast performance. *** *These updates are live for all MyAlice users. As always, if you have any questions or run into anything unexpected, reach out to our support team — we're here to help.* --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.myalice.ai/release-log/release-notes-2026-sprint-6-w2.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.