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
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
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.
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.
To eliminate ambiguity and ensure all future sends route through the verified subdomain:
www sending domain was deleted from Salesforce Account Engagement.go.corustone.com is now the only sending domain in the instance.When composing or editing an email send in Account Engagement, the Sender field can be configured as:
info@go.corustone.com (consistent, brand-level sender)This is set at the individual email or template level, not at the domain level.
Before sending to any external recipients, all new email sends must be tested internally:
go.corustone.com and passes spam/deliverability checks."Don't send one to the world until you're sure." — Mark Hope
corustone.com) for any email sending — it is permanently reserved for Veeth's intranet.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.www.corustone.com sending domain in Salesforce Account Engagement~~ (completed during session) — @Karly Oykhmango.corustone.com to self, Raphael, and Lincoln; verify sender display, content, and deliverability — @Karly OykhmanA 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