Skip to main content
An email domain sends every partner notification from your own authenticated address, like [email protected], instead of a generic third-party one, so messages are trusted, reach the inbox, and look like they came from you.

​
The problem it solves

​
Impact

A partner who never received the invite has no opinion about your portal. Sending from a domain their mail server trusts is the least glamorous adoption lever there is.

​
How it works

Partner notifications, portal invites, announcements, comments, and deal and CRM updates, normally send from a shared Introw address. An email domain sends them from your own domain instead, so a partner sees [email protected] rather than an address they do not recognize.
The email domain configuration, where partner notifications are sent from your own sending domain instead of Introw's.
Your domain is authenticated with the DNS records Introw provides, so mailbox providers trust the mail and far fewer messages land in spam. Paired with a custom portal domain, it completes the white-label: the portal lives on your URL and the emails come from your domain, with no third-party name anywhere a partner looks. Instead of partner managers chasing partners who never saw an email, notifications send from an address partners trust and recognize. Setup is a few minutes of DNS records, not an engineering project, and there is no migration: existing notification settings stay exactly as they are, so nothing has to be reconfigured. The result is mail that reaches the inbox, gets opened, and keeps partners engaged with the program.

​
Going deeper

How to

Setup, configuration, and all how-to guides.

API reference

Endpoints and code.
Works with

Custom Domains

Portal on your URL, emails from your domain: the full white-label.

Notifications

The same partner notifications, now sent from your domain.

Branding & White-label

Branded emails from a sender partners recognize.