Custom Email Domain Integration Guide

We're updating how emails are sent from the Engagement Hub (EH) so that you can send emails from your own domain instead of the default system email.

Currently, all Nexus communications — including emails, invitations, user registrations, and password resets — are sent from s17@briefingedge.com. With this update, you'll be able to use your own email alias, such as EBC@yourdomain.com, improving trust and deliverability to your customers.

Why this matters:

Emails will come from your domain instead of @briefingedge.com
You maintain control over branding and reply handling.
Replies will be sent to an inbox you control.

If you prefer not to use a custom domain, you can continue using s17@briefingedge.com — no changes needed.

Here are the two most used methods to perform this Custom Email Domain process along with their use cases and required information:

Option 1 - SMTP (SMTP Credentials)

Use Case:

You want to send emails from a specific address like scheduler@client.com using your SMTP server.

Required from You:

Email Address to send from
SMTP Host & Port

SMTP Username & Password

Option 2 - AWS SES (Domain Authentication with DKIM/SPF)

Use Case:

You want to send from your domain (e.g., @clientdomain.com) without exposing SMTP credentials.

Required from You:

Email Address (e.g., noreply@clientdomain.com)
Email Domain (e.g., clientdomain.com)