Every loan officer has had the same conversation. You email a borrower their next steps, you get silence, and three days later they say the words that cost you the deal: "I never got that." Sometimes that is a busy borrower. Often it is deliverability — and deliverability is not luck. It is a function of who is sending, from what domain, with what reputation. LoanOfficer.ai now lets you take ownership of all three by connecting your own SendGrid account as the outbound email provider.
What the Integration Actually Changes
Out of the box, outbound mail leaves on shared infrastructure. That works, and for many originators it always will. But once your volume grows — a database of several thousand contacts, monthly equity reports, evergreen nurture campaigns, AI follow-up running around the clock — you want the sending identity to be yours. Connecting SendGrid over SMTP relay does exactly that: your authenticated domain, your sender reputation, your suppression list, and your reporting on opens, bounces, and spam complaints.
The practical upside is visibility. When a campaign underperforms on a shared sender you are guessing. When it underperforms on your own SendGrid account you can open the activity feed, see whether the message was delivered, deferred, bounced, or dropped, and act on the answer.
The Five-Minute Setup
The whole configuration lives in your own user settings, which means each person on a team connects their own sending account. Open User Settings, and under User Information scroll to Calendar & Email Integrations. Click Add New and enter SendGrid as the provider name.
1. Get your username from SendGrid
This is the step that trips people up: the username is not your login email. Inside SendGrid, open the Email API section, click Integration Guide, and choose SMTP Relay. SendGrid displays the username to use. Copy it and paste it into the Username field. SendGrid's own SMTP getting-started documentation shows the same screen if you want a second reference while you work.
2. Server, port, and email address
- SMTP server:
smtp.sendgrid.net - Port: 25, 587, or 465 for SSL connections. Port 587 is the standard submission port and the safest default; choose 465 when you want the connection encrypted from the first byte.
- Email: the address associated with your SendGrid account.
3. Generate the API key that acts as your password
SendGrid does not accept your account password over SMTP. The password field takes an API key you create: give the key a name, click Create Key, copy the value, and paste it into the Password field. Copy it immediately — SendGrid shows the full key exactly once, and if you lose it you have to generate a new one and update the integration.
4. Create the provider and make it your default
Click Create Provider, refresh the screen, and your SendGrid account appears in your integrations. Now do the step almost everyone forgets: select it as your default outbound email. Creating the provider stores the connection; setting the default is what actually reroutes your mail. Once it is set, everything the platform sends goes out through your connection — replies you type yourself, automated sends from the AI assistant, evergreen campaigns, and monthly Property Pulse equity reports.
Send yourself a test message and confirm it arrives from your own domain. That thirty-second check is the difference between "configured" and "working."
Authenticate Your Domain Before You Scale Volume
Connecting SMTP is the plumbing. Authentication is what earns you the inbox. Inside SendGrid, complete domain authentication so your mail is signed with DKIM and aligned for SPF, then publish a DMARC record for the domain. This is no longer optional at volume: Google's email sender guidelines require authentication, easy unsubscribe, and low spam-complaint rates from anyone sending in bulk to Gmail addresses, and Yahoo enforces comparable requirements. Most of a borrower database sits behind exactly those two providers.
Three habits keep an owned sending domain healthy:
- Warm up gradually. A brand-new sending domain that blasts 8,000 contacts on day one looks exactly like a spammer. Ramp volume over a couple of weeks, starting with your most engaged segment.
- Send to people who want it. Sort your list by engagement score and lead with the top of it. Engagement is the strongest positive signal a mailbox provider reads.
- Honor unsubscribes instantly and keep your list clean. Complaints and hard bounces do more damage than a missed send ever will. The FTC's CAN-SPAM compliance guide is the baseline, not the ceiling.
Why This Is a Mortgage Problem, Not an IT Problem
A mortgage database is a long game. The borrower you email today may refinance in 2028. The realtor you nurture may send four deals next spring. Everything about that model assumes your email keeps arriving for years — through a rate cycle, a brokerage change, a database that doubles in size.
Sending from a domain you own and authenticate makes that durable. It also makes your reporting honest: when your lead scores read email opens and clicks as engagement signals, those signals are only meaningful if delivery was real in the first place. A message that never reached the inbox looks identical to disinterest in the data — and it will quietly push a good borrower down your call list.
Team Deployment Notes
Because the integration is per user, a branch can standardize on SendGrid while keeping per-originator sending separation. Each loan officer generates their own API key, so keys can be rotated or revoked individually in SendGrid — useful when someone leaves the team — without interrupting anyone else's mail flow. If a connection ever fails, the cause is almost always one of two things: a mistyped username, or an API key that was regenerated in SendGrid after the integration was saved.
Where This Fits in the Stack
The SendGrid connection joins the rest of the platform's integration layer — LOS connections for ARIVE, Encompass, LendingPad, and Calyx, calendar and email sync, and Zapier. The principle behind all of them is the same: a mortgage-first CRM should slot into the systems you already run instead of asking you to abandon them, and the channels that carry borrower conversations should belong to you.
The Takeaway
Five minutes of setup: provider name, username from the SMTP Relay guide, smtp.sendgrid.net, a port, your SendGrid email, an API key as the password, Create Provider, then set it as your default. Authenticate the domain, warm it up, and lead with your engaged segment. The two-minute walkthrough is in the Academy — Connect SendGrid to LoanOfficer.ai, also published in Spanish. Setup questions go to support@loanofficer.ai. If you are not on the platform yet, you can see the whole feature set or try it for $1 for 14 days.
