113 lines
4.0 KiB
HTML
113 lines
4.0 KiB
HTML
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8" />
|
||
<meta name="viewport" content="width=device-width,initial-scale=1" />
|
||
<title>Delivery Help & Error Messages</title>
|
||
<link rel="stylesheet" href="assets/styles.css" />
|
||
</head>
|
||
<body>
|
||
<div class="container">
|
||
|
||
<div class="topbar">
|
||
<div class="brand">
|
||
<div class="brand-mark" aria-hidden="true"></div>
|
||
<div class="brand-title">
|
||
<strong>Delivery Help</strong>
|
||
<span>Plain-English explanations when email doesn’t arrive</span>
|
||
</div>
|
||
</div>
|
||
|
||
<nav class="nav" aria-label="Primary">
|
||
<a class="pill" href="index.html">Overview</a>
|
||
<a class="pill" href="secure-mail-delivery.html">Secure Delivery</a>
|
||
<a class="pill" href="routing-reliability.html">Reliability</a>
|
||
<a class="pill" href="spam-junk-reduction.html">Cleaner Inboxes</a>
|
||
</nav>
|
||
</div>
|
||
|
||
<section class="hero">
|
||
<div class="hero-inner">
|
||
<div>
|
||
<div class="kicker"><span class="kdot"></span> Support improvement</div>
|
||
<h1>Clear answers when email doesn’t arrive.</h1>
|
||
<p class="lead">
|
||
Delivery issues shouldn’t be a mystery. When something fails or is delayed, you should know what happened and what to do next—without translating cryptic codes.
|
||
</p>
|
||
|
||
<div class="cta-row">
|
||
<!-- Replace this with your public tool/URL if desired -->
|
||
<a class="btn primary" href="#next-steps">Quick next steps</a>
|
||
<a class="btn secondary" href="#what-to-send">What to include when contacting support</a>
|
||
</div>
|
||
<div class="small-note">Less confusion. Faster resolution.</div>
|
||
</div>
|
||
|
||
<aside class="hero-side">
|
||
<h3>Common outcomes</h3>
|
||
<ul>
|
||
<li>Sometimes: “Retry later” (temporary)</li>
|
||
<li>Sometimes: “Fix something first” (permanent)</li>
|
||
<li>Always: clear next steps</li>
|
||
</ul>
|
||
</aside>
|
||
</div>
|
||
</section>
|
||
|
||
<div class="section-title" id="next-steps">Quick next steps</div>
|
||
<section class="grid">
|
||
<article class="card">
|
||
<h2>If the message is delayed</h2>
|
||
<p>Many delays resolve automatically. If it’s temporary, the sending system will retry on its own.</p>
|
||
<ul>
|
||
<li>Wait a short time and check again</li>
|
||
<li>Escalate if it persists</li>
|
||
</ul>
|
||
</article>
|
||
|
||
<article class="card">
|
||
<h2>If the message is rejected</h2>
|
||
<p>Some failures require a correction (often on the sender side). The key is knowing exactly what needs to change.</p>
|
||
<ul>
|
||
<li>Confirm the recipient address</li>
|
||
<li>Ask the sender to share the bounce details</li>
|
||
</ul>
|
||
</article>
|
||
</section>
|
||
|
||
<div class="section-title" id="what-to-send">What to include when contacting support</div>
|
||
<section class="card">
|
||
<p>
|
||
For the fastest help, include:
|
||
</p>
|
||
<ul>
|
||
<li>Recipient email address</li>
|
||
<li>Sender email address or domain</li>
|
||
<li>Date/time (and timezone) of the attempt</li>
|
||
<li>The bounce/error message or screenshot (if available)</li>
|
||
</ul>
|
||
<p style="margin-top:12px;color:rgba(238,242,255,.58);">
|
||
If you maintain a public “error reference” page (like your SMTP error guide), link it here as a self-service option.
|
||
</p>
|
||
</section>
|
||
<div class="section-title">FAQ</div>
|
||
<section class="grid">
|
||
<article class="card">
|
||
<h2>Do users need to change anything?</h2>
|
||
<p>No. This runs in the background and does not change daily workflow.</p>
|
||
</article>
|
||
<article class="card">
|
||
<h2>Will this disrupt delivery?</h2>
|
||
<p>No downtime was required, and the goal is improved consistency—not disruption.</p>
|
||
</article>
|
||
</section>
|
||
|
||
<footer class="footer">
|
||
<span><span class="tag"><b>Goal</b> No guessing—clear guidance.</span></span>
|
||
<span><a href="index.html">Back to overview</a></span>
|
||
</footer>
|
||
|
||
</div>
|
||
</body>
|
||
</html>
|