> For the complete documentation index, see [llms.txt](https://docs.resifactory.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resifactory.net/the-console/signups.md).
# Signups
Signups answers "what are my mailboxes actually receiving?" It groups every message by **sender plus normalised subject**, so a thousand near-identical verification emails collapse into one row.
## How grouping works
Subjects are normalised before grouping — verification codes and order numbers are stripped out, so these three:
```
Your verification code is 481920
Your verification code is 203847
Your verification code is 771002
```
become one row reading `your verification code is`, with a count of 3.
Each row shows:
| Column | What it shows |
| ------------ | ---------------------------------------------------------------------------- |
| **From** | The sender address. |
| **Subject** | A real example, with the normalised form beside it. |
| **Accounts** | How many **distinct mailboxes** received it. This is the interesting number. |
| **Messages** | Total messages in the group. |
| **Latest** | When the most recent one arrived. |
{% hint style="success" %}
**Accounts is the number to read.** 400 messages across 3 mailboxes is one noisy service. 400 messages across 380 mailboxes means something happened to your whole set — a signup wave, or a mass notification.
{% endhint %}
## Categories
Tabs above the table sort the patterns by what they are:
| Tab | What lands here |
| ------------------------ | -------------------------------------------------------- |
| **All** | Every pattern. |
| **Orders / shipping** | Confirmations, dispatch notices, tracking, receipts. |
| **Raffle — Entered** | Entry confirmations. |
| **Account confirmation** | "Confirm your email", welcome mail, verification. |
| **Other** | Anything that did not match a category. |
| **Won / Successful** | Wins — "you've been selected", "invitation to purchase". |
Each tab shows its message count. **Empty categories do not appear**, so the tabs you see reflect what you actually receive.
Categories match on subject and sender text in several languages, so Japanese retail mail is categorised alongside English.
### The Won tab
**Won / Successful** is worth checking regularly — it is the one that means money. It lists individual winning messages rather than patterns, since each one matters on its own.
## Filtering
* **Filter by sender or subject** — narrows the patterns.
* **All batches** — restricts to one [batch](/the-console/batches.md).
* **Refresh** — recomputes.
## Drilling in
**Click a row** to open the [Inbox](/the-console/inbox.md) filtered to that exact pattern — every message from that sender with that subject shape, across every mailbox.
### Right-click a row
| Action | What it does |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Open in inbox** | Same as clicking. |
| **Copy ▸ From address / Sample subject / Normalized subject / Counts** | Copies that field. |
| **Copy matching / non-matching emails** | The mailbox addresses that did — or did not — receive this pattern. |
| **Filter inbox by sender only** | Everything from that sender, whatever the subject. |
| **Delete all messages in this cluster** | Permanently deletes every message in the group. |
{% hint style="danger" %}
**Delete all messages in this cluster** is permanent and can cover thousands of messages. The confirmation spells out how many messages across how many mailboxes. Read it before confirming.
{% endhint %}
### Copy matching / non-matching
This pairing is the most useful thing on the page. "Which of my mailboxes got the win email, and which did not?" — copy the non-matching list and you have exactly the set that needs attention.
## Scan all mailboxes
**Scan all mailboxes** runs a backfill across your mailboxes and re-reads what is there.
You do not normally need it — new mail flows in automatically within seconds. It is useful:
* After a first import, to catch mail that arrived before the mailboxes were added.
* After a period where you suspect mail was missed.
Progress is reported as it runs, and you can leave the page — the job continues and reattaches when you come back.
## Using Signups well
* **Check Won regularly.** It is the one that pays.
* **Watch the Accounts column** for anything that suddenly spans most of your mailboxes.
* **Use copy non-matching** to find the mailboxes that missed something.
* **Prune noise.** A newsletter that has generated tens of thousands of messages can be deleted in one action, which makes everything else easier to see.
---
# 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://docs.resifactory.net/the-console/signups.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.