Sending from your domain
The lead sees your address, and the sending reputation becomes yours.
Everything your workspace sends leaves from an address of ours, carrying your organization name, until you connect your own domain. Connected, the address is yours: the lead sees your company in the sender line, a plain reply lands in your inbox, and the delivery reputation you build up belongs to you.
Where it lives
The card sits on Organization identity, next to your logo, your color and your numbering. Owners and admins connect and change it. You can connect more than one domain — one for each brand you speak for — and one of them is marked In use: it is the address on everything the workspace says in your name (the sales agent touches, the proposal, the proposal nudge, the meeting confirmation). Connecting another one never changes the address in use; that switch is a click of its own, on Use this one.
Connect it in three steps
- 1 Type your domain, like empresa.com, and press Connect. Pasting the whole e-mail address works too: we keep what comes after the @.
- 2 Publish the records shown on the card in the panel where your DNS is hosted. The card marks what is already published, so you only touch what is missing — and when a name is already taken by another value, it asks you to edit that record instead of creating a second one, which your panel would refuse. Copy each value with the button beside it: one wrong character is the whole failure mode here. When we can tell which panel hosts your zone, the instruction names it.
- 3 Press Verify now. DNS takes minutes to propagate, so a first attempt that finds nothing is ordinary. The card lists which record is still missing and why, and you press it again.
| Record | What it does |
|---|---|
| CNAME, delivery | The delivery path. It is what carries the message out under your domain, with the SPF that authorizes it living on our side of the pointer. |
| CNAME, DKIM (two of them) | The signature that proves the message really came from you. Two records, so the key can be rotated without a minute of downtime. |
| TXT, DMARC | Recommended, not required. Sending is released with the delivery CNAME and DKIM in place; DMARC is the policy you publish for the rest of the world, and it starts at p=none so you can watch before you enforce. |
| TXT, ownership | Shows the domain is your organization’s. The value is unique to your workspace, and publishing it takes access to the zone — which is exactly what a domain owner has and nobody else does. Two workspaces of the same group can share a domain: each publishes its own TXT, and the other records stay as they are. |
The Name column already comes relative to the zone, the way most panels ask for it, so paste it as it is. A panel that shows the full name after saving is doing its job. Typing the full name yourself is what produces a record ending in empresa.com.empresa.com, and that verification never passes.
Your address and display name
Verified, the card asks for the part before the @ and for the display name. It starts at contato@ with your organization name, and you change both. The preview shows the exact line the lead sees, which is also the line a reply comes back to.
Before the DNS is ready, and if it breaks
Sending never stops because of DNS. While the records are not verified, the e-mail goes out from no-reply@quathos.com with your organization name, exactly as it did before you connected anything. If a record that used to answer stops answering, the card turns to Needs attention and the sender falls back to ours right away, so what you send keeps arriving while you fix the zone. The state is reread every hour, so a correction made at night is picked up without you opening the screen.
Disconnecting takes effect on the spot. If the one you removed was in use, the next verified domain takes over; with none left, the sender goes back to ours and nothing stops. Changing domains no longer means going without one in between: connect the new one, verify it, press Use this one, and remove the old one when you want. Connection, verification and disconnection each become an audit event, with who did it and when.