Sending Settings

The address an email comes from matters as much as what's inside it. Sending settings is where you control that: the From name, the From address, where replies land, and (optionally) the domain you send from.

To find it, go to Emails then Settings. The page has two tabs, Identities and Domains.

How it fits together

There are two layers here:

• A sending domain is the part after the @, for example a subdomain like mail.yourband.com. You can use the platform's shared default with no setup at all, or verify a domain you own.
• A sending identity is a full email address built on top of a domain, for example hello@mail.yourband.com, with a friendly From name like "Your Band" attached and an optional reply address.

Every email goes out from one identity. If you only ever want to use the default that's set up for you, you can skip the Domains tab entirely.

Identities

Open Emails then Settings. The Identities tab is the default view.

When your account is first created, a default sending identity is set up automatically so you can send right away. You'll see it in the list with a Default badge. Each identity row shows:

• The address itself.
• The From header preview, which is exactly what shows up in an inbox, for example Your Band <hello@mail.yourband.com>.
• The Reply-To address, if you've set one.

Editing an identity

Open the More menu on an identity and pick Edit identity. Two things are yours to change:

• From name. What fans actually read in their inbox, and usually more important than the address itself. Use your project name rather than a personal name, unless personal is the brand.
• Reply-To (optional). Where replies are routed when someone hits reply. Leave it blank and replies fall back to your account email.

Click Save and the change applies to everything sent from that identity from then on.

Adding another identity

You might want a separate address for different kinds of message: newsletter@, tour@, merch@. To add one:

1. Click Add identity in the top right of the identities card.
2. Pick a Sending domain from the dropdown. The platform default is always available, plus any domains you've verified.
3. Type the Address, meaning the part before the @. Letters, digits, dots, hyphens and underscores only.
4. Type the From name recipients should see.
5. Optionally set a Reply-To address.
6. Click Add sending identity.

The new identity appears in the list and is ready to use immediately.

Setting the default identity

The Default identity is what everything uses unless something else says otherwise. Broadcasts always use it. To change it:

1. Open the More menu on a non-default identity.
2. Pick Make default.

Choosing a different address for one automation

Inside an automation, the Send email step has its own Send from picker. Leave it on Default sending identity and it follows whatever your default is. Pick a specific address instead and that step always sends from it, no matter what the default becomes later.

If an address you pinned there is later deleted, or its domain stops being verified, the step says so and publishing the automation is blocked until you choose another one. See automations for the rest of the step.

Deleting an identity

You can't delete the default identity. Make a different one the default first, then delete the old one through its More menu.

Domains

Open the Domains tab to see and manage sending domains.

The platform default is listed first, marked Platform default. It works without any setup, but the From address sits on a shared domain. That's completely fine for getting started. For serious sender reputation and brand polish, you'll want your own domain.

Adding a domain you own

1. Click Add domain in the top right.
2. Type the Domain you want to send from, for example a subdomain like mail.yourband.com. A dedicated subdomain such as mail. or email. is safer than your main domain, because it keeps your normal business email out of the way.
3. Optionally type a MAIL FROM domain, typically a bounce. subdomain. This improves deliverability further by letting bounce messages route through your own domain.
4. Click Add domain.

The domain appears in the list with a pending status and a block of records to publish.

Publishing the records

You'll see up to two sets of records:

• DKIM records: three CNAME entries that prove you control the domain and let receiving servers verify each message you send. Each row shows the name, the type CNAME, and the value. Click any value to copy it.
• MAIL FROM records, if you set a MAIL FROM domain: an MX entry and a TXT entry that route bounce messages back through your own domain.

To publish them:

1. Open the dashboard where you manage your domain's records (usually wherever you bought the domain).
2. For each row in the list, create a record with the matching name, type and value.
3. Save and wait. Changes usually take a few minutes, occasionally a few hours.

Verifying

Once the records are live, come back to Emails then Settings then Domains and click Re-check on the domain. TribeNest looks the records up and confirms they're visible. When everything checks out the status flips to verified, and from that point you can build sending identities on it.

The badges to watch for:

• pending: the records haven't been confirmed yet. Either they haven't spread yet, or they don't match.
• verified: the domain is ready.
• failed: verification didn't succeed. Check the records again.
• MAIL FROM: SUCCESS / pending: a separate status for the MAIL FROM subdomain, shown next to the main status when you've set one.

You can re-check at any time, and the Last checked time appears under the domain row.

Removing a domain

Click Delete on a domain row to remove it. The platform default can't be deleted. Removing a verified domain breaks any identities built on it, so make sure those are unused first.

Whose brand automatic emails carry

Broadcasts you design carry whatever is in your template. The emails TribeNest sends for you (sign-in codes, order confirmations, booking reminders, membership notices) are branded automatically, and they follow the site they came from.

That means:

• If a fan bought from one of your sites, the confirmation carries that site's name, colours, typeface and corner style, and the links in it point back to that site.
• If several sites live under one account, each one's emails look like that site rather than like the account as a whole.
• If the message can't be traced to a particular site, it falls back to your account's own name and look.
• If a message comes from one of your apps, that app's own branding wins.

There's nothing to switch on. Repaint a site's theme and its emails follow within a minute or so. See my website for where those colours and fonts are set.

Why bother verifying a domain?

For getting started, the platform default is fine. Once you're sending real volume:

• Better deliverability. Major inbox providers trust domains that authenticate cleanly.
• Brand polish. An address on your own domain looks like the real thing rather than a shared platform address.
• Fewer "via" labels. Some inbox providers add a "via" notice when the From domain doesn't match the underlying sender. Verifying your domain removes that.

Where to go next

• Ready to design something to send? See creating a template.
• Got an audience to send to? See email lists.
• Time to send your first real campaign? See sending an email.
• Want full mailboxes on your domain, not just a sending address? See business email.
• Curious what your sends are costing? See email credits.