Picture your customer's inbox on a Tuesday morning. One email says it is from you — your name, your company's domain, the address they have replied to before. Another says it is from notifications@some-tool-they-have-never-heard-of.com, "on behalf of" you. One of these gets opened. The other gets deleted, marked as spam, or — quietly worst of all — never arrives. If software is sending emails to your customers, the single most important setting is whose domain those emails come from.
The trust problem nobody talks about
Most quoting and follow-up tools send email from their own infrastructure and their own domain. It is easier for them: no setup for you, no DNS records, works out of the box. But look at it from your customer's side. They asked you for a price. Days later, an email arrives from a company they have never dealt with, asking them to click a link about money. That is precisely the shape of a phishing email, and your customers have spent a decade being trained to distrust it.
"Who is this third party emailing me about my quote?" is a question your customer should never have to ask. Every ounce of doubt it creates is friction between them and the word yes — and as we covered in why customers ignore your quotes, friction is usually the real killer, not price.
DKIM in plain English
Email has an awkward historical flaw: the "from" address is just text. Anyone can put anything there, which is exactly how spammers and phishers operate. So the world's mailbox providers — Gmail, Outlook and the rest — now demand proof.
DKIM (DomainKeys Identified Mail) is that proof. Think of it as a wax seal on a letter:
- You publish a public "seal pattern" in your domain's DNS records — a small text entry, set up once.
- Every email sent on your behalf is stamped with a matching cryptographic signature.
- The receiving mail server checks the stamp against your DNS record. If they match, it knows the email was genuinely authorised by the owner of your domain — not forged by a stranger.
That is it. No ongoing maintenance, no technical skill required beyond pasting a couple of records into your domain settings (or asking whoever manages your website to do it — it takes minutes).
Why this matters for deliverability
Mailbox providers have become markedly stricter about authentication, and unauthenticated or weakly authenticated mail is increasingly filtered, throttled or binned outright. The practical consequences for your quotes:
- Verified domain, consistent sending: your follow-ups land in the primary inbox, where decisions happen.
- Unverified or third-party sending: your follow-ups fight for survival in spam and promotions folders. The customer never sees them, your funnel shows "sent but never viewed", and you conclude — wrongly — that the customer is not interested.
If you measure your quote funnel (see what a good quote win rate looks like), poor sent-to-viewed numbers are very often a deliverability story, and DKIM is chapter one of that story.
Brand consistency: small firms look bigger done right
Beyond deliverability and trust, there is a simpler commercial point. Every touchpoint either reinforces your brand or dilutes it. When your quote, your follow-ups, your acceptance page and your eventual invoice all come from the same domain with the same name, you look like an organised, established business — the kind people are comfortable paying a deposit to. When your quote comes from you but the chaser comes from a random SaaS address, you look like a small operation held together with mismatched tools. Customers notice, even if only subconsciously, and it shows up in how quickly they commit.
What good looks like in practice
If you are choosing software that emails your customers, put these on your checklist:
- Emails sent from your own domain, not the vendor's — the from address should be yours.
- DKIM verification as part of setup, with clear instructions for the DNS records.
- Replies come back to you, so a customer who answers a follow-up lands in your inbox, not a void.
- Your branding on any pages the customer sees — acceptance pages, signature pages, payment pages.
This is exactly how Quote Nudge is built. During setup you verify your domain with DKIM (via Resend, the email infrastructure it runs on), and from then on every automated follow-up on your Xero quotes is sent from your own verified domain — your name, your address, your branding, all the way through to the e-signature acceptance page. The sequences are idempotent too, so no customer ever receives a duplicate chase. To the customer, it is simply you being impressively on the ball.
Set it up once, benefit on every quote
Domain verification is one of those rare jobs that is mildly fiddly exactly once and then pays out forever. Fifteen minutes with your DNS settings buys you better inbox placement, fewer awkward "who is this?" replies, and a brand that looks the same at every step from quote to signed acceptance. For email that is asking someone to commit money, nothing less should be acceptable.
Quote Nudge sends every follow-up from your own DKIM-verified domain and chases every unanswered Xero quote until it is signed — £16.79/month, 14-day free trial, no card required. Join the waitlist at quotenudge-x.mcp-g.com.