wiki/knowledge/email-marketing/quarra-email-signature-technical-fix.md · 618 words · 2026-04-05

Quarra Stone Email Signature Technical Fix

Overview

Quarra Stone's current email signatures are grainy, pixelated, and — when image-based — frequently appear as file attachments in email threads rather than rendering inline. The goal is to replace these with high-resolution, scalable signatures that include a clickable website URL (and ideally click-to-call phone numbers) without the attachment problem.

This issue was raised by Lauren Pomaranski and Lincoln Durham in the ^[1] October 2025 marketing sync. Karly Oykhman (Asymmetric) is consulting Mark internally on the best technical approach before providing a template and implementation instructions to Lauren.

Problem Statement

Issue	Detail
Image quality	Current signature image is grainy and pixelated at various screen sizes
Attachment behavior	Image-based signatures often render as file attachments in reply threads
Interactivity	Website URL is not reliably clickable; phone numbers are not click-to-call
Scalability	Signature does not scale cleanly across mobile and desktop clients

"The thing that I don't want to have happen is that the image becomes an attachment in like response to emails… And then the other thing is just that it like scales. I don't want it to be grainy, whether you're looking at it on your phone or on your computer."
— Lincoln Durham

Requirements

Must-Have

Clickable website URL — minimum requirement; the Quarra Stone website link must be hyperlinked
No attachment behavior — the signature must not appear as a file attachment in reply chains
High resolution / scalable — must render cleanly on both mobile and desktop email clients

Nice-to-Have

Click-to-call phone numbers — if achievable without significant added complexity
Consistent layout — retain the existing visual layout (logo, name, title, contact info) that Lauren currently uses

Preferred Approach

The preferred solution is an HTML-based signature rather than a flat image embed. This avoids the attachment problem and allows native hyperlinking. If an image element is required (e.g., for the logo), it should be:

Hosted externally (linked via URL, not embedded as a base64 or attached file)
Exported at sufficient resolution to be crisp at 1x and 2x display densities

A pure-text/HTML layout with a linked logo image is the most robust cross-client solution.

Implementation Plan

Karly consults Mark (Asymmetric technical lead) on the correct HTML signature approach for the email clients Quarra Stone uses
Asymmetric produces a template — one canonical signature template with placeholder fields (name, title, phone)
Template + instructions delivered to Lauren — Lauren manages company-wide rollout
Rollout method — Lauren emails instructions to all staff; follows up in person with anyone who has trouble

Action Items

[ ] Karly consults Mark on technical solution for HTML email signatures (@Karly Oykhman)
[ ] Karly provides signature template and setup instructions to Lauren (@Karly Oykhman)
[ ] Lauren manages company-wide implementation and troubleshooting (@Lauren Pomaranski)

Generalizable Insight

For clients with image-based email signatures: The common failure mode is embedding a rasterized image directly in the signature, which degrades at non-native resolutions and triggers attachment behavior in many email clients. The more durable pattern is an HTML signature with a remotely-hosted logo image and native HTML hyperlinks — this scales cleanly, links work reliably, and nothing appears as an attachment. Rollout is best handled by providing a single canonical template with a written setup guide, then having an internal champion (like an office manager or EA) do a one-time walkthrough with staff.

^[2]
^[3]
^[4]