How Zyntro Sends Your Email
Why email sending needs a domain of your own, and what Zyntro does with it.
What It Is
Zyntro does not send your email from a shared Zyntro address. It sends from a sending domain that you own, using mail infrastructure Zyntro provisions for your brand.
That arrangement needs your permission, and permission for email is granted through DNS. You publish a small set of records on your domain, those records tell the world's inbox providers that Zyntro may send on your behalf, and once they are in place your email goes out under your own name.
You set this up once per brand, on Communication > Email > Senders, a screen titled Mail Delivery Settings.
Why It Matters
Email is one of the channels Segmentation Intelligence uses to act on your behalf, so the quality of your sending setup decides whether that work ever reaches anyone. Three things follow from doing it properly.
Your mail arrives. Inbox providers are strict about mail that claims to be from a domain without proof. Correct records are the difference between the inbox and the spam folder.
Your reputation is yours. Because you send from your own domain, the sending reputation you build belongs to you rather than to a pool shared with strangers.
Replies come back into Zyntro. The same setup routes inbound mail for your sending domain back into the platform, which is what lets Zyntro read replies, match them to the right contact, and act on them.
How It Works
Setup runs in two halves, and you will see both on the screen.
First, you nominate the domain. You enter the sending domain you want to use and Zyntro derives a return path domain from it, which handles bounce reports. Before going further, Zyntro checks two records that must already be live: an MX record on the sending domain, which routes inbound mail into Zyntro, and a CNAME on the return path domain. Continue stays greyed out until both are found.
Then Zyntro provisions the sending infrastructure and shows you the records that authorise it: DKIM, which signs your mail cryptographically; SPF, which lists who may send for your domain; and DMARC, your policy for mail that fails those two checks. When all three verify, Activate Setup finishes the job.
Afterwards the screen becomes a DNS Verification dashboard, with a card per record that you can re-check at any time. Each card answers two separate questions: whether the record is published in DNS, and whether it has been accepted for sending. Both have to be true before mail leaves.
Examples
A consultant sends from a subdomain, not their main domain
Their everyday mail runs on example.com. They choose comms.example.com as the sending domain, so Zyntro's traffic and their day-to-day correspondence stay entirely separate. Their normal mailbox is untouched, and a problem with one cannot damage the other.
A reply arrives and Zyntro acts on it
A contact replies to a nurture email. Because the MX record routes mail for the sending domain into Zyntro, the reply lands in the platform rather than an inbox nobody is watching. It is matched to the contact, and the sequence or stream that sent the original message responds according to its reply rule.
Records are published but sending is still blocked
All four cards show Published in DNS, yet nothing sends. Publishing a record and having it accepted are two different events: DNS changes take time to spread, and the delivery service re-checks on its own schedule. Verify All Records asks it to look again.
Important: The sending domain you choose is close to permanent. There is no way to change or remove it from this screen once setup is complete, so read Choosing Your Sending Domain before you type anything.
