Most signature tools demo beautifully and fall apart in month three. The difference is rarely the editor — it is how the tool gets a signature onto a phone, what happens when someone changes department, and who has to touch it when a banner campaign ends. Here is how to evaluate that properly.

Start with your deployment model, not the editor

There are only three ways a signature reaches an email, and the one a vendor uses decides most of what you will live with.

The eleven questions that separate products

• Directory sync: does it read job title, department, phone and photo from Entra ID or Google Directory automatically, and how often does it re-sync?
• Empty-field handling: when a user has no mobile number, does the row collapse cleanly or leave a dangling label and pipe character?
• Reply signatures: can you use a shorter block on replies so threads do not turn into a wall of logos?
• Group targeting: can rules target a security group, an OU, a domain, or only individual users?
• Campaign scheduling: can a banner start and expire on a date without anyone logging in?
• Click analytics: per banner, per department, exportable — or a vanity number on a dashboard?
• Disclaimer logic: can a legal block apply only to external recipients?
• Delegate and shared mailboxes: whose signature appears when an assistant sends on behalf of a director?
• Rendering guarantee: which clients do they actually test on, and will they show you the test matrix?
• Data path: for server-side products, does mail route through the vendor, and in which region does it land?
• Exit: can you export your templates as HTML and leave without a rebuild?

What changes at each size

Under 50 mailboxes

You mostly need consistency and a fast rollout. Directory sync matters less because you can fill twenty rows by hand. Avoid anything that requires a mail-flow change — the admin overhead is not worth it at this size.

50 to 250 mailboxes

This is where manual updates die. Joiners and leavers arrive weekly, marketing wants banners, and someone in sales has invented their own layout. Directory sync and group targeting become the two features you are really buying.

250 and above

Now governance dominates: approval workflows, role-based admin, audit logs, regional disclaimer variants, and a support agreement with a response time in it. Also confirm the vendor can handle multiple domains and brands under one tenant — most acquisitions arrive with a second brand attached.

Cost modelling that survives renewal

Per-user pricing looks simple until you count shared mailboxes, contractors and dormant accounts. Ask three questions: are shared and resource mailboxes billable, is billing by licensed user or by user actually receiving a signature, and what does the price do at renewal after your headcount grows 30%. Then compare the annual figure against the real alternative — an IT person spending two hours a week on signature tickets is roughly 100 hours a year.

The short version

Pick the deployment model first, prove mobile in the demo, and buy for the size you will be in eighteen months. Editors are easy to build and easy to switch. Directory logic, mobile coverage and campaign scheduling are the parts that quietly decide whether the tool is still working next year.

Every company hits the same wall: forty people, forty signatures, four versions of the logo and one that still lists an office you closed. Centralizing is not technically hard. Doing it without a week of complaints is the actual skill.

Week 1 — Audit before you design

Collect a real sample rather than guessing. Ask ten people across departments to forward you a recent sent email, and note what varies: title wording, phone formats, whether people include mobile numbers, which social profiles appear, and what legal text sales has invented on its own.

You are looking for three things — fields that must be personal, fields that must be identical for everyone, and fields that should not be there at all.

Week 2 — Design one template with variants, not ten templates

The maintainable pattern is a single layout with conditional rows:

• Core block: name, title, department, company, primary phone, website. Identical structure for everyone.
• Conditional rows: mobile number, direct line, certification line, pronouns — rendered only when the directory field exists.
• Department variants: a booking link for sales, a support portal link for service, a licence number for regulated roles.
• Legal block: external recipients only, one version per jurisdiction if you operate in several.

Ten separate templates means ten places to update when the logo changes. One template with rules means one.

Week 3 — Fix the directory, then pilot

Signatures are a read-only mirror of your directory, so bad data becomes visible instantly. Before piloting, normalize phone numbers to international format, standardize titles, confirm department values, and decide who owns those fields going forward — usually HR, not IT.

1. Pick a pilot group of 10 to 15 across at least three departments, including one person who sends mostly from a phone and one who uses a shared mailbox.
2. Run for five working days and collect feedback in one channel, not in individual DMs.
3. Test the awkward cases: replies inside long threads, a delegate sending on behalf of an executive, an external send with the disclaimer, and a mail sent from a mobile device.
4. Freeze the template after pilot feedback. Late tweaks during rollout are how projects slip.

Week 4 — Roll out with a message people accept

Resistance is almost never about design; it is about losing control unexpectedly. Announce two days ahead, show a before-and-after image, and say plainly what happens next: signatures are now applied automatically, personal edits will be overwritten, and requests for changes go to one address.

Then remove the old instructions. If the wiki page explaining how to paste a signature manually still exists, someone will follow it.

What to keep doing afterwards

Centralizing is a one-month project and a ten-minute-a-week habit. The habit is the part that keeps it from drifting back.

Email signatures break for a boring reason: people build them like web pages. Outlook renders HTML with the Microsoft Word engine, Gmail strips your styles, and Apple Mail scales everything on a phone. Build for those three and you are covered almost everywhere.

The five rules

• Tables, not flexbox. Layout must be nested tables with explicit widths. Flexbox and grid are ignored by Word-based rendering.
• Inline styles only. Style blocks in the head are frequently stripped. Every rule goes in a style attribute on the element.
• Web-safe fonts with a stack. Arial, Helvetica, Georgia, Tahoma, Verdana. Custom fonts silently fall back, so choose a fallback you can live with.
• Absolute pixel widths. Percentages behave unpredictably in Outlook. Set width in pixels on tables and images, and cap the whole signature near 600px.
• No background images, no external CSS, no JavaScript. They will be blocked, stripped, or flagged.

Markup that survives

This is the structural pattern — two columns, a photo cell and a details cell, with the divider drawn as a bordered cell rather than a styled div.

Client quirks worth memorizing

The testing routine

1. Send to yourself first from the client the signature was built in, then reply to that mail — replies expose spacing bugs that new messages hide.
2. Check the big three: Outlook for Windows, Gmail on web, Apple Mail on an iPhone. That covers the overwhelming majority of business recipients.
3. Toggle dark mode on the phone and look at the logo, the divider, and any grey text.
4. Turn images off and read what remains — if the signature becomes unreadable, too much information lives inside images.
5. Forward it once. Forwarding is the harshest test; layouts that survive a forward survive most things.

Size and deliverability

Keep the rendered signature under roughly 50KB. Heavy signatures cause Gmail to clip the message body behind a link, and repeated large images across a long thread add up. Host images on a CDN over HTTPS rather than embedding them, and never attach the logo — attachments trigger the paperclip icon on every mail you send and read as spam-adjacent to some filters.

Finally, always set alt text on every image. When images are blocked by default — still common in corporate environments — alt text is the only thing your recipient sees.

There are now three Outlooks in common use and each hides signature settings somewhere different. Find your version first, then follow the matching steps.

New Outlook for Windows and Mac

1. Open Settings using the gear icon at the top right of the window.
2. Go to Accounts, then Signatures.
3. Select New signature and give it a name you will recognize, such as Main or Reply.
4. Paste or build your signature in the editor. If you are pasting prepared HTML, paste it into the compose window first, then copy from there — pasting straight into the box sometimes strips formatting.
5. Set the defaults below the editor: which signature applies to new messages and which applies to replies and forwards.
6. Save, then send a test mail to yourself.

Classic Outlook for Windows

1. Open a new email, then on the Message tab choose Signature, then Signatures.
2. Click New, name the signature, and click OK.
3. Compose your signature in the Edit signature box. Use the picture button to insert a logo rather than dragging it in.
4. Choose your defaults on the right: the email account it belongs to, plus the new-message and reply selections.
5. Click OK to save and close.

Classic Outlook keeps signature files at %appdata%\Microsoft\Signatures. Copying that folder to a new PC moves signatures across, which is handy for a single machine and unmanageable across a company.

Outlook on the web

1. Click the gear icon at the top right.
2. Choose Mail, then Compose and reply.
3. Build your signature in the editor and name it.
4. Tick the two boxes to apply it automatically to new messages and to replies and forwards.
5. Save.

Common problems

Gmail keeps signatures per address rather than per device, so a desktop signature does not reach the Gmail mobile app. Set both, and know the two limits that trip people up.

Gmail on desktop

1. Open Settings from the gear icon, then click See all settings.
2. Stay on the General tab and scroll down to Signature.
3. Click Create new, name it, and confirm.
4. Build or paste your signature. To paste prepared HTML, open it in a browser, select the rendered signature on the page, copy, and paste into the box — copying rendered output preserves formatting far better than pasting code.
5. Set the defaults beneath the editor for new emails and for replies and forwards.
6. Scroll to the bottom and click Save Changes. This is the step people miss — the editor gives no other confirmation.

Gmail on Android and iOS

1. Open the Gmail app and tap the menu icon, then Settings.
2. Select the account you want to change.
3. Tap Signature settings on Android, or Signature settings under Compose on iOS.
4. Enable the mobile signature and enter your text.

The mobile signature is plain text only. Keep it to name, title, company and one phone number — do not attempt a copy of the desktop version.

Adding a clickable image or banner

Use the image button in the signature editor and choose Web address (URL) rather than uploading, so the image is served from a stable link. Then select the inserted image and use the link button to attach a destination URL. Add UTM parameters to that URL if you want the traffic to be identifiable in analytics.

Troubleshooting

• Signature is not applied: check the defaults dropdown — a signature can exist without being assigned to new mail.
• Formatting collapsed after saving: Gmail sanitizes pasted markup. Rebuild using simple nested tables with inline styles.
• Extra double space before the signature: remove the blank line above it and disable Insert signature before quoted text if you do not want it before replies.
• Different signature per alias: Gmail supports one signature per send-as address — pick the address in the dropdown above the editor.

iOS Mail supports one signature for all accounts or one per account, but its editor is plain text. Getting a formatted signature onto a phone takes a copy-paste workaround — here is the reliable version.

Setting a plain text signature

1. Open Settings on the device, then scroll to Apps and open Mail.
2. Tap Signature.
3. Choose All Accounts or Per Account. Per Account is what you want if you have a work and a personal address on the same phone.
4. Delete Sent from my iPhone and type your signature. Keep it to three or four short lines.
5. Go back — changes save automatically.

Getting a formatted signature onto iOS

Because the editor accepts pasted rich text but cannot create it, the trick is to paste in formatting from elsewhere.

1. Send yourself an email from a desktop client that already carries the full signature.
2. Open that email on the iPhone and press and hold on the signature.
3. Select all of the signature using the selection handles, then tap Copy. Include the whole block, not just the text.
4. Go to Settings, Apps, Mail, Signature, clear the field, then press and hold and tap Paste.
5. Shake the device once and choose Undo if the paste arrives styled in blue Apple defaults — shaking again with Redo often restores the original formatting. If that fails, paste as plain text and keep it simple.

Third-party mail apps

Note that each app keeps its own signature. Someone using Apple Mail for personal and Outlook for work has two to configure, which is the core argument for managing signatures at the server instead of the device.

Apple Mail handles signatures well once you know two things: where the files live, and why your fonts keep reverting.

The standard method

1. Open Mail, then choose Mail, then Settings from the menu bar.
2. Click the Signatures tab.
3. Select the account in the left column, then click the plus button to add a signature.
4. Name it, then build or paste the signature in the right pane.
5. Untick Always match my default message font. Leaving it on strips your fonts and colours — this is the single most common Apple Mail complaint.
6. Choose the signature in the Choose Signature dropdown so it applies automatically.

Pasting an HTML signature that keeps its layout

Pasting code directly gives you code. Paste the rendered output instead.

1. Open your signature HTML file in Safari.
2. Select the whole rendered signature on the page and copy it.
3. Paste into the signature pane with the default-font checkbox already unticked.
4. Send a test mail to a Gmail address and to an Outlook address to confirm the layout survived.

Multiple accounts and per-account defaults

Signatures are assigned per account, so a work address and a personal address can carry different blocks. If you assign several signatures to one account you can also set the dropdown to Randomly or In Sequential Order — useful for rotating campaign banners on a personal brand, and a bad idea for a company where consistency is the point.

Known quirks

• Images appear as attachments to Outlook recipients: use externally hosted images by URL rather than dragging local files in.
• The signature sits below quoted text on replies: that is Apple Mail behaviour and cannot be changed in settings.
• Spacing differs from the original design: Apple Mail adds a line before the signature; account for it rather than fighting it.
• Signature disappears after a macOS update: the version-numbered folder changed. Re-add through the Settings pane rather than the file method.

Yahoo Mail supports a rich text signature per address, but its editor accepts no HTML source and no image upload from disk. Everything has to arrive by paste or by URL.

Desktop setup

1. Click the gear icon at the top right, then More Settings.
2. Open the Mailboxes section and select the mailbox you want to edit.
3. Scroll to Signature and switch the toggle on.
4. Type or paste your signature in the box. To keep formatting, build the signature in a browser page or another mail client, copy the rendered result, and paste it here.
5. Changes save automatically — send a test message to confirm.

Mobile app

Open the app, tap the profile icon, then Settings, then Signature. Enable the toggle and enter your text. As with iOS Mail, the mobile signature is plain text — do not attempt to reproduce a full layout.

Working around the limits

A sensible Yahoo signature

Given the constraints, keep it to five elements: name in bold, role, one phone number as a tel link, one email or website link, and — if you need a visual — a single hosted logo no wider than 200 pixels. Skip banners, skip social icon rows, and skip anything that depends on precise spacing.

The two environments look similar and behave differently. If you are planning a signature rollout across a hybrid estate, the differences below decide your architecture.

The four available mechanisms

Where on-premises Exchange hurts

Transport rules on Exchange Server append a disclaimer, and that is genuinely all they were designed for. The practical problems:

• No per-user data by default. Getting name and title into the block means pulling Active Directory attributes, which the rule engine does not do natively — you end up scripting it.
• Appends at the bottom of the thread. The disclaimer lands under all quoted text, so a long reply chain buries it.
• Encrypted mail cannot be modified, so the rule silently does nothing or wraps the message, depending on your fallback action.
• Images must be linked, never embedded, because the transport agent cannot attach inline content cleanly.

Where Microsoft 365 is better — and still limited

Exchange Online rules support the same appending, plus conditions on group membership, recipient location and message properties. That gives you internal-versus-external logic without scripting, which is the most common real requirement.

Roaming signatures are the newer option: the signature is stored with the mailbox and appears in the compose window across Outlook clients where the user signs in. The catch is coverage — support varies by Outlook build and platform, and mobile behaviour is inconsistent, so it is not a complete answer on its own.

A hybrid estate: what usually works

1. Standardize the directory first. Both environments read the same attributes if you are syncing with Entra Connect, so clean data fixes both sides at once.
2. Use client-side signatures for what the sender sees — the compose window, replies, internal mail.
3. Use a server-side rule as the safety net, scoped so it only stamps mail that arrives without a signature, typically mobile sends.
4. Keep the legal disclaimer server-side and external-only. It is the one block that must never depend on a client being configured correctly.
5. Test the migration path: users moving from on-prem to cloud mid-project will otherwise fall through both rules for a day.

Testing checklist

A signature rule sits in the middle of your mail flow, which means a mistake is not cosmetic. These are the settings that matter and the order to configure them in.

Before you create anything

• Decide the scope. All senders, one group, or one domain — a rule scoped to a pilot group first is always the right start.
• Decide internal versus external. Most organizations want the full block externally and a light block internally.
• Prepare the HTML. Inline styles, tables, hosted images over HTTPS, absolute widths.
• Confirm the directory attributes you plan to insert are actually populated for everyone in scope.

Building the rule

1. Open the Exchange admin center, go to Mail flow, then Rules, and create a new rule using the Apply disclaimers template.
2. Set the condition. Start with sender is a member of your pilot group, and add recipient is external if you want the external-only variant.
3. Paste the HTML into the disclaimer text box. Personalization tokens for directory attributes go in here — test with one user before applying to a group.
4. Choose Append rather than Prepend for a signature. Prepend is for banners and warnings that must be seen first.
5. Set the fallback action to Wrap. This is important — see the warning below.
6. Add an exception so the rule does not fire on messages that already contain a marker string from your client-side signature, preventing duplicates.
7. Set the rule mode to Test with policy tips for a day, review the message trace, then switch to Enforce.

Avoiding duplicate signatures

Duplicates happen when a client-side signature and a transport rule both fire. Two reliable techniques:

• Marker exception: include an invisible unique string in the client-side template and set the rule exception to skip messages containing it.
• Scope split: apply the transport rule only to senders in a group containing mobile-heavy users, rather than everyone.

After go-live

Document the rule name, its conditions and the person who owns the template. Signature rules are inherited by whoever takes over the tenant, and an undocumented rule with a hardcoded office address will outlive the office.

A directory-synced signature is just a template with placeholders. The work is not the template — it is making sure the fields behind it are populated, formatted and owned by someone.

What is actually available to sync

Conditional rows are the whole trick

The difference between a professional signature and an amateur one is what happens when a field is empty. A hardcoded row produces this:

A conditional row produces nothing at all. Every optional field — mobile, direct line, pronouns, certifications, booking link — must be wrapped so the entire row including its label and separator disappears when the value is blank. Test this deliberately with a user who has half their fields empty.

Getting the data clean

1. Export the directory to a spreadsheet and sort by each field to spot blanks and outliers quickly.
2. Normalize phone numbers to a single international format across every record.
3. Reconcile job titles with HR records — the directory usually loses this race.
4. Assign an owner. HR owns titles and departments, IT owns the mail attributes, and someone signs off on both.
5. Add the fields to onboarding. If a new joiner is created without a title, their signature will show it on day one.

Sync cadence and what breaks

Ask how often the signature platform re-reads the directory. Hourly or daily is fine for most companies; weekly is not, because promotions and department moves become visible to customers before your signatures catch up. Also confirm what happens when a user is disabled — the signature should stop, not persist on a shared mailbox someone else now sends from.

A sensible field map to start from

• Always shown: name, job title, company, one contact number, website.
• Conditional: mobile, direct dial, department, booking link, pronouns.
• Rule-driven, not per user: logo, banner, social row, legal disclaimer.
• Never in a signature: home address, personal mobile, internal extension lists, anything that changes weekly.

Most email disclaimers are copied from another company, are far too long, and would not survive scrutiny. A short, accurate, correctly targeted disclaimer is more defensible than a wall of text nobody reads.

What a disclaimer can and cannot do

• It cannot create a contract with someone who never agreed to it. Telling a stranger they are now bound by confidentiality does not bind them.
• It can demonstrate intent — that your organization treats the content as confidential — which matters in disputes and in some regulatory reviews.
• It can satisfy specific statutory requirements, such as company registration details in certain jurisdictions or regulated-sector notices.
• It cannot undo a misdirected email, but it does give the recipient a clear instruction and a contact route.

The four blocks worth having

Note what is absent: virus warnings, opinions-are-my-own boilerplate on corporate mail, and environmental do-not-print appeals. They add length and remove credibility from the parts that matter.

Targeting: the part most companies get wrong

A disclaimer belongs on external mail only. Applying it internally means every reply between two colleagues carries a legal paragraph, and after four replies the thread is mostly disclaimer. Configure the rule with a recipient-is-external condition, and consider suppressing it on replies where it already appears earlier in the thread.

If you operate in several countries, keep one variant per jurisdiction and target by the sender office location field rather than trying to write one paragraph that satisfies everyone.

Formatting so it stays readable

1. Separate it visually from the signature with a thin rule and a clear gap — it is a legal notice, not part of your contact details.
2. Use smaller, lighter text, around 10 to 11 pixels in a mid grey, so it does not compete with the signature.
3. Keep it as live text. A disclaimer inside an image is unreadable when images are blocked and invisible to accessibility tools.
4. Link rather than include for anything longer than a short paragraph.
5. Version it. Keep a dated record of the wording — being able to show what your disclaimer said in a given month is occasionally very useful.

A workable structure

Confidentiality sentence. Instruction for misdirected mail with a contact address. Company legal name, registration detail and registered address on one line. A link to the privacy notice. That is usually four lines, applies externally, and does its job without burying the message it is attached to.

Broken images are the most visible signature failure — a red X next to your name on every message you send. Nearly all of it comes down to three decisions: where the image lives, how big it is, and what happens when it does not load.

Hosted or embedded?

Host on a CDN or your own web server over HTTPS, with a stable path you will not reorganize. Mixed content over plain HTTP is blocked by many clients.

Sizing and resolution

• Export at 2x, display at 1x. A logo displayed at 150px should be exported at 300px wide, then given width=150 in the markup. This is what stops it looking soft on high-resolution screens.
• Always set width and height attributes as well as in CSS. Outlook uses the attributes and ignores some CSS sizing.
• Keep total image weight under about 50KB across the whole signature.
• Profile photos: 72 to 96px displayed, square, with a consistent crop across the team. Mixed crops look worse than no photos.
• Banners: around 500 to 600px wide, no taller than 100 to 150px.

Formats

PNG with transparency for logos and icons. JPG only for photographs. Avoid SVG — support is inconsistent and Outlook does not render it. Avoid WebP for the same reason. Animated GIF is a separate topic with its own trade-offs.

Dark mode

Many clients invert light backgrounds in dark mode, which turns a dark logo on transparent background into a dark logo on a dark background. Two practical fixes: use a logo version with a light outline or light-coloured mark that reads on both backgrounds, or place the logo on a solid brand-coloured rectangle so the surrounding area never inverts underneath it.

Alt text and the images-off test

1. Write real alt text on every image — the company name for a logo, the person name for a photo, the campaign message for a banner. Never leave it empty and never write image1.
2. Disable image loading in your mail client and send yourself the signature.
3. Read what remains. Name, title, phone and company must all still be there as live text.
4. If key information disappeared, it was living inside an image. Move it into text.

A large share of corporate recipients have images blocked by default. A signature that only works with images on is a signature that half-fails silently.

An animated banner can lift clicks noticeably. It can also freeze on a static frame for a large part of your audience and add 400KB to every email you send. Both outcomes come down to how you build it.

Client support, honestly

Build rules

• Under 200KB, ideally under 100KB. This is the discipline that keeps the whole thing viable.
• Three to six frames, not thirty. A subtle change beats a video-like sequence and compresses far better.
• Loop two or three times, then stop. Infinite motion beside text is distracting and is a genuine accessibility problem for some readers.
• Flat colour, limited palette. GIF compresses solid areas well and gradients badly.
• No flashing. Avoid rapid contrast changes entirely — beyond being unpleasant, they can trigger photosensitive reactions.
• Reduce the palette to 64 or 128 colours before export; the size saving is usually large and the visible difference small.

Where a GIF earns its place

Short-lived, specific campaigns: an event countdown, a product launch week, a seasonal announcement. It works because the motion signals that this is new, which is exactly what a permanent element should not signal.

Where it does not earn its place: the logo, a permanent tagline, or anything that will sit in your signature for a year. Permanent motion stops being noticed within days and keeps costing bandwidth forever.

Measuring instead of guessing

1. Run the static version first for two weeks and record the click rate.
2. Switch to the animated version with the same destination and the same UTM campaign but a different content parameter.
3. Compare like for like over a similar period and similar sending volume.
4. Set an expiry date for the campaign at the moment you launch it, so it does not become permanent by neglect.

If the animated version does not outperform the static one by a margin worth the file size, keep the static one. That result is more common than banner vendors suggest.

Your team already sends thousands of emails a month to people who chose to correspond with you. A banner under the signature is the cheapest owned channel you have — provided it is scheduled, measured and retired.

Dimensions that work everywhere

Design rules

• One message, one action. A banner competes with the email body. It gets one sentence and one verb.
• Legible at a glance — minimum 14px equivalent text after scaling, high contrast, brand colours.
• Do not put critical information only in the image. Images are blocked often; the alt text carries the message when they are.
• Leave breathing room: a clear gap and ideally a thin divider between the signature and the banner.
• Match the signature width exactly so the block reads as one composed unit rather than an advert stapled on.

Scheduling beats remembering

The failure mode of banner campaigns is not bad design, it is banners that outlive their campaign. A webinar banner still running three weeks after the webinar makes the whole company look inattentive.

1. Set the end date when you set the start date. Every campaign gets an expiry, without exception.
2. Target by department. Sales can carry a demo offer while support carries a help-centre link. The same banner for everyone wastes the best inventory.
3. Rotate no more than two or three at once. More than that and no one campaign accumulates enough data to judge.
4. Keep a default. When no campaign is scheduled, fall back to a permanent, low-key brand banner rather than empty space.

Measuring properly

Tag every banner destination with campaign parameters so the traffic is identifiable, then judge on downstream outcomes rather than clicks alone.

Track three numbers: click rate per thousand sends, conversion rate on the landing page, and which department generated them. The third number is usually the surprise — support teams often outperform sales, because their mail is opened by people who already have a problem you solve.

What to run when you have nothing to promote

• A customer review or rating badge
• An award, certification or partner status
• A link to your most useful resource, not your homepage
• A recruitment line if you are hiring — your team emails a lot of people in your industry

A row of social icons is the default decoration on business signatures and one of the least examined. Most of them link to abandoned profiles, and every extra icon reduces the chance of a click on any of them.

Include a profile only if all three are true

• It is active — posted within the last month.
• It is relevant to the recipient, not just to your marketing team.
• Someone monitors messages there, because a linked profile is an invitation to contact you on it.

For most B2B teams that leaves two: LinkedIn and one other. For consumer-facing or design-led businesses, Instagram or YouTube may outrank LinkedIn. Five icons signals a checklist, not a presence.

Personal or company profile?

Icons that hold up

1. Size at 20 to 24 pixels displayed, exported at 2x, with even spacing of roughly 8 to 10 pixels between them.
2. Use PNG with transparency, not SVG — Outlook will not render SVG.
3. Pick a treatment that survives dark mode: either official brand colours, or a single-colour set in your brand blue that reads on light and dark. Plain black icons disappear in dark mode.
4. Give every icon real alt text — the platform name, so a blocked-image reader still knows what is there.
5. Link to the profile, not the platform. Broken or generic links are common when icons are copied between templates.
6. Add campaign parameters if you want to see this traffic separately in analytics.

Placement

Put the icon row below the contact details and above any banner or disclaimer. Keep it on one line. If your icons wrap to a second line on a phone, you have too many — which brings us back to the first section.

Signature traffic usually lands in your analytics as direct traffic, which means it looks like it came from nowhere and gets no credit. Tagging fixes that in an afternoon — if you agree the naming convention first.

The five parameters

Which links to tag

• Banner: always. This is the campaign you are actually measuring.
• Website link and logo: yes, tagged as medium logo — this is your baseline volume.
• Booking or demo link: yes, and by department so you can see which team drives meetings.
• Social icons: yes, medium social, one campaign for all of them.
• Email address and phone number: no. Mailto and tel links cannot carry parameters.

Link hygiene that protects deliverability

1. Use HTTPS everywhere. Plain HTTP links in a signature look dated and are flagged by some filters.
2. Avoid public URL shorteners. They are heavily abused, frequently blocklisted, and hide the destination — a bad combination in a business signature. If you need short links, use your own branded domain.
3. Keep the number of links low. Under six total is a good ceiling; a signature with a dozen links looks like a newsletter to a filter.
4. Make link text descriptive. Book a 20-minute call beats Click here, for both people and accessibility tools.
5. Check destinations quarterly. Landing pages get renamed; signatures do not notice.

Reading the data without fooling yourself

Signature clicks arrive slowly and steadily rather than in a spike, so day-level charts will look like noise. Compare month over month instead, and look at three things: clicks per thousand emails sent, conversion rate once they land, and the department mix. If one team produces most of the clicks, either their audience is better matched or their variant is better — worth finding out which before you scale it to everyone.

A phone number in a signature has one job: get tapped on a phone and connect. Two small formatting decisions determine whether it does.

Always use international format

Write the number with the country code and a plus sign, for example +971 4 555 0100. A local-format number fails the moment someone abroad taps it, and increasingly fails locally too because mobile dialers assume international input. Display spacing is for humans; the link is what matters for dialing.

Make it a real tel link

• The href has no spaces, brackets or dashes — digits and a leading plus only.
• The visible text can be formatted however reads best.
• Style the link yourself. If you do not, iOS and some clients auto-detect the number and render it in their own blue with an underline, which breaks your design.
• Extensions go in the href using a comma for a pause or a semicolon before the extension digits, depending on the dialer — test on both iOS and Android before rolling out.

How many numbers?

Two numbers is the practical maximum. Three or more forces the recipient to choose, and the usual result is that they email instead.

Directory-driven numbers

Store the raw international number in the directory and let the template do the formatting and the linking. Then make the mobile row conditional so a user without a mobile number does not ship a signature reading Mobile: with nothing after it. Also confirm that WhatsApp or similar links, if you use them, are built from the same field rather than typed separately — two sources of truth means one of them will be wrong.

Inspirational quotes in signatures are divisive for a reason: they are personal expression attached to corporate correspondence. Sometimes that works. Often it introduces risk nobody assessed.

What a quote actually does

• It adds personality, which can help in relationship-led roles where a signature is otherwise interchangeable.
• It adds length to a block people already skim.
• It attaches someone else opinions to your company. A quote from a controversial figure reads as endorsement, whatever the intent.
• It can raise copyright questions for longer passages or song lyrics — short attributed quotations are generally fine, extended passages are not.
• It ages. A quote chosen in a particular mood sits in your signature for years.

If you allow quotes, set boundaries

1. One line, under about 90 characters. If it wraps to three lines on a phone, it is too long.
2. Always attribute — a quote without a source reads as either plagiarism or self-importance.
3. Nothing political, religious or partisan. This is the rule that prevents the awkward conversation later.
4. Style it as secondary text — italic, smaller, muted grey — so it never competes with the contact details.
5. Keep it out of external mail if your brand is formal, or out of legal and finance signatures regardless.
6. Review annually. Ask people to re-confirm their quote once a year and most will quietly drop it.

Alternatives that do the same job better

The last row is the honest argument: if a line of text under your name is worth the space, it should be doing measurable work. A quote cannot be measured, cannot be scheduled, and cannot be retired without asking the person who chose it.

No mainstream email client plays embedded video reliably, and attempts to force it get messages flagged. The working pattern is simple: a still image that looks like a player, linked to the video.

Why not embed

• Video tags are stripped by nearly every client for security reasons.
• Attached video files are large, often blocked by gateways, and look like a threat to filters.
• Even where playback partly works, it is inconsistent enough that you must build the fallback anyway — so build the fallback and stop there.

The thumbnail pattern

1. Take a strong still frame from the video, or design a purpose-made cover image at roughly 500 to 600px wide.
2. Add a play triangle in the centre — a soft circle with a triangle is instantly readable as video, and it is what earns the click.
3. Overlay a short label and the duration, for example Watch: 90-second product tour. Duration matters; people click when they know the cost.
4. Export as PNG or JPG under 50KB, at 2x for retina, with width and height attributes set to the 1x values.
5. Link the image to the hosted video with campaign parameters attached.
6. Write alt text that carries the message and the action, since blocked images are common.

Where to host

For anything sales-related, a landing page with the video and one call to action beats sending people to a video platform, because the platform is designed to keep them there rather than send them to you.

What to measure

Click rate on the thumbnail, watch-through rate on the player, and action rate after watching. A high click rate with a low watch-through usually means the thumbnail promised something the video does not deliver in its first ten seconds — fix the video opening, not the thumbnail.

A signature designed on a 27-inch monitor and never checked on a phone will break in predictable ways. All five failures have the same root cause: fixed layouts meeting a 375-pixel screen.

The five failures

Build rules for mobile

• Two columns maximum. Three-column signatures fail on phones almost without exception.
• Photo left, details right is the most reliable layout — it degrades to a stacked block gracefully.
• Set a max-width on the outer table and never rely on percentage widths for structure.
• Divider as a bordered cell, not as a background image or a styled div.
• Test with the longest name in your company, not with your own — long names and long titles are what push layouts past the edge.

A short mobile-friendly structure

1. Line one: name in bold, 15 to 16px.
2. Line two: job title and company, 13px, muted.
3. Line three: one phone number as a styled tel link.
4. Line four: email or website as a styled link.
5. Optional: logo no wider than 150px, then banner at full signature width.

That block is under 600px, has four tappable elements with room between them, and reads identically on a laptop and a phone.

How to test properly

Send a test to yourself and open it in the native mail app on an actual phone, not in a browser resized to phone width — the two render differently. Check both light and dark mode, rotate to landscape once, and then reply to the message from the phone to see what a recipient of your reply would get. That last step catches more problems than any other.