---
title: Corustone Salesforce Account Engagement — Sending Domain Setup (go.corustone.com)
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-02-10-impromptu-zoom-meeting-121163714.md
tags:
- salesforce
- account-engagement
- dns
- cloudflare
- email
- deliverability
- spf
- dkim
- corustone
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Corustone Salesforce Account Engagement — Sending Domain Setup (go.corustone.com)

## Overview

During an impromptu working session, Mark Hope and Karly Oykhman configured `go.corustone.com` as the sole verified sending domain for Corustone's Salesforce Account Engagement instance. The primary driver was a conflict between the naked domain (`corustone.com`) and Veeth's intranet, which occupies that domain and cannot be repurposed for email sending.

**Attendees:** Mark Hope (mark.hope@asymmetric.pro), Karly Oykhman

---

## Problem: Naked Domain Conflict

Raphael's initial Account Engagement setup assumed the naked domain (`corustone.com`) could be used as the sending domain. This is not possible because `corustone.com` is reserved for Veeth's intranet. Using it for email would break the intranet routing and is therefore off-limits.

> "The Naked Domain doesn't work properly there because Veeth has that — the Naked Domain is being used by their intranet." — Mark Hope

---

## Solution: go.corustone.com Subdomain

A new subdomain, `go.corustone.com`, was chosen as the dedicated sending domain. This is a common pattern (e.g., `go.`, `send.`, `em.`) for isolating email infrastructure from the root domain.

### DNS Records Added in Cloudflare

Both records were added under the `corustone.com` zone in Cloudflare:

| Type | Name | Value | Purpose |
|------|------|-------|---------|
| TXT | `go` | `v=spf1 include:aspmx.googlemail.com ~all` | SPF — authorizes Salesforce/Google to send on behalf of the subdomain |
| TXT | `[salesforce-domain-key]` | *(unique key provided by Salesforce Account Engagement)* | DKIM — domain key for cryptographic email authentication |

> **Note:** The DKIM domain key value is unique to the Salesforce Account Engagement instance. Retrieve it from **Account Engagement → Admin → Domain Management → Expected DNS Entries**.

After saving both records, Salesforce verified `go.corustone.com` as a valid sending domain.

---

## Implementation: Forcing the New Sending Domain

To eliminate ambiguity and ensure all future sends route through the verified subdomain:

1. The old `www` sending domain was **deleted** from Salesforce Account Engagement.
2. `go.corustone.com` is now the **only** sending domain in the instance.
3. Because it is the sole domain, Account Engagement will default to it for all new email sends without requiring manual selection.

---

## Sender Address Configuration

When composing or editing an email send in Account Engagement, the **Sender** field can be configured as:

- **A general address** — e.g., `info@go.corustone.com` (consistent, brand-level sender)
- **The record owner** — dynamically resolves to the Salesforce user assigned to the lead/contact (personalizes outreach)

This is set at the individual email or template level, not at the domain level.

---

## Testing Protocol

Before sending to any external recipients, all new email sends must be tested internally:

1. Send a test to yourself (Karly), Raphael, and Lincoln.
2. Verify sender display name, from address, subject line, and email body rendering.
3. Confirm the email arrives from `go.corustone.com` and passes spam/deliverability checks.
4. Only proceed to a live send after internal sign-off.

> "Don't send one to the world until you're sure." — Mark Hope

---

## Key Decisions

- **Do not use the naked domain** (`corustone.com`) for any email sending — it is permanently reserved for Veeth's intranet.
- **Delete `www` sending domain** to prevent accidental sends from an unverified or incorrect domain.
- **`go.corustone.com` is the canonical sending domain** for all Corustone Account Engagement activity going forward.

---

## Action Items

- [ ] ~~Delete `www.corustone.com` sending domain in Salesforce Account Engagement~~ *(completed during session)* — @Karly Oykhman
- [ ] Send test emails from `go.corustone.com` to self, Raphael, and Lincoln; verify sender display, content, and deliverability — @Karly Oykhman

---

## Related

- [[clients/corustone/_index]] — Corustone client overview
- [[knowledge/salesforce/account-engagement-overview]] — General Account Engagement notes
- [[knowledge/dns/cloudflare-dns-management]] — Cloudflare DNS workflow

---

## Appendix: Secondary Topic — Staffing Discussion (Deferred)

A brief off-topic conversation occurred regarding a staffing decision during a transition period. Karly proposed retaining Melissa and releasing Ben to reduce costs. Mark flagged an unknown risk: Melissa's reaction to a potential role change is uncertain and requires a contingency plan.

**Decision:** Defer to a group meeting with Sebastian to build consensus and define backup options before any action is taken.

> "We can decide what we want to have happen, but it doesn't necessarily mean that's what will happen." — Mark Hope