Mon - Sat: 9:00 AM - 6:00 PM
Platform Features
Email Domain Authentication for Dealership Senders
Every drip, blast and one to one email your team sends from the CRM can carry your store's own domain, which is the difference between the inbox and the junk folder.
What email domain authentication does for a dealership
Email domain authentication makes every message LeadLocate CRM sends on your behalf leave as mail from your dealership's own domain, with the records in place that let the receiving server confirm you authorized it. That is the one sentence version. The longer version starts with how inbox providers decide what to do with a message. They look at the domain the message claims to be from, they check whether that domain has published records naming the servers allowed to send for it, and they look at the sending history of that domain. A message that passes those checks from a domain with a clean history goes to the inbox. A message that fails them, or that comes from a shared address thousands of unrelated senders also use, is on much thinner ice.
For a store that sends a handful of emails a week from a personal mailbox, none of this matters much. For a store running email drips, bulk blasts and automated first replies to every lead, it is the whole game. Volume from an unauthenticated or shared address is exactly the pattern receiving servers are built to distrust. Authenticating the store's domain turns the CRM into a sender the inbox providers can vouch for, and it does it once, for every user and every tool in the account.
This is a deliverability feature, and most dealers do not know a CRM can do it in house. The full features list shows where it sits among the communications tools, and the auto dealer software CRM page covers the broader email picture.
How it shows up on a normal day at the store
The honest answer is that on a normal day nobody at the store notices it, which is the point. The BDC agent replies to a lead from the CRM email composer and the reply arrives from the store's domain. The internet director queues Thursday's aged inventory blast under Marketing Tools and the ninety copies arrive from the store's domain. The Automated Templates set answers a Sunday night lead within the minute and that reply arrives from the store's domain. The customer sees the dealership's name where the sender goes, hits reply, and the reply threads back into the CRM inbox under the lead.
What the store does notice is the absence of the old problems. Fewer customers saying they never got the email. Fewer replies bouncing off a shared address and vanishing. Fewer salespeople giving up on email and texting from their personal phones because the CRM email did not seem to land. And when a customer forwards the store's email to a spouse, the spouse sees the dealership's domain, not a string of characters from a sending service.
The day it does get noticed is the day a store switches over. A manager who has been watching open activity on a drip usually sees the change without being told, because the messages that were going to the junk folder start being read. That is the scene most stores describe, and it is the reason this page exists.
Questions? Request a Call Back
Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.
Prefer to talk right now? Call or text 844-376-2274.
Where it lives in the CRM, and who touches it
Domain authentication is account level, not per user. It is set once for the dealership, by the Master Administrator working with our team, and from that point every send from every user in the account carries the store's domain. The CRM's user roles, User, Manager and Master Administrator, keep it out of reach of a new salesperson, which is right: a sending domain is a store asset, like the phone number on the sign.
The domain itself can be one the store already owns or one purchased through the CRM. The Website menu includes domain search, purchase, transfer out and a self service DNS editor, so a store that manages its own domain inside LeadLocate can publish the records the authentication needs without leaving the platform. A store whose domain is managed elsewhere gets the records from our team and adds them where its domain lives. The custom domains and DNS page covers the domain tools in detail.
Once authenticated, the domain is used by every email tool in the account: the composer under the Email menu, Bulk Email and Email Automation under Marketing Tools on the dock, Automated Templates and Follow Up Processes under Billing and Admin, and the email composer in the LeadLocate mobile app. There is no second setting to remember in each tool.
What the records actually do
Two kinds of records carry the weight. The first names the servers allowed to send mail for the domain, so when a message arrives claiming to be from the store, the receiving server can check whether it came from a server on that list. The second attaches a signature to each outgoing message that the receiving server can verify against a public key published on the domain, so the message is provably unaltered and provably authorized. The industry names for these are SPF and DKIM, and a third record, DMARC, tells receiving servers what to do with a message that fails and where to send reports.
None of this is dealership specific, which is why it is easy to skip and expensive to skip. What is dealership specific is the volume and the pattern: a store sends a burst of nearly identical emails to a list, then a steady trickle of one to one replies, then another burst. That pattern from an authenticated domain with a clean history reads as a business doing business. The same pattern from an unauthenticated address reads as something to be cautious about.
Authentication is not a reputation by itself. A store that authenticates its domain and then blasts a list full of dead addresses will still hurt its standing, which is why the Email Validator sits next to the sending tools. Authentication plus clean lists plus messages people actually asked for is the combination that keeps a store's domain in good standing.
What it replaces and what an unauthenticated domain costs
The direct replacement is a deliverability add on from a separate email platform, or the consultant a store hires when its emails stop arriving. The indirect replacement is the workaround that most stores fall into without naming it: salespeople who stop trusting CRM email and send from personal mailboxes, where nothing is logged, nothing threads under the lead and nothing survives the salesperson leaving.
The cost of an unauthenticated domain is mostly invisible, which is why it persists. The blast that reached forty percent of the list instead of all of it does not send a report saying so. The drip step that landed in junk does not tell the manager. The customer who replied to a shared address and got no answer does not call to complain. What the store sees is email that seems not to work, and the usual response is to send less of it, which is backwards.
Email domain authentication is part of every LeadLocate plan, from CRM Only at $199 a month to the lead plans, with no deliverability surcharge. The pricing page lists what each plan includes.
The compliance angle: the store is the sender, on the record
Authentication settles a question that comes up whenever a customer disputes an email: who sent it. With the store's domain authenticated, the answer is the store, verifiably, and the CRM's communications log records the send under the lead with the date and the user. That pairing, a provable sender and a logged send, is what a manager wants in hand when a customer says they never agreed to be emailed or asks what they were told about a price.
It also protects the store from the opposite problem, someone else sending as the store. A domain with authentication records published tells receiving servers to reject or quarantine mail that claims to be from the dealership but did not come from an authorized server. That is a real protection for a business whose name is on a sign and whose customers will open anything that looks like it came from there.
Consent is still the store's responsibility. Authentication makes a message trustworthy; it does not make it wanted. Sending to customers who gave the store their address, honouring requests to stop by removing the contact from the campaign lists and processes, and keeping the record are the practices that go with it. Texting consent has its own rules, covered on the do not call scrub and blacklist page.
How to turn it on
Ask. Email domain authentication is available on request, and our team puts it in production for your dealership. The Master Administrator opens a support ticket from More Options on the dock or raises it on the onboarding call, tells us which domain the store wants to send from, and our team supplies the records. If the domain is managed inside the CRM, the records are published through the self service DNS editor under the Website menu. If the domain is managed elsewhere, whoever handles the store's website adds them there, which takes a few minutes. Once the records are live, every email tool in the account sends from the store's domain without any per user change.
The one decision to make beforehand is which domain. Most stores use the same domain as their website so that the email address a customer sees matches the site they visited. A group with several rooftops can authenticate a domain per rooftop, so each store's email arrives as that store. If you want to see the result before you sign up, the pre-recorded live demo shows email leaving the CRM and arriving in a customer's inbox.
What to pair domain authentication with
Pair it with the Email Validator so the authenticated domain only ever sends to addresses that exist. Pair it with Email Automation and Follow Up Processes, which are the tools that generate the volume that makes authentication matter. Pair it with the email inbox and composer for the one to one replies that carry the same domain and thread under the lead. And pair it with the Reports dashboard on the dock, where email activity by user and by day shows whether the messages are earning replies once they are landing.
For a store that also runs personal salesperson websites or Lead Pages landing pages on a custom domain, the domain tools under the Website menu are the natural companion, because the domain a customer sees on the page and the domain they see on the email should be the same one. And when the email does its job and the customer answers, the vehicle insert button, the appointment booking link and the desking tool are all one click from the same thread.
Frequently Asked Questions
What is email domain authentication?
Records published on your dealership's domain that let receiving mail servers confirm a message claiming to be from your store was actually authorized by your store. In LeadLocate CRM it means every email the CRM sends leaves from your own domain rather than a shared sending address.
How do I check whether my domain is authenticated?
Ask our team through a support ticket from More Options on the dock, or on your onboarding call. We confirm which records are live for your domain and supply any that are missing. If your domain is managed inside the CRM, the self service DNS editor under the Website menu shows the records directly.
Which methods does LeadLocate use to authenticate a domain?
The standard ones inbox providers expect: a record naming the servers allowed to send for the domain, a signature on each message verified against a key published on the domain, and a policy record telling receivers what to do with mail that fails. The industry names are SPF, DKIM and DMARC.
Does authentication apply to every user and every tool?
Yes. It is set once at the account level and covers the composer, Bulk Email, Email Automation, Automated Templates, Follow Up Processes and the mobile app composer for every user in the account.
Does my store have to buy its domain through LeadLocate?
No. A domain you already own works; our team supplies the records and whoever manages your domain adds them. Domains bought through the CRM's Website menu can publish the records through the built in DNS editor.
Is there a charge for domain authentication?
No. It is part of every LeadLocate plan, from CRM Only up, and our team puts it in production for your dealership on request.
More Resources from LeadLocate
Send as your dealership, every time
Email domain authentication is part of every LeadLocate plan, month to month. Tell us the domain, and our team puts it in production for your dealership.
Prefer to talk right now? Call or text 844-376-2274.


LeadLocate™ All rights reserved. Other product and company names mentioned herein are the property of their respective owners.
Answers to your questions:
LeadLocate is an all-in-one lead generation software and CRM platform. We generate in-market sales leads and provide you with all the tools necessary to sell that customer. All of your leads, texts, calls, emails, deals, and files are available in one place, accessible with a single login.
LeadLocate™ All rights reserved. Other product and company names mentioned herein are the property of their respective owners.
Answers to your questions:
LeadLocate is an all-in-one lead generation software and CRM platform. We generate in-market sales leads and provide you with all the tools necessary to sell that customer. All of your leads, texts, calls, emails, deals, and files are available in one place, accessible with a single login.



