Email sending and domains
How InsightHire sends email for your organization, how to connect your own SMTP or email provider, and how to verify your sending domain.
InsightHire already sends email for you. Candidates get invitations, reminders and updates from InsightHire's mail service with your organization's name on them, and you don't have to set anything up.
Connect your own email only if you want messages to come from your own domain, such as jobs@yourcompany.com.
Everything here lives on Settings → Email settings, on the page called Email sending.
Who can do what
- Organization Admins connect or change the sending setup, run tests, add and verify domains, add team senders and set up enterprise mailbox grants.
- Everyone on the hiring team can open the page, see how email is being sent, and read the email logs.
- Everyone can connect their own personal mailbox. See Send from your own mailbox.
Your options
There are four ways mail can leave InsightHire. When more than one is set up, the first that applies is used:
- Enterprise mailbox grant. Your Google Workspace or Microsoft 365 admin lets InsightHire send as any address on your domain. See Shared and enterprise mailboxes.
- Your own mailbox. Messages you send personally go out through your connected Gmail or Microsoft 365 account. See Send from your own mailbox.
- Your own SMTP or email provider, described below.
- InsightHire's mail service, the default.
The top of the Email sending page tells you which one is in use. If an older setup has been replaced by a higher one, it shows as Legacy configuration marked Not in use, and you can remove it safely.
Connect your own SMTP or email provider
- Open Settings → Email settings and choose Connect your own email.
- The page offers Connect my Gmail and Connect my Outlook mailbox first. Those connect your own personal mailbox, not an organization-wide sender.
- For an organization-wide sender, choose Show advanced options under Advanced: SMTP or API provider.
- Pick your provider: SMTP Server, SendGrid, Mailgun, Resend, Amazon SES, Postmark or SparkPost.
- Fill in From Email, From Name and, optionally, Reply To Email.
- Fill in the connection details for your provider:
- SMTP Server: SMTP Host, SMTP Port, SMTP Username, SMTP Password, and whether to Use SSL/TLS or Require TLS.
- API providers: the API Key, plus an API Secret and AWS Region for Amazon SES, or the Mailgun Domain for Mailgun.
- Choose Create Configuration.
Once saved, the Email Configuration card shows your From address, From name, Reply-To and the last test result. Choose Test Configuration to check the connection, and Edit Configuration to change it.
Details to ask IT for
- Host: the mail server name, such as
smtp.office365.com. - Port: usually 587 for STARTTLS or 465 for SSL. Use the value your provider gives you.
- Username: often the full sending email address.
- Password: ideally an app password or a dedicated SMTP credential, not someone's normal password.
- Security: whether the provider wants STARTTLS or SSL.
- From address: an address your provider allows you to send as.
Never put SMTP passwords in tickets, shared documents or spreadsheets. Rotate a credential straight away if it is exposed.
Verify your sending domain
Verifying your domain tells receiving mail systems that InsightHire is allowed to send for it, so your mail lands in the inbox, not spam. You need a saved email configuration first. Team sender addresses also need a verified domain.
- On Settings → Email settings, choose Manage Domains.
- Choose Add Domain, enter the Domain Name, and add it.
- Choose Show DNS Records and copy the records into your domain's DNS. Whoever manages your domain, often IT, will need to do this.
- Wait for DNS to update. This usually takes 5 to 30 minutes.
- Choose Verify.
InsightHire looks up your real DNS records and shows each check as Verified or Pending:
- SPF: says which servers may send for your domain.
- DKIM: signs your mail so it can't be tampered with.
- DMARC: tells receivers what to do when a check fails.
The domain is verified once SPF and DKIM both pass. DMARC is shown but not required to send. Setting it up is still good practice.
Team senders, shared and enterprise mailboxes
Once your domain is verified, you can send from named addresses such as talent@company.com or offers@company.com without a separate setup for each. See Team sender addresses.
To have those messages land in a real shared mailbox's Sent folder, or to let InsightHire send as anyone on your Google Workspace or Microsoft 365 domain, see Shared and enterprise mailboxes.
Check what was sent
Open Hiring → Email plan, choose the Settings tab, then Email logs. Each email shows its status: Pending, Queued, Sending, Sent, Delivered, Opened, Clicked, Bounced, Complained, Failed or Blocked. Expand a row for the sender, the times and any error details.
Filter by how mail went out: All sends, Platform SMTP or OAuth shared inbox.
When your own SMTP or provider is in use, the Email sending page also shows Usage & Limits (daily and monthly usage) and Email Statistics (sent, delivered, opened, clicked, and open, click and bounce rates).
Troubleshooting
Authentication failed
Check the username and password, whether your provider needs an app password, and whether SMTP sending is switched on for that account.
The connection times out
Check the host and port. Ask IT whether a firewall blocks outbound mail, and whether the provider expects STARTTLS on 587 or SSL on 465.
Messages go to spam
Verify the domain (SPF and DKIM), make sure the From address is allowed by your provider, and avoid sending large volumes straight away from a new domain or account.
A check stays Pending
DNS can take a while to update. Check the record was added exactly as shown, on the right name, then choose Verify again later.
Related
Outbound webhooks
Send signed InsightHire events, such as new applications, finished journeys and offer decisions, to an HTTPS endpoint your organization controls.
Team sender addresses
Send from addresses like talent@, interviews@ and offers@ on your verified domain, and pick a sender per email template.
