In the mail path
Outbound mail is relayed through the platform, the sender is matched to a rule, and the signature is injected into the message itself. Phones, webmail and shared mailboxes are covered — nothing depends on the sending device.
OnBrand Mail
Every message leaves on brand.
Signatures are applied to mail on its way out, not on the sender's laptop. Phones, webmail, shared mailboxes, the person who reinstalled Outlook last week — all of it lands with the current signature, and nobody has to be asked twice.
Works with
- Microsoft 365
- Google Workspace
Australian-owned, Australian-hosted by Trucell.
|
Priya Nair Service Delivery Manager
M 0400 000 000
|
|||
|
|
||||
|
||||
This email is confidential and intended for the named recipient only.
Product
Designed in the console.
Shown in Outlook.
Operators build once. Senders see the same signature beside the message they are writing — and the mail path stamps it again if the client never got a chance.
-
01
Build once
Drag blocks, merge directory fields, and catch Outlook or Gmail issues before anyone hits send.
-
02
See it compose
The Outlook sidebar puts that template beside the message, so senders see what the recipient will.
-
03
Stamp anyway
If the client never applied it, the mail path injects the same template on the way out.
Operator
Console designer
Sender
Outlook compose
How it works
Two ways in,
one source of truth
Most signature tools pick one and live with its blind spot. OnBrand Mail runs both, from the same templates and the same rules — fed by the directory you already keep.
In the client
An Outlook add-in and Gmail integration put the same signature in front of the sender while they type. The two paths know about each other: a message stamped at compose time is not stamped twice.
03
From your directory
Names, titles, phone numbers and photos come from Microsoft Entra or Google Workspace. Change somebody's title once, in the place it already lives, and their signature follows on the next sync.
Console
Built to be handed
to an operator
The console is for people who keep mail moving — designers, IT, MSPs — not for a one-off setup that never gets touched again.
- Designers
- IT
- MSPs
A designer that tells you the truth
The same compiler that runs at publish checks the design while it is being edited: Gmail's size limit, the layouts Outlook mangles, a merge field nobody in the directory has a value for. Preview shows new messages, replies, mobile widths and plain text.
Rules, in the order they fire
Priority-ordered and first match wins, so the list on screen is the logic. Test a sender before you save and see which rule would have matched, and why the ones above it did not.
Campaign banners with real numbers
Add a banner to every signature for a fixed window, then see the clicks it earned. Bot traffic is flagged rather than dropped, so the figure you report is one you can defend.
Staged rollout, and a way back
Onboarding moves a tenant from a pilot group to the whole organisation only once its own checks pass. If a signature is ever wrong, one switch relays that tenant's mail untouched — mail keeps flowing, just unbranded, while it is sorted out.
Pricing
Priced per mailbox,
and only the ones we stamp.
A seat is a mailbox the platform actually signs. The count is reconciled against your directory every night, so leavers stop being billed without anybody filing a ticket.
In the directory
248 mailboxes
Everyone in Entra / Workspace
Stamped tonight
186 seats
Only mailboxes we signed
On the invoice
186 seats
Leavers drop off next sync
- 14-day trial
- Ten-user minimum
- USD, excluding tax
- Invoice or card
Prices in USD per user per month, excluding tax. Annual plans are billed for the year; monthly plans are billed each month and cost more. The minimum is ten users. Every plan starts with a 14-day trial, and nothing is charged until it ends.
Full pricing detailsFor MSPs
Made for people who
run other people's email
OnBrand Mail is multi-tenant from the ground up. One console covers every customer you look after, with roles that stop at the tenant boundary and an audit trail that records who changed what.
Partner console
Staff access stops at the tenant boundary
-
01
Isolation that holds
Per-tenant isolation enforced in the database, not just the interface.
-
02
Delegated access
Staff see the customers they administer, and no others.
-
03
Seats you can defend
Per-mailbox billing, reconciled against the mailboxes actually served.
-
04
Onboarding that isn't freehand
Connector scripts generated per tenant, so setup is repeatable.
Partner margin
Resell it, and keep 15%
Partners earn 15% of the list price on every seat they sell, and choose per customer how it reaches them.
Wholesale
We invoice you at 85% of list, one invoice per customer, with the discount printed on it. You bill your customer whatever you like — at list you keep 15%, above it you keep more.
Referral
Your customer pays us directly at list price and we transfer your 15% once they have paid. Nothing is owed to you on an invoice that goes unpaid, and nothing lands on your ledger that you have to chase.
Either way you administer your customers in the same console, with access that stops at your own book. Ask us about the partner agreement.