Every email Salesforce sends for you, from a rep's follow-up to a flow alert to a list email, goes out under your name. We set up the DNS records that prove Salesforce is allowed to send for your domain, the shared addresses your team sends from, the deliverability and bounce settings, and the templates that make each email look like it came from you.
900+ integrations completed · Salesforce partner · We sign BAAs
How it works
SPF and DKIM records published for each domain, with a DMARC policy on top
Org-wide addresses verified and assigned to the profiles that use them
Emails go out from Salesforce, bounces are flagged on the record
Receiving mail servers check whether Salesforce is allowed to send for your domain. SPF lists the servers that may send for you, so Salesforce is added to your existing SPF record. DKIM signs each email with a key: Salesforce generates it under DKIM Keys in Setup, you publish two CNAME records in DNS, and then the key is activated. DMARC tells receivers what to do with mail that fails, and it passes when the signed domain matches your from address.
Org-wide email addresses let a team send from one shared address, like admissions@ or billing@, instead of each rep's own. Each one is verified from its inbox and given to the profiles that should use it. Flow and email alerts can send from them too, so automated emails come from a real address people can reply to.
The Deliverability page in Setup controls what Salesforce sends at all. A sandbox is set to system email only, so test records do not email real people, and production is set to all email. Bounce management flags addresses that bounce right on the lead or contact, so reps fix the address before the next send.
Where your company routes all outbound mail through its own servers, email relay sends Salesforce mail through your mail server, so it follows the same rules as the rest of your email. Templates and letterhead finish the setup, so every email carries your brand.
What's included
Salesforce added to your existing SPF record as one combined record, so nothing that already sends for you breaks.
A DKIM key created in Salesforce for each sending domain, the CNAME records published, and the key activated once DNS is live.
A DMARC record added or adjusted, starting with reports so you see who sends for your domain before anything is blocked.
Shared addresses set up, verified and assigned to the right profiles, with a default no-reply address where it fits.
Access levels set for production and each sandbox, so test data does not email a real person.
Bounce management turned on, so bounced addresses show a flag on the lead or contact.
Salesforce mail routed through your own mail server where your company requires it.
Templates with merge fields and branded letterhead, set up as part of the same project.
List email and mass email set up for your team, with Salesforce's daily sending limits for your edition explained up front.
Flow and integration alerts sent from the right address to the right people.
Every system we connect to Salesforce, in one list
CallRail and CallTrackingMetrics native integrations, with recordings and AI call summaries on the lead
Gravity Forms, Jotform and Typeform fills create leads with tracking attached
LiveChat, SnapEngage, Tawk.to and Avochato conversations saved to the lead
Kipu and Sunwave: admissions in Salesforce, clinical in the EMR, kept in step
CollaborateMD, AdvancedMD and HiLite, with insurance payments on the patient
Stripe, PayTrace and PayPal payments recorded on the opportunity
Google Ads, Microsoft Ads, Meta and TikTok leads in, offline conversions out
ActiveCampaign lists and automations that follow Salesforce
Open other systems from the Salesforce record with SSO
Salesforce data in Google Sheets, BigQuery and Looker Studio
No app for it? We build the connection with Apex and the APIs
Book a free call. We check how your domain is set up for Salesforce and show you what is missing.
The JTS team are extremely knowledgeable when it comes to advertising attribution and maximizing the potential of customer and leads. They know software extremely well, and how all the pieces fit together perfectly. I highly recommend his services to anyone looking to streamline their technology and maximize their sales potential.
I have been thoroughly impressed with the results. JTS team expertise in systems and software integration has given me clear and concise reports, they help me also with generating qualified leads, has been instrumental in driving my business forward. Thank you for everything you have done for my business.
For the past five years, Journeys Through Search has been an incredible marketing company to assist in our PPC, web development and support. Quick responses, vast knowledge and marketing creativity made them such a value add to our organization.
How it works
We look at who sends email from Salesforce, from which addresses and domains, and where it lands.
Priced by project, not by the hour. You approve before we start.
Records prepared for whoever runs your DNS, then Salesforce settings configured and keys activated.
Test sends checked for passing SPF, DKIM and DMARC, and your team shown what changed.
Working with us
US and overnight hours
Our teams cover all hours, so work keeps moving after your day ends.
AI agents in the workflow
We use AI agents in development and content creation, on a HIPAA-compliant Claude Enterprise license, so builds move faster.
900+ integrations completed
We have done this before, and it shows in how we plan and test.
Free call first
Honest advice before any work starts, even if you never hire us.
Yes. Without them, receiving servers cannot confirm Salesforce is allowed to send for your domain, and your emails are more likely to land in spam or be rejected.
We prepare the exact records. Whoever manages your DNS adds them, or we add them with access you give us.
A shared address, like admissions@ or support@, that users and automations can send from. It is verified from its inbox before Salesforce lets anyone use it.
Yes. Email alerts and flows can send from an org-wide email address instead of a user's own address.
Yes. Deliverability in each sandbox is set to system email only, so test records do not send to real addresses.
Yes. Salesforce sets daily limits on list and mass email based on your edition and licenses. We tell you what yours are and set up larger sends to fit.
Yes. See our Salesforce email templates page for templates, letterhead and signatures.
Yes. We sign BAAs for healthcare work.
Yes. Journeys Through Search is a Salesforce partner.
By project, not by the hour. The first call is free, and you get a project quote after it.
