← Back to Salestrics Today

Custom Mail Domain: RevOps Setup Playbook

Mail on account only works when outbound sends from org mail — not personal inboxes agents cannot see. Custom mail domain puts your brand on every thread on the revenue graph; it is included on Salestrics One and available on paid standalone tiers. Teams that buy CRM before DNS is verified stall in forward-and-paste habits. This 2026 RevOps playbook is the DNS-to-deliverability checklist — records, verification, teammate rollout, and pairing with mail-on-account policy.

Why custom domain matters for agentic CRM

  • Brand trust — customers reply to yourdomain.com, not a generic address
  • Graph completeness — threads attach to accounts automatically
  • Assistant context — summaries include full customer conversation
  • MCP read prompts — “summarize mail on [Account]” returns data
  • Auto and nurture — sequences send from verified org domain

Mail product: Salestrics Mail. Policy: mail on account.

Pre-flight checklist

  1. Domain registrar access — IT or founder can edit DNS
  2. Subdomain decision — mail.yourdomain.com vs root; document choice
  3. Teammate list — who gets org mail day one vs phased
  4. Legacy forward plan — old Gmail read-only 30 days if needed
  5. Signature template — Connect link, legal footer, unified format

DNS setup (typical flow)

StepActionOwner
1Admin → Mail → Add domainRevOps
2Copy MX, SPF, DKIM to registrarIT
3Wait propagation; click Verify in AdminRevOps
4Create mailboxes or aliases per seat mapRevOps
5Send test to external inbox; check headersIT

Exact record values live in Admin — do not copy generic examples from blog posts.

Deliverability basics

  • SPF aligned — sending server authorized in DNS
  • DKIM signed — outbound mail authenticated
  • Warm-up discipline — no 500-contact blast on day one
  • Bounce handling — remove hard bounces from campaigns
  • Auto governance — nurture caps per Auto playbook

Rollout by role

RoleDay-one org mailException window
AE / AMRequired for customer outboundNone after week 2
CSMRequired
FounderRequired for sales mailPersonal for investors OK if policy allows
MarketingRequired for campaigns
FinanceInvoicing mail if on Ledger

Pairing with migration cutover

If you are migrating CRM same weekend:

  1. Verify domain Saturday — before Monday pipeline work
  2. Forward legacy 30 days — optional safety net
  3. Update CRM email fields — contact emails match new outbound
  4. Connect signatures — meeting links point to in-product Connect

Cutover guide: migration weekend playbook.

Security and compliance notes

  • Offboarding — disable mailbox same day; forward to manager 14 days
  • Shared aliases — support@ on Resolve desk, not personal AE aliases
  • PII — customer mail stays in workspace; no export to personal tools
  • Vendor review — document mail storage for security questionnaires — vendor security playbook

Anti-patterns

  • DNS never verified — paid CRM, personal Gmail selling
  • Per-rep domains — fragments brand and graph
  • Blast before warm-up — domain reputation damage
  • Skip signatures — customers reply to wrong inbox
  • Mail policy without domain — policy unenforceable

30-day mail hygiene review

  • % customer outbound from org mail — target 95%+ for GTM
  • Threads on accounts — spot audit 20 opps
  • Bounce rate — campaign and one-to-one
  • Assistant usage — mail summaries returning context

Troubleshooting common DNS issues

SymptomLikely causeFix
Verification failsDNS not propagatedWait 24–48h; check TTL at registrar
Mail lands in spamSPF/DKIM mismatchRe-copy Admin values exactly
Replies go to old inboxMX still points to legacyUpdate MX; keep forward temporarily
Some teammates on GmailPhased rollout stalledSet hard deadline in mail policy

Free Forever vs paid domain timing

Prove mail habits on Free Forever first — then attach custom domain when upgrading to paid tier or One. Pair with Free Forever to paid so domain setup is week-one on paid, not month six.

Alias and shared inbox patterns

  • sales@ — alias to round-robin or single owner; document in RevOps wiki
  • support@ — Resolve desk queue; not an AE personal mailbox
  • billing@ — finance + Ledger; restricted send permissions
  • hello@ — marketing inbound; Auto enrollment from form

Aliases without owner discipline create orphan threads — assign a human backup for each shared address.

MCP prompt (mail audit)

List open opps over $X with customer mail in the last 30 days not on org domain — read only, for RevOps policy enforcement.

Related reading