> 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/best-practices-to-keep-your-emails-out-of-spam.md). # Best Practices to Keep Your Emails Out of Spam ### **Start with Engaged Contacts** Email providers prioritize engagement.Begin by sending emails to people who have: * Opened your emails recently * Clicked links * Replied or interacted with you Avoid sending to large, cold audiences right away. ### **Warm Up Your Email Sending** New domains and new sending behavior require time to build trust.Start small: * Send to 10–25 contacts * Gradually increase volume over time * Focus on quality over quantity ### **Focus on Replies (Most Important Signal)** Replies are one of the strongest positive signals you can send.Try asking simple questions like: * “Are you currently looking to buy or just browsing?” Even a short reply helps improve your sender reputation. ### **Keep Emails Simple and Natural** Avoid: * ALL CAPS * Excessive punctuation (!!!) * Image-only emails * Too many links * Spam trigger phrases Instead: * Write like a normal conversation * Keep formatting clean * Include your contact details ### **Get Permission Before Sending** Before sending marketing emails: * Interact via call, text, or in person * Let them know you’ll follow up via email * Ask them to save your contact This helps email providers recognize you as a trusted sender. ### **Maintain a Healthy Contact List** * Remove inactive contacts regularly * Avoid purchased or third-party lists * Monitor unsubscribes and bounces * Segment your audience based on engagement --- # 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/best-practices-to-keep-your-emails-out-of-spam.md?ask=&goal= ``` `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.