Internal communications

Internal email that goes out
from your mailbox, not ours.

Built to brand in a real editor, then handed to your company's own Gmail or Microsoft 365 account to deliver. We are never the sender — which changes the deliverability, the pricing and what the tool is able to know about your staff.

01

This is the whole argument,
and it fits in one screenshot.

A campaign built in SlipperySign, delivered by the sender's own mailbox, as the recipient sees it.

inbox — all@company.com

Q3 all-hands: what changed, and what's next

AL Anna Lindqvist anna.lindqvist@company.com  ·  to all@company.com

Team — a short summary of where we landed this quarter, and the three things changing in October.

Everything below is also on the intranet, but I wanted you to have it directly.

MB Marco Bianchi Replied to Anna directly — 11 minutes ago
01 / SENDER Anna's name. Anna's address.

No relay address, and no “via” line beside her name. It is her mailbox, so it is simply her email.

02 / REPLIES Answers go back to Anna.

Into her inbox, in the same thread, where she can actually answer them. Nothing is stranded in a marketing tool.

03 / DELIVERY Your domain's reputation, not a shared IP.

It travels the same path as every other internal mail, so it arrives where internal mail arrives.

04 / RECORD It's in her Sent folder.

Because she sent it. There is no separate system of record to reconcile at audit time.

02

What the tool is unable to do
is the part IT cares about.

Each of these is a property of how the system is built, not a setting someone promises to leave switched off.

0 Recipients identifiable

Opens and clicks are counters. There is no recipient column in the tracking tables, so no per-person report can be produced — by us, or by an employer.

0 Contacts uploaded

Campaigns address the distribution lists already in your directory. Your staff list never leaves your tenant.

0 Passwords held

There is no password field and no password store. Google or Microsoft authenticates, and we receive an address.

EU/US Residency, per customer

Set against the customer record, not the deployment. EU storage carries a jurisdiction restriction.

Answers IT asks for first
AreaImplementation
IdentityFederated to Google Workspace or Microsoft 365. No credential is seen or stored.
SendingGmail API and Microsoft Graph, from the user's own mailbox, under a revocable gmail.send / Mail.Send grant.
Token custodyThe send token lives in the browser for the duration of the send. It never reaches our servers.
RecipientsExisting distribution lists and group aliases, resolved by your mail provider at send time.
MeasurementAggregate counters and a daily rollup. No per-recipient identity is recorded.
RetentionPer-customer policy; campaigns and tracking detail delete themselves on schedule.
AuditSent campaigns are immutable. Administrative actions, including impersonation, are logged.
InfrastructureRuns at the edge. No cold starts, and cost does not scale with your headcount.
03

A real editor, because the person
writing it isn't a designer.

Components on the left, the email in the middle, properties on the right. Built on MJML, so it survives Outlook.

ASections write their own contents list

Mark a section and the table of contents reorders itself. Long updates stop being a scroll.

BLocked regions survive fifty authors

Freeze what must not move. Everyone edits around it and the template still looks like your company.

CApproval that actually blocks

Send stays locked until the named reviewer signs off, and any edit afterwards voids the approval.

DTwo people, one campaign

Viewer and editor roles, and a check-out lock so nobody overwrites anyone mid-sentence.

Send the next one from your own address.

Sign in with the Google or Microsoft account you already have. Nothing to install, and no contact list to upload.

Open the app

SlipperySign Mail — first of a family. Tools for learning experiences follow.