Customer stories

Rollout walkthroughs from teams like yours

How organisations use Signavique to standardise signatures, keep contact data current and prove compliance.

These walkthroughs describe typical deployments assembled from real support conversations; company details are composites and metrics are qualitative.

Professional services220 staff · Microsoft 365 · legal disclaimer requirement

Compliant signatures for a 220-person accounting firm, in one afternoon

The challenge

The regulator required a company-level legal disclaimer on outbound email, and partners were responsible for it personally.
Every partner and manager had built their own signature over the years — five different fonts, three logo versions and no disclaimer anywhere.
IT had tried a group policy before; it silently failed on Macs and mobiles, so nobody trusted it.

How they set it up

One approved template, locked down

The marketing team built the firm template in Signavique with the disclaimer add-on, fixed the brand colours and fonts, and left only the personal fields editable.

Deployment rule with sign-off

A deployment rule targeted everyone in the workspace, and the compliance partner used the approval step to sign the design off before it went live.

Every platform covered

Outlook on Windows and Mac picked up the signature through roaming signatures, while the Outlook web and mobile install guides in the user portal covered the rest.

What changed

The approved disclaimer is on every outbound email, and changes go through one approval instead of 220 email requests.
New starters get the correct signature from day one — nobody emails 'what's the signature template?' anymore.
The firm can evidence exactly when the disclaimer was approved and applied, from the activity log.

SaaS & technology85 staff, growing · Google Workspace · HubSpot

A scaling SaaS sales team keeps every outbound email on-brand

The challenge

Sales hired faster than IT could onboard them; new reps sent sequences with whatever signature their last company used.
Marketing ran quarterly campaign banners, but had no way to push one to the team or tell whether anyone clicked.
Contact details lived in HubSpot, so titles and phone numbers in signatures were always out of date.

How they set it up

Templates per team, brand per company

Marketing saved an SDR, AE and customer-success template with locked brand fields; each new hire's signature is assigned from their department automatically.

Live contact data

The HubSpot connector syncs names, titles and phone numbers, and the Google Workspace directory keeps the rest current — no more 'Senior Sales Executive' from three promotions ago.

Campaign banners with tracking

The team schedules a banner into signatures for each campaign, with start and end dates, and reads click counts per banner from the tracking links.

What changed

Every outbound email — sequences included — carries the current brand and a working campaign banner.
Marketing knows which banners earn clicks instead of guessing.
Onboarding a new rep takes minutes, not a support ticket.

Multi-site group60 sites · mixed Microsoft 365 and Google Workspace · strict compliance

One control plane for 60 practices in a healthcare group

The challenge

Each practice had its own mail platform and its own way of doing signatures; the group brand existed only on the website.
Clinicians moved between sites, so job titles and locations changed often — and old titles kept appearing in patient email.
The group needed an audit trail proving who approved each signature change.

How they set it up

Directory sync from both platforms

Microsoft Entra and Google Workspace directories sync into one people list, so a title change in HR flows into the signature without anyone touching mail settings.

Team-level rules with central approval

Each practice maps to a team in Signavique. Regional managers request changes; the group's communications lead approves them, keeping the shared brand elements locked.

Roles that match the org chart

Practice managers can update local details but can't alter the brand header, legal footer or disclaimer — permissions are enforced server-side, not on trust.

What changed

One brand, 60 practices, zero manual mail-settings work — signatures update themselves from the directory.
Every signature change has a named approver and a timestamp.
Clinicians moving sites get the right location in their signature on the next sync, not the next helpdesk ticket.

Want a rollout like these?

Build your first template in the free generator, then connect your mail platform and directory from the admin console. The workspace setup guide walks through the whole path.

Build a signature Workspace setup guide