> For the complete documentation index, see [llms.txt](https://spamrescue.gitbook.io/spamrescue-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spamrescue.gitbook.io/spamrescue-docs/what-is-spamrescue-and-how-it-works.md). # What Is SpamRescue and How It Works A clear walkthrough of what SpamRescue does, how the process works, and what it means for your inbox. ### What Is SpamRescue? [SpamRescue](https://spamrescue.com/) is an email intelligence platform built around a simple idea: spam filters make mistakes, and when they do, real emails disappear. A customer reply, a new lead, or a time sensitive message can land in a spam folder by accident and sit there unseen, because nobody has a reason to check a folder they were trained to ignore. SpamRescue does not replace your existing spam filter. It works alongside whatever filtering your email provider already runs, reviewing the results and catching legitimate messages that were wrongly placed in spam. Think of it as a second reviewer, one whose only job is to check the first reviewer's mistakes. ### The Problem It Solves Spam filters rely on signals rather than actually reading a message the way a person would. Sender reputation, domain age, authentication records, and writing patterns all factor into a filtering decision. Most of the time this works well, but none of these signals are perfect. * A new domain with little sending history can look unfamiliar to a filter, even if every email it sends is genuine. * A first time reply from someone who has never emailed you before can resemble an unsolicited message statistically, even though it is exactly the kind of email you want. * An unusual subject line on a legitimate message can accidentally trip the same filters built to catch bulk spam. None of these are rare edge cases. They happen constantly, and because filtering is silent, nobody is notified when it goes wrong. The sender assumes their message was received. The recipient never knows it was sent. That quiet gap between what was sent and what was actually read is the exact problem SpamRescue exists to close. ### How SpamRescue Works The process runs in three ongoing steps. #### 1. Scan Once an inbox is connected, SpamRescue continuously reviews messages that have already been filtered into spam. This is not a one time check. Scanning keeps running in the background as new mail arrives. #### 2. Score Every flagged message is scored based on how likely it is to be a genuine, wanted conversation rather than actual spam. This step matters because it prevents SpamRescue from simply pulling everything out of spam, which would defeat the purpose of filtering in the first place. Only messages that look legitimate are treated differently from everything else sitting in the folder. #### 3. Recover Messages that score as likely legitimate are surfaced back, so they can be reviewed and acted on before the opportunity attached to them passes. A full technical explanation of this process is available on the [how it works](https://spamrescue.com/how-it-works.php) page. ### Core Features at a Glance * **Continuous scanning** — spam folders are monitored on an ongoing basis, not checked once and forgotten. * **Scoring engine** — every flagged message gets a clear score, separating what deserves attention from what is safely ignored. * **Multi account support** — teams managing more than one inbox can protect all of them from a single place. * **Activity log** — every recovered message is recorded, creating a clear history of what was found and when. * **Adjustable sensitivity** — scoring can be tuned to be more cautious or more open, depending on how strict recovery needs to be. ### Who This Is Built For SpamRescue matters most for anyone who depends on email for real, one to one conversations rather than bulk marketing. A few examples: * Customer support teams replying to unfamiliar senders * Sales teams following up on new leads * Small business owners handling their own inbox * Newer or smaller domains without a long sending history Newer domains in particular tend to be treated with more caution by spam filters, simply because they lack an established history. That makes recovery tools more valuable, not less, for exactly the businesses that can least afford a missed conversation. ### Getting Started Setting up SpamRescue does not require changing anything about your existing email provider. The process is meant to stay simple: 1. Connect an inbox and authorize access. 2. Let the initial scan run against the existing spam folder. 3. Review whatever legitimate messages get surfaced. 4. Let scanning continue automatically in the background from that point forward. Businesses managing several inboxes, whether across departments, team members, or client accounts, can add and monitor each one from the same place, rather than relying on separate tools or manual checks per account. ### What to Check Before You Buy * Setup is designed to take minutes, not a lengthy onboarding process. * Pricing scales with account coverage, so it is worth comparing the [pricing page](https://spamrescue.com/pricing.php) against how many inboxes you plan to protect. * SpamRescue works alongside your current provider rather than requiring a switch. * Support is available through the [support page](https://spamrescue.com/support.php) for setup questions or unexpected scoring results. ### A Simple Scenario Consider a small consulting business that just landed a promising new client. The client replies to confirm a contract, using an email address the business has never received mail from before. To a rule based spam filter, this looks statistically similar to an unsolicited message: unfamiliar sender, no prior engagement history, first contact. The filter quietly routes it to spam. The business never sees the confirmation, assumes the client went quiet, and follows up days later, apologizing for a delay that was never actually theirs. With SpamRescue running, that same message gets scanned shortly after it lands in spam, scored as a likely legitimate reply based on its content and context, and surfaced back to the business the same day. The delay never happens, and the client never notices anything went wrong in the first place, because nothing did from their side. ### Without a Recovery Layer It is worth being direct about what happens in the absence of a tool like this. A missed email simply stays missed. There is no notification, no bounce message, and no signal to either party that anything went wrong. The sender assumes their message arrived. The recipient has no reason to manually search a folder they were trained to ignore. Over time, this creates a quiet, invisible gap between what was sent and what was actually read, one that grows larger the more a business relies on email to reach customers and leads. SpamRescue treats spam folders the way a careful business might treat any other process that could silently fail: worth checking on an ongoing basis, rather than trusted blindly once it is set up. ### Common Questions **Does it replace my spam filter?** No. It reviews what your existing filter has already set aside, rather than changing how incoming mail is filtered. **Will it flood my inbox with recovered spam?** No. The scoring system only surfaces messages that look genuinely legitimate, so actual spam stays where it belongs. **Does it cover multiple accounts?** Yes. Multiple inboxes can be connected and monitored from one place. **How much daily attention does it need?** Very little. Scanning runs continuously, and the activity log gives a clear record without requiring constant manual checking. ### The Bottom Line Spam filtering will never be perfect, and businesses that assume otherwise are the ones most likely to lose a conversation without ever knowing it happened. SpamRescue does not promise to eliminate spam. It promises to check the filter's work, catch what it got wrong, and hand back the messages that actually matter, quietly and continuously, before they turn into a missed customer or a lost lead. [Visit SpamRescue](https://spamrescue.com/) to see what your spam folder might be hiding. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://spamrescue.gitbook.io/spamrescue-docs/what-is-spamrescue-and-how-it-works.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.