> ## Documentation Index > Fetch the complete documentation index at: https://docs.omnilinker.pl/llms.txt > Use this file to discover all available pages before exploring further. # Send from your own domain > Add your shop's address as an e-mail sender, add the DNS records Omnilinker shows, and send customers e-mail from your own domain. E-mails to your customers (a delay notice, "ready for pickup", a reply) leave Omnilinker from a **sender**. Send from an address on your shop's own domain, such as `sklep@twojsklep.pl`, once you have added a few DNS records at your domain's provider. Until then, or if you can't change your DNS, use the **shared sender**. You need the **Set up senders (e-mail domains and the SMS sender name)** permission, and Customer service switched on for your account. ## Add a sender on your domain **1. Open Senders** Open **Customer service** > **Senders**. **2. Enter the address** Under **Send from your own domain**, enter the **Sender address** customers should see and the **Name customers see**. To receive replies somewhere else, fill in **Replies go to (optional)**. Click **Add sender**. **3. Add the DNS records** The sender shows **Waiting for DNS** and a table of records. Add each one in the DNS settings of your domain (see [Where to add the records](#where-to-add-the-records)). Use **Copy** next to the host and the value, so nothing is mistyped. **4. Wait for the check** Omnilinker checks the records every 15 minutes. Each record shows **Found** once it is in place. When every required record is found, the sender shows **Verified**, and e-mails go out from it. To check at once, click **Check now**. > [!NOTE] > > New DNS records can take from a few minutes to a few hours to be visible, depending on your provider. If the records > aren't found within 72 hours, the sender shows **Not verified**. Correct the records, then click **Try again**. ## What the records do | Record | Type | What it does | | - | - | - | | **DKIM key** (three records) | CNAME | Lets the e-mail provider sign your mail for your domain, so receiving servers can check it really comes from you. | | **Bounces (MAIL FROM)** | MX | Undelivered mail returns to `bounce.` under your domain, so bounces are recorded and the address stops being used. | | **SPF (MAIL FROM)** | TXT | Allows the e-mail provider to send for `bounce.` under your domain, so SPF passes. | | **DMARC** | TXT | Recommended, not required, and not checked. `p=none` only asks for reports and changes nothing about delivery. If your domain already has a DMARC record, keep yours. | The records sit on subdomains (`…._domainkey`, `bounce`, `_dmarc`), so they don't touch your website or the mailbox you use today. ## Where to add the records Records are added in your domain's DNS zone, at the company that manages the domain's DNS (often the one you bought the domain from, or your hosting). Two things differ between providers: * **The host.** Omnilinker shows the host without your domain (`bounce`, `abc._domainkey`), which is what most panels want. If your panel asks for the full name, hover the host to see it (`bounce.twojsklep.pl`). * **The MX priority.** Enter the **Priority** shown (10) in the panel's priority field, not in the value. > [accordion] Cloudflare > > Set the DKIM CNAME records to **DNS only** (grey cloud), not proxied. A proxied CNAME doesn't resolve to the DKIM key, > and the record is never found. > [accordion] The panel adds the domain to the host by itself > > If a record isn't found although you added it, check its full name. Some panels append your domain to whatever you > type, so a full name typed into the host becomes `bounce.twojsklep.pl.twojsklep.pl`. Enter the host without the > domain. ## Use the shared sender When your server offers it, **Use the shared sender** sends your e-mails from an Omnilinker address made from your shop's name, shown to customers as "your shop via Omnilinker". Replies go to the address you enter in **Replies go to**. There is nothing to set up, and it can be used at once. ## Choose the sender for a message When more than one sender can send (an address on your own domain beside the shared sender, say), **Message buyer** shows a **Send from** list under the e-mail or SMS channel you picked. It starts on the sender Omnilinker would use anyway, and lists the others by their name. Pick another to send that one message from it; the reply address shown under the channel follows your choice. If the sender you picked can't send any more (it was removed meanwhile), the drawer says "The sender you picked can't send any more. Pick another one." and sends nothing. A bulk **Tell buyers about a delay** run and an automatic message use the default sender. An automation step can name its own sender in **Send from**; see [Automatic messages](https://docs.omnilinker.pl/customer-service/automatic-messages#the-two-steps). ## Where replies go Omnilinker sends e-mails but doesn't receive them. A customer's reply goes to the **Replies go to** address of the sender you sent from, or to the sender address when you left it empty. It never arrives in Omnilinker, so answer it from that mailbox. **Message buyer** says so under the channel ("Replies go to …"). A reply to an SMS isn't received at all, except STOP. See [What happens to an e-mail you send](https://docs.omnilinker.pl/customer-service/email-delivery#where-replies-go). ## What the Senders page also shows At the top, **How every message is sent** sums up the rules that apply to every sender: the SMS quiet hours, what a STOP reply does, and both daily limits with how many were sent today ("500 SMS a day · 12 sent today"). With the **Change customer service settings** permission, **Change quiet hours and limits** opens [Customer service settings](https://docs.omnilinker.pl/customer-service/settings). ## Which addresses can't be used * **Public mailboxes**, such as `@gmail.com`, `@wp.pl` or `@onet.pl`: only their owner can add DNS records there. Use an address on your shop's own domain. * **A domain another Omnilinker account already sends from.** Each domain belongs to one account. If it is your domain, contact Omnilinker support. ## Remove a sender Click **Remove** and confirm. Nothing is sent from the sender again, and its domain is freed. Messages already sent keep showing who sent them. ## Text messages Text messages have their own senders, connected to your own SMSAPI.pl account, on the same **Senders** page. See [Text messages (SMS)](https://docs.omnilinker.pl/customer-service/sms-senders). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.