Sending customer emails from your own domain: the setup, step by step

In a familiar sort of afternoon, the quote leaves at 2:14 and the customer calls at 2:40 to ask whether you sent it. It is sitting in Promotions, under a sender she does not recognize. The carefully chosen linen has arrived; the conversation has not.

Set up a recognizable sender, authenticate the store's domain, and test where replies go before relying on automatic messages. OrderPilot guides the email setup and shows the domain records to add. The useful finish line is a sample quote your team can receive, recognize, open, and answer.

1. Choose the sender and the events that send mail

The sender should be the store the customer knows, with a reply path someone monitors. Start in Settings › Messages & notifications and use the guided setup to choose the sender, theme, and logo.

The setup also asks about the moments that should send emails: a newly created quote, the invoice event offered by your workflow, and staff changes to statuses. Read the review of those choices before finishing. They control behavior, not just appearance, so have the person responsible for the order process beside you. Choose a default email theme to give the templates a consistent starting appearance, then inspect individual messages for their job. A quote asks the customer to review a purchase. A signature request asks for agreement. A payment request should make the next payment clear. Those messages deserve different copy even when they share a design.

Keep this alongside the first-week setup plan. The sending decisions should agree with the statuses and payment process you are teaching the staff, so the customer does not receive an invoice before the team considers the order ready.

2. Give the domain records to the person who manages DNS

OrderPilot displays the records needed for the branded sending domain. Copy their type, name, and value exactly into the domain host, then return to the sending-domain panel to review their status.

You need access to the place where the domain's DNS is managed, not necessarily an IT department. If an agency or outside technician maintains the domain, send them the record details and ask them to confirm the result. Avoid guessing at an unfamiliar DNS screen during the Saturday rush. The fabric wall already provides enough combinations for one afternoon. Email authentication helps receiving systems distinguish authorized mail from impersonation. Google's sender guidelines require authentication for mail to personal Gmail accounts and recommend authenticating every sending domain. Correct authentication improves the basis for delivery; it does not guarantee a particular inbox tab.

Use the records shown for your store rather than copying values from another merchant's instructions. Keep existing mailbox records intact unless the person managing the domain has identified a specific change. A pending verification result calls for a record review, not a series of improvised edits.

3. Read the DMARC check before changing the policy

DMARC tells receiving systems how to treat mail that fails the domain's authentication and alignment checks. OrderPilot checks for a record and provides a starter when none is found:

v=DMARC1; p=none;

The starter requests no rejection or quarantine based on DMARC. It contains no report destination; reports need a separately configured rua address. Google's DMARC guide recommends beginning with p=none and reviewing authentication before moving to stricter policies. The policy concerns other mail using the domain too, including normal staff mailboxes and other sending services. Have the domain manager review those senders before changing an existing policy. Do not replace a working stricter policy with the starter simply because it appears in an example. OrderPilot recommends DMARC but does not make this check a prerequisite for sending; mailbox providers have their own requirements.

Once the records are in place, keep a note of who maintains them. The next domain change should not depend on finding the person who remembers a password from the old website project.

4. Decide who receives the customer's reply

Reply-To should lead to a monitored destination. OrderPilot warns about a no-reply address because a customer answering “Can we change the legs?” needs a route back into the sale.

Review default CC and BCC settings and the salesperson copies. Include people who genuinely need the conversation, with a clear owner for the response. Copying several inboxes is not the same as assigning someone to answer.

Optional reply capture brings customer replies into the order's conversation and needs an additional DNS record. Configure the record shown for that feature, then test a reply against a sample order. The result you want is specific: the answer appears with the right order, and the staff member taking over can read what the customer asked.

Without that capture setup, a working Reply-To mailbox still needs its own handling routine. Tell the team where to look. After capture is configured, verify it rather than assuming that successful outbound mail also proves inbound routing.

For an illustrative test, send a Madison sofa quote to a team-controlled inbox. Reply with a question about the walnut legs. Find the message from the staff side and have another associate pick up the conversation. That tests the handoff as well as the address.

5. Keep the email focused on the order

The message should explain the purchase and the next action without making the customer hunt through a promotion. OrderPilot's template editor flags content that can push a message toward Spam or Promotions, and its previews help you inspect the result. Use a subject that identifies the transaction and body copy that answers the immediate question. If you need the customer to approve a fabric change, explain the change and point to the updated quote. A large seasonal-sale banner above the request competes with the reason for sending it.

Each brand can have its own email design. Keep the functional parts consistent enough that staff recognize the action across brands, while the logo and visual style match the customer's showroom. The email-theme guide covers the design choices in more depth.

Review delivery warnings and unsubscribe handling alongside the templates. A warning is useful operational information. Repeatedly sending the same message to an address that fails does not improve its chances of being read.

6. Treat a sending pause as a customer-service task

OrderPilot can pause sending after excessive bounces or spam complaints. The pause protects the store from continuing a pattern that harms future messages. Read the reason and contact OrderPilot support to restore sending; removing and rebuilding the setup is not the normal recovery path.

Customers waiting for a quote or payment request still need attention while the problem is resolved. Review the send log and the affected records, identify what has not gone out, and give urgent conversations an appropriate alternative contact. Keep a note on the order of what was communicated.

Do not assume that every unsent message will automatically replay after support restores sending. Reconcile the affected records with the log, then send the messages still needed. This also prevents an obsolete quote from being sent after a customer has already agreed to a revision. The send-log guide explains what the recorded events establish. A Sent event is not proof that the customer read the quote or that the message appeared in their primary inbox. Use the log to investigate the conversation, then follow up with the customer where necessary.

7. Test the whole message on a phone

Use team-controlled Gmail and Outlook addresses for a practical first test. These are test destinations, not a guarantee that every customer's mailbox behaves the same way.

Open the message in the inbox where it arrived. Read the From line and subject without opening it, then inspect the content on a phone. Open the PDF, follow the signing or payment link appropriate to the sample, and send a reply. Compare what happened with the staff record. Use the phone and dark-mode preview guide to catch faint logos, cramped text, or buttons that are difficult to distinguish. A sample that looks right in the editor still needs this real-inbox check.

Texts are a separate channel. With SMS configured and enabled, OrderPilot can send ready-made messages at selected statuses; staff cannot compose one-off texts or edit those templates. Set up the store's process using the order-texting consent guide, then choose status messages that fit the customer journey.

A checklist for the person managing the domain

• Use the store's intended sending domain and the exact records shown in OrderPilot.
• Review the existing DNS and mail services before changing records.
• Return to OrderPilot and resolve any unverified sending records.
• Review the DMARC result and the existing policy; add a starter only where appropriate.
• Configure the additional reply-capture record if the store will use that feature.
• Send a sample message, open its links, and test the reply route.
• Tell the store who maintains the domain and how to reach them if verification changes.

Give the sending log and the test result to the person who owns customer messages. Then refine the email design and wording around the job each message needs to do.

Sources

1. Email sender guidelines — Google, requirements effective February 1, 2024.
2. Set up DMARC — Google Workspace Help.