Skip to main content
WORKSPACE EMAIL

Get a properly-authenticated sending domain in minutes — ParsaLink talks to AWS SES on your behalf and gives you the DNS records to paste into your registrar.

​
Why a Dedicated Domain?

Sending from a properly-authenticated custom domain (SPF + DKIM + DMARC) is the single biggest factor in landing inboxes instead of spam folders. Sending from a shared address — or from a personal Gmail without DKIM — drags your deliverability down even when the content is perfect. ParsaLink’s workspace email setup gets you:
  • A subdomain dedicated to your workspace (e.g. yourco-stg.parsalink.io or yourco.parsalink.io)
  • SES verification + DKIM record generation handled automatically
  • A parsa-assistant@<your-subdomain> address you can CC or forward to so the CRM captures the conversation
  • Per-tenant sending reputation — your team’s email behavior doesn’t get tainted by another tenant’s bad list hygiene

​
Setting It Up

1

Open Workspace Email

Go to Settings → Workspace Email.
2

Pick or auto-provision a subdomain

Most workspaces use the auto-provisioned subdomain (one click). If you’d rather use your own domain (e.g. mail.yourco.com), enter it here.
3

Verify the domain in SES

ParsaLink calls AWS SES and creates the verification token, then shows you the DNS records to paste into your registrar (TXT for verification + three CNAMEs for DKIM).
4

Paste the DNS records

Add the records exactly as shown to your DNS provider (Cloudflare, GoDaddy, Route 53, etc.). Most propagate within 5–15 minutes.
5

Click Verify

ParsaLink polls SES until verification succeeds. You can leave the page and come back — verification status persists.
6

Send a test

Click Send Test Email to confirm everything’s wired through. The test goes to your account email, signed by your new subdomain.
If your DNS is managed by Cloudflare and you’ve added an API token to Settings → Integrations → Cloudflare, ParsaLink can push the DKIM records into Cloudflare for you. One less manual step.

​
Sending Addresses

Once the domain is verified, you can spin up multiple sending addresses on it (one per team member, or per campaign): [email protected], [email protected], etc. Manage them at Settings → Workspace Email → Sending Addresses. Each address can be configured with:
  • A display name (the “From” name recipients see)
  • A default footer
  • A reply-to address (if you want replies to go to a shared inbox)

​
Inbound Capture

The big payoff of workspace email is the dedicated inbound address — typically parsa-assistant@<your-subdomain>. Anything sent to that address is captured by SES, parsed for the contact email, matched to a CRM record, and logged on the contact’s timeline. Common workflows:
  • CC the assistant on outbound mail — paste it into your BCC field and the conversation lands on the contact’s record.
  • Forward replies — forward any inbound reply to the assistant address and the reply gets logged.
  • Reply to a digest — the daily digest’s reply-to address is the assistant; replies route to the CRM AI agent under your identity.
ParsaLink never reads your personal inbox — every inbound capture is opt-in via this address.

​
Configuration Set (Engagement Events)

If your SES sub-account is wired up with a Configuration Set (delivery / bounce / complaint / open / click event publishing), set the configuration set name at Settings → Workspace Email → Advanced. ParsaLink stamps X-SES-CONFIGURATION-SET on outbound mail and routes the resulting events into Email Tracking.