Set Up Your Company Email Address
Configure your company email for sending from JobsiteOn, including email verification, DNS setup for SPF and DKIM records.
Configure your company email for sending from JobsiteOn, including email verification, DNS setup for SPF and DKIM records.
This guide walks you through setting up your company email address in JobsiteOn so you can send and receive emails through the inbox. You will learn how to add your email address, verify your domain ownership, configure DNS records for reliable delivery, and test that everything works correctly.
By the end of this guide you will have:
Before starting the email setup process, gather the following:
office@yourcompany.com or info@yourcompany.comNote: If you do not manage your company's DNS records yourself, you may need to involve your IT administrator or the person who manages your domain. The DNS records you will need to add are standard email authentication records.
This is where you manage your sending email address and domain authentication.
office@yourcompany.com)Tip: Choose a professional, general-purpose email address rather than a personal one. Addresses like
office@,info@, orhello@work well because they represent your company rather than an individual. If a team member leaves, you will not need to change anything.
Here are common patterns:
| Address | Best for |
|---|---|
office@yourcompany.com |
General business communication |
info@yourcompany.com |
Customer inquiries |
service@yourcompany.com |
Service-related conversations |
hello@yourcompany.com |
Friendly, approachable tone |
Avoid using personal email addresses like mike@yourcompany.com because all team members send from this single address.
After adding your email address, JobsiteOn needs to verify that you own it. The verification process depends on your setup:
JobsiteOn sends a verification email to the address you entered. Open that email and click the verification link. This confirms that you have access to the email account.
Note: The verification email is valid for 24 hours. If it expires, you can request a new verification email from the settings page.
DNS records are how the email ecosystem verifies that you have authorized JobsiteOn to send email on behalf of your domain. Without proper DNS records, your emails may land in spam folders or be rejected entirely.
You need to add two types of records: SPF and DKIM.
SPF tells receiving email servers which mail servers are authorized to send email for your domain. When a customer's email provider receives an email from office@yourcompany.com, it checks your domain's SPF record to verify that the sending server is authorized.
| Field | Value |
|---|---|
| Type | TXT |
| Host/Name | @ (or your domain name) |
| Value | The SPF value shown in your JobsiteOn email settings |
| TTL | 3600 (or default) |
If you already have an existing SPF record for your domain (this is common if you use Google Workspace, Microsoft 365, or another email service), you need to merge the new include statement into your existing record rather than creating a second SPF record.
For example, if your existing SPF record is:
v=spf1 include:_spf.google.com ~all
And JobsiteOn asks you to add include:mail.jobsiteon.com, your merged record would be:
v=spf1 include:_spf.google.com include:mail.jobsiteon.com ~all
Tip: You can only have one SPF record per domain. Having multiple SPF records causes authentication to fail. Always merge rather than creating a second record.
DKIM adds a digital signature to every email sent on your behalf. The receiving email server uses your domain's public key (published in DNS) to verify that the email was not tampered with in transit and that it was authorized by your domain.
| Field | Value |
|---|---|
| Type | CNAME |
| Host/Name | The selector value shown in JobsiteOn (e.g., jobsiteon._domainkey) |
| Value/Target | The CNAME target value shown in JobsiteOn |
| TTL | 3600 (or default) |
After adding both records, they need to propagate across the global DNS system. This typically takes:
You can proceed with other setup tasks while waiting for propagation.
Note: Do not worry if verification does not succeed immediately after adding DNS records. Wait at least 30 minutes before troubleshooting, and up to a few hours for slower DNS providers.
Once you have added the DNS records and waited for propagation:
The verification status for each record shows:
If both records show as Verified, your email setup is complete.
If a record shows as Failed:
v=spf1 prefix and one ~all suffixWith DNS records verified, it is time to test that your emails actually reach customer inboxes without issues.
When you receive the test email in your personal inbox, verify:
For a more thorough check, open the email headers (this is usually in the "Show original" or "View source" option in your email client). Look for:
Tip: Send test emails to multiple email providers (Gmail, Outlook, Yahoo) since each provider has slightly different spam filtering. If your email passes Gmail and Outlook, you are in good shape for the vast majority of customers.
With the technical setup complete, review your sending preferences:
The display name appears in the "From" field of your emails. Make sure it is:
By default, replies go to the same address you send from. If you want replies directed to a different address, configure the reply-to setting here.
Consider setting up a default email signature that appears at the bottom of all outbound emails. A good signature includes:
If your test emails or customer emails are going to spam folders:
p=reject while still configuring your recordsIf records still show as Pending or Failed after 48 hours:
This means the email verification step (Step 3) was not completed. Check the inbox of your company email address for the verification email. If it expired, go back to Settings and request a new verification email.
It is technically possible but strongly discouraged. Free email domains have shared SPF and DKIM records that you cannot modify. This means your emails are more likely to be flagged as spam or rejected. Use a custom domain email address for professional communication.
This depends on your plan. Check your workspace settings to see if multiple sending addresses are supported. In most cases, a single company-wide sending address is recommended for consistency.
DMARC is an additional layer of email authentication that builds on SPF and DKIM. While not required for JobsiteOn to send email, setting up a DMARC policy improves your overall email deliverability and protects against spoofing. If your domain already has a DMARC record, make sure it does not conflict with JobsiteOn's sending.
You can update your sending address at any time by returning to the email settings. You will need to reverify the new address and may need to update DNS records if the domain changes. Existing conversations remain intact -- they are not affected by the email address change.
Did this answer your question?