Nurturing configuration

Nurturing configuration covers the infrastructure that powers your email workflows — domains, senders, and default settings. Before you can create workflows and send emails, this foundation needs to be in place. Once configured, it mostly runs quietly in the background.

This article provides an overview of nurturing configuration and how the pieces fit together.

Accessing nurturing settings

Add your domain

1. Go to Settings > Integrations > SendGrid
2. Add your sending subdomain
3. Rizer gives you DNS records to add
4. Add those records in your DNS provider
5. Return to Rizer and verify

Create senders

1. Go to Settings > Emails > Senders
2. Create sender profiles with names and email addresses
3. Test that emails send correctly

Workflows themselves are managed separately under Nurturing in the main navigation, not in Settings.

How the pieces fit together

Understanding the relationship between domains, senders, and workflows helps you configure everything correctly.

Domains are the foundation

A domain is the base address for sending emails — the part after the @ sign. Before you can send any nurturing emails, you need at least one verified domain.

You own the domain (like yourcompany.com) and create a subdomain for Rizer to send from (like mail.yourcompany.com). Verification proves you control the domain and authorizes Rizer to send on your behalf.

Senders live on domains

A sender is a specific email identity — the name and address that appears in recipients’ inboxes. Senders are created on verified domains.

One domain can have multiple senders:

• sarah@mail.yourcompany.com
• sales@mail.yourcompany.com
• updates@mail.yourcompany.com

Each sender has a name (what recipients see) and an email address (where it comes from).

Workflows use senders

When you create a nurturing workflow, you assign a default sender. That sender’s name and email appear on every email in the workflow unless you override at the step level.

The hierarchy:

1. Domain must be verified
2. Sender must be created on that domain
3. Flow uses that sender to send emails

Domain configuration

Domains are configured in Settings > Integrations > SendGrid.

What you’ll see

The domains list shows:

• Domain name — The subdomain you’ve added (mail.yourcompany.com)
• Authentication status — Active, Pending Verification, or Deactivated

Domain statuses

Pending verification — You’ve added the domain but DNS records aren’t verified yet. Emails can’t be sent until verification completes.

Active — DNS records are verified. You can create senders and send emails from this domain.

Deactivated — You’ve manually deactivated the domain. All senders on it stop working. Reactivate to resume.

Adding a domain

1. Click + Domain
2. Enter your sending subdomain (mail.yourcompany.com)
3. Click Save

The domain appears with Pending Verification status. You’ll need to add DNS records to verify.

Viewing DNS records

Click a domain row to expand and see the required DNS records:

• SPF record — Authorizes Rizer’s servers to send for your domain
• DKIM record — Adds cryptographic signatures to prove email authenticity
• CNAME record — Points your subdomain to Rizer’s infrastructure

Copy these records and add them to your DNS provider (Cloudflare, GoDaddy, AWS Route 53, etc.).

Sender configuration

Senders are configured in Settings > Emails > Senders.

What you’ll see

The senders list shows:

• Sender name — The display name recipients see
• Email address — The from address
• Domain — Which verified domain this sender uses
• Status — Active or Deactivated

Adding a sender

1. Click + Sender
2. Select the Domain from verified domains
3. Enter the Name (what recipients see, like “Sarah from Acme”)
4. Enter the Email address local part (the part before @)
5. Optionally set a Reply-to address if replies should go elsewhere
6. Click Save

Sender fields explained

Name

The friendly name shown in email clients. Recipients see this before they open the email.

Good names:

• “Sarah Chen” — Personal and direct
• “Sarah from Acme” — Personal with company context
• “Acme Sales Team” — Professional team identity

Avoid:

• Generic names that don’t connect to your brand
• Names that look spammy or impersonal

Email address

The sending address. Combined with the domain, this is the full from address (sarah@mail.yourcompany.com).

Common patterns:

• firstname@ (sarah@)
• firstname.lastname@ (sarah.chen@)
• role@ (sales@, hello@)

Reply-to address

Where replies go. Leave blank to use the sender email, or specify a different address.

Use a different reply-to when:

• The sending address isn’t monitored
• You want replies centralized in a team inbox
• The sending subdomain can’t receive email

Important: Make sure someone monitors the reply-to address. Replies to nurturing emails are buying signals.

Deactivating a sender

When someone leaves the company or you want to stop using a sender:

1. Click the menu icon next to the sender
2. Click Deactivate

What happens:

• The sender can’t be selected for new workflows
• Existing active workflows using this sender continue sending (to avoid breaking live campaigns)
• The sender stays in your list for reference

Default settings that affect nurturing

Some organization-wide settings affect how nurturing works.

Default email template language

Set in Settings > Organization, this determines:

• The default language when creating new email templates
• System text like unsubscribe footers
• Template suggestions and pre-built designs

If you nurture in multiple languages, create separate workflows for each. This setting just establishes the default starting point.

Organization timezone

Also in Settings > Organization, the timezone affects when scheduled emails send. Nurturing emails are queued and sent based on your organization’s timezone.

Managing multiple senders

Multiple senders serve different purposes within your nurturing strategy.

Common sender patterns

Individual reps: Each salesperson has their own sender. Emails feel personal because they come from someone the prospect knows.

Team identities: sales@, support@, marketing@ for broader campaigns that don’t need personal attribution.

Executives: Occasional emails from leadership for high-value prospects or important announcements.

Content/thought leadership: A sender for educational content that positions your company as experts.

Choosing senders for workflows

When creating a workflow, consider who should appear to be reaching out:

• Personal relationship exists? Use the rep who worked with them
• No personal relationship? Use a friendly team identity
• High-value prospects? Consider a senior person
• Educational content? Consider marketing or thought leadership

Consistency within workflows

Generally, keep the sender consistent within a workflow. Starting with Sarah and switching to John mid-sequence feels disjointed.

Exception: A final step from a senior person (“I noticed Sarah has been in touch…”) can work well for escalation.

Common questions

How many senders can I have per domain?

No specific limit. Create as many as makes sense for your team and use cases.

What happens to emails in progress if I deactivate a sender?

Emails already queued for sending should complete. New emails won’t send until you reactivate or assign a different sender to the workflow.

Do I need a separate domain for each product line?

Usually not necessary. One domain with multiple senders works for most organizations. Separate domains are more useful for separate brands or complete isolation needs.

Can I use my personal email as a sender?

Only if your personal email is on a domain you control and have verified. You can’t send from gmail.com or other public email providers.