Compatibility

Gmail Web (mail.google.com) renders Sigent signatures in full HTML — colors, links, images, and tables work as designed. The mobile Gmail app on iOS and Android also picks up the signature, but with a couple of caveats: Gmail mobile re-saves a copy when you compose, so updates from the dashboard may take a few hours to propagate. Personal Gmail accounts and Google Workspace accounts both work identically.

Before you start

• Sign in to Gmail at https://mail.google.com.
• Have your Sigent.ai install link ready (from the dashboard’s Share button).
• If you use Google Workspace, confirm with your admin that user-set signatures are allowed.

Steps

1. Open your install link and click Copy to clipboard.
2. In Gmail, click the gear icon in the top right and choose See all settings.
3. Scroll down to the Signature section.
4. Click + Create new and give the signature a name (e.g. “Sigent Pro”).
5. Click into the signature editor and paste with Cmd/Ctrl + V.
6. Under Signature defaults, choose the new signature for For New Emails Use and On Reply/Forward Use.
7. Make sure Insert signature before quoted text in replies is checked if you want the signature above the reply trail.
8. Scroll to the bottom and click Save Changes.

Verify your signature

Send a test email to yourself from Gmail Web. Open it in Apple Mail or another client to confirm rendering travels well. Try replying to your own message — the signature should appear above the quoted text.

Troubleshooting

• Signature size warning (“Signature too long”). Gmail rejects signatures larger than 10 KB. If you see this, reduce avatar/logo dimensions or trim disclaimer copy. Sigent’s render engine targets sub-5KB output by default.
• Custom fonts aren’t rendering. Gmail strips @font-face declarations and unknown font families. Stick to web-safe fonts (Arial, Helvetica, Georgia) or accept that recipients see a fallback. Sigent uses Arial as the default for this reason.
• Images don’t appear for some recipients. Gmail blocks remote images by default until the recipient clicks “Display images below.” This is per-recipient behavior, not a Sigent issue. Avatars and logos stay broken-image-icon until the recipient opts in.
• “Did you mean to send this signature?” prompt. Gmail sometimes flags signatures with links to URL shorteners or mailto: chains with many recipients. Use clean canonical URLs (avoid bit.ly) and a single mailto: for your primary email.
• Signature appears below quoted text on replies. Re-check Insert signature before quoted text in replies in Settings → Signature.
• Updates from the dashboard don’t show in Gmail. Gmail caches the signature locally per browser profile. Re-paste from your install link after editing to refresh.

Notes

Gmail Web is the most forgiving client we support. If a signature looks broken in Gmail Web, it will likely look worse in Outlook Classic — fix Gmail first and the rest tends to follow.

Need help? Contact support — we usually respond within 24 hours.