View Standard Fix
USE CASE Target

Outlook Email Broken Layout Fix: Resolve Custom Font Fallback Overrides for Transactional & System Notifications

Transactional emails (receipts, password resets, shipping alerts) carry critical operational data. Spacing collapses or broken buttons can block users from completing essential user journeys. Below is the targeted integration guide to fix Custom Font Fallback Overrides inside Outlook 2013 templates when using Salesforce Marketing Cloud (SFMC).

Technical Breakdown

Outlook 2013 uses the Microsoft Word (MSO) which lacks support for standard rendering rules. This causes Custom Font Fallback Overrides elements to break or collapse when rendering templates.

Salesforce Marketing Cloud (SFMC) Behaviors

SFMC's Content Builder wraps block exports in div frames that can break conditional comments. Additionally, AMPScript calls for personalizations can trigger parsing errors if they are inside MSO conditional comments. Ensure your AMPScript tags are evaluated *outside* the VML blocks. Because system notifications are triggered frequently, ensure your CSS rules are completely inlined to guarantee readability in high-volume, automated delivery queues.

Remediation Code Block

To prevent Outlook's Times New Roman fallback override, wrap your custom font declarations inside an @media block that Outlook ignores, or use MSO conditional statements to override font-families specifically for Microsoft Word rendering engines. In your Salesforce Marketing Cloud (SFMC) campaign manager, make sure you configure your links to run via %%unsubscribe_url%%.

<!--[if mso]>
<style type="text/css">
  body, table, td { font-family: Arial, sans-serif !important; }
</style>
<![endif]-->
<style>
  @import url('https://fonts.googleapis.com/css2?family=Montserrat&display=swap');
</style>

Live Code Sandbox Test

Interactive Salesforce Marketing Cloud (SFMC) Custom Sandbox

Target Environment: Outlook 2013

How to Deploy inside Salesforce Marketing Cloud (SFMC)

1

Copy the fixed VML or table wrapper code block from the remediation box above.

2

Create an 'HTML content' layout block in Content Builder. Paste the table structure. Enclose any custom merge tags inside standard AMPscript wrapper lines.

Targeted Fixes by Use Case & Industry