Make your follow-up emails land in inboxes.
Your CRM sends the follow-up emails that turn an enquiry into a booked call. For those to reach the inbox instead of the spam folder, we need permission to send as you. There are two ways to do that. One takes a minute and needs only you. The other takes a few days and needs your web partner. Start with the first.
Before either option, one quick answer
Tell us the exact email address you want leads to hear from. Not roughly, exactly. If your business uses more than one domain, we need the one you actually send from day to day. Getting this wrong is the most common cause of follow-up emails going missing, and it stays invisible until someone tells you they never heard back.
Option A · Connect your mailbox 1 minute · recommended
If you are on Microsoft 365 or Outlook, or on Google Workspace or Gmail, this is the whole step. You approve once, your emails go out through your real mailbox which is already trusted, and there is nothing to configure and nobody to chase.
- In your CRM go to Settings, then Email Services
- Choose to connect your mailbox and pick Microsoft or Google
- Sign in with the address you gave us above and accept
That is it. No DNS, no web partner, no waiting. If you connected Outlook or Google in Step 3 for your calendar you are most of the way there, though email is a separate approval and still needs doing.
Option B · Dedicated sending domain a few days · we handle it
If your email is not on Microsoft or Google, or you would rather keep automated sending completely separate from your normal mailbox, we set up a dedicated sending sub-domain instead, typically mail.yourdomain.com.
- We generate the records (a CNAME plus SPF, DKIM and DMARC) inside your CRM
- We email your web partner the exact strings to paste in. You are copied but need do nothing
- Your CRM verifies automatically once they are live and this step ticks green
What we need from you: the email address of whoever manages your website DNS. If that is you, say so and we will send the records straight to you with a walkthrough for your registrar.
Do not let this step be the thing that delays your launch
Option B depends on a third party replying, and that is where onboarding most often stalls for weeks. If you are on Microsoft or Google, do Option A today and we can go live without ever touching your DNS. The dedicated domain can always be added later.
Self-check tool
Loading DNS checker...
Only relevant if you are doing Option B.
Common questions on this step
Which option should I pick?
If your work email is Microsoft 365, Outlook, Google Workspace or Gmail, pick Option A. It is faster, it needs nobody but you, and deliverability is better from day one because you are sending through a mailbox that already has a reputation. Pick Option B only if you are on something else, or if you send at a volume where you want automated mail kept separate.
If I connect my mailbox, can the CRM read my email?
The connection is for sending, and for threading replies from leads so they land in your CRM conversation instead of getting lost. It is not there for us to browse your inbox and we do not. If it still sits badly with you, Option B keeps automated sending entirely separate from your mailbox and is the cleaner answer.
Will automated emails damage my normal email reputation?
At the volume a Decision Maker Pipeline sends, following up on your own enquiries, no. These are people who asked to hear from you. The reputation advice you may have read is about cold outbound at scale, which is a different activity. If you ever move to that, we set up a separate sending domain for it.
Will this change how my regular email works?
No, on either option. Option A adds permission for the CRM to send as you and changes nothing about your inbox. Option B adds records for a sub-domain that does not exist today, so [email protected] is untouched.
My web partner is taking forever to respond.
Switch to Option A if you can and stop waiting on them. If you genuinely need Option B, forward us their last reply, or their silence, and we will escalate with a templated chaser. Past five working days we will suggest moving your DNS to Cloudflare, which removes this bottleneck permanently.
Records were added but the step still is not green.
Almost always a typo, usually a missing trailing dot or a misspelt DKIM selector. Send a screenshot of what was entered at the DNS panel and we will spot it in seconds. It is also worth waiting a few hours before assuming it failed, because DNS takes time to spread.
More FAQs in the full FAQ section.