> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/email-deliverability/deliverability-health-checklist.md).

# Deliverability Health Checklist

### **1. Domain & Setup (Foundation)**

* [ ] My domain shows as **Authenticated** in Rechat
* [ ] DNS records (SPF, DKIM, DMARC) are properly set up
* [ ] I am sending from a professional domain (not @gmail.com, etc.)

{% hint style="info" %}
*If this section is incomplete, fix this first. Nothing else matters until this is done.*
{% endhint %}

### **2. Sending Behavior (Reputation Building)**

* [ ] I send emails consistently (not large, random blasts)
* [ ] I gradually increased my sending volume over time
* [ ] I started with small groups before scaling

{% hint style="info" %}
*Sudden spikes in sending volume are one of the fastest ways to trigger spam filters.*
{% endhint %}

### **3. Audience Quality (Who You’re Sending To)**

* [ ] I send primarily to contacts who know me
* [ ] My contacts have engaged (opened, clicked, or replied) recently
* [ ] I regularly remove inactive contacts
* [ ] I do NOT use purchased or third-party lists

{% hint style="info" %}
*Bad lists = bad reputation. Every time.*
{% endhint %}

### **4. Engagement Signals (Most Important)**

* [ ] My emails receive replies
* [ ] My open rates are consistent or improving
* [ ] My contacts click links in my emails
* [ ] I occasionally ask simple questions to encourage replies

{% hint style="info" %}
*Replies are the strongest positive signal you can send to email providers.*
{% endhint %}

### **5. Email Content (Spam-Safe Formatting)**

* [ ] My emails feel personal and conversational
* [ ] I avoid ALL CAPS and excessive punctuation
* [ ] I don’t overload emails with links or images
* [ ] I include my name, contact info, and (when applicable) office address

{% hint style="info" %}
*If your email looks like an ad, it may be treated like one.*
{% endhint %}

### **6. Warm-Up & New Activity**

* [ ] I started sending to my most engaged contacts first
* [ ] I increased volume gradually over time
* [ ] I avoided sending large campaigns immediately

{% hint style="info" %}
*This is especially important if you’re new to Rechat or recently switched platforms.*
{% endhint %}

### **7. Contact Awareness (Trust Signals)**

* [ ] I’ve spoken to or interacted with my contacts before emailing
* [ ] I let contacts know they’ll be hearing from me
* [ ] I’ve asked contacts to save my email or reply

{% hint style="info" %}
*Email works best when it follows a real relationship—not replaces it.*
{% endhint %}

### **8. Monitoring & Adjusting**

* [ ] I review open rates, clicks, and unsubscribes
* [ ] I adjust my audience if engagement drops
* [ ] I test emails before sending large campaigns

{% hint style="info" %}
*Low engagement is an early warning sign—don’t ignore it.*
{% endhint %}

## **Your Deliverability Score**

Give yourself 1 point for each checked item:

* [ ] **22–24 points:** 🟢 Excellent — You’re in great shape
* [ ] **18–21 points:** 🟡 Good — Some room to improve
* [ ] **12–17 points:** 🟠 At Risk — Likely impacting deliverability
* [ ] **Below 12:** 🔴 Needs Attention — High risk of spam placement

## **If You’re Struggling with Deliverability**

Start here:

1. Send a simple email to 10–20 people who know you
2. Ask a question to encourage replies
3. Pause large campaigns
4. Clean your contact list

Then gradually rebuild from there.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rechat.com/guides/marketing/email-deliverability/deliverability-health-checklist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.