> For the complete documentation index, see [llms.txt](https://superwave.gitbook.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://superwave.gitbook.io/manual/superwave-users-manual/3.-generating-your-inboxes.md).

# 3. Generating your inboxes

***

### Get Started:

1. Go to [Email Permutator: Find Anyone Email Address for Free (mailmeteor.com)](https://mailmeteor.com/email-permutator) and generate **up to 99** versions of your names. \
   \
   If you are splitting it between three “Sales persons” you only need 33 for each. \
   \
   (Tip: If you need more variations, you can remove one or two letters from the first name, last name in different instances to have more combinations of the name in question).

<figure><img src="/files/t7WcuL6NDrFMZOCG2mzx" alt="" width="563"><figcaption></figcaption></figure>

***

2. For each domain, create a new spreadsheet and type "DisplayName" & "EmailAddress" as shown onto the A & B columns of Row 1 respectively.\
   \
   The custom name spreadsheet should be structured as shown in the image below. \
   \
   Remember, **no spaces** in the header titles so our systems can recognize the file.\
   The headers must be formatted EXACTLY as shown.\
   \
   Repeat Step 1 & 2 for all the domains you'd like to onboard with us, then move on to Step 3.

<figure><img src="/files/Fesfa45k5MzvfaXCdgxd" alt="" width="301"><figcaption><p>An example of how your Email Permutation Sheet<br>should look like</p></figcaption></figure>

* Each domain must have it's own permutation sheet, do **not** add the permutations of multiple domains into one sheet.
* Do not send Google doc links with the permutation information, Step 3 explains what to do once you've generated permutations for each of your domains.

***

3. Once you have your addresses ready, you now must:\
   \
   Export each domain's permutation spreadsheet as a ***.CSV*** file.\
   \
   Name each ***.CSV*** file the name of it's corresponding domain, here's a comparison example:

<figure><img src="/files/skHedftNADiDVbPkZeEg" alt=""><figcaption><p>This is how your permutation CSV files should look like if you followed our guide correctly.<br>domain.com.csv <span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span>                     superwave - inboxes .csv <span data-gb-custom-inline data-tag="emoji" data-code="274c">❌</span></p></figcaption></figure>

Drop the finished permutations files into your designated Superwave Slack channel.

***

### Benefits:

* No need to create a password as the code will create it for you.
* You can now have a single “Sales person” up to 99 times.
* You can also split the 99 users into multiple people if you wish (Ricky, Hannah, Ashley, whatever you want).

### **Limitations:**

* Some names aren’t able to produce 99 combinations of itself (Example: Bob only has 3 possible mathematical combinations). This means you have to be more creative when naming.
* While you are allowed to issue less than 99 inboxes, doing so just means you're leaving potential reach on the table with that domain.

### Repeated addresses:

You can’t have the same address 99 times (Example: *tommy\@domain* can’t exist 99 times, but *t\@domain, tom\@domain, tommy\@domain*, etc can).

If your user sheet has repeated addresses, or domains in a single server have the same address prefixes, like this:

```
robert@domain1.com
robert@domain2.com
robert@domain3.com
```

Then the system will automatically correct the sheet to keep addresses unique, like this:

```
robert.a@domain1.com
robert.b@domain2.com
robert.b@domain3.com
```

It appends a letter in alphabetic format as many times as needed. In an exaggerated scenario you might get something like this:

```
robert.zzz@domain.com
```

**All servers run three domains each**, so if you don't want appendages in your user sheets **you must spin up as many unique prefixes as possible**, which could include having more "SDR names" in your user sheets.

***

### Bonus: Creating female SDRs

It is well-known in this industry that women get higher open rates and more positive reception from niches and markets.

If you visit [this Google Colab script runner](https://colab.research.google.com/drive/16qEkncssjxK_IjsKkZAnV2j2wdhKQydn?usp=sharing) you can generate up to 99 female names in the proper format for your convenience. The script uses a database of thousands of girl names and a wide range of last names from all corners of the world so not two addresses are the same.

<figure><img src="/files/9OFJxONlsK4wTSThwhyX" alt=""><figcaption></figcaption></figure>

Once the script is ran, you'll be able to download your list this way by clicking on the three dots next to the .csv file with your domain as filename:

<figure><img src="/files/oLlu5HHkP4ROJkDdd3Je" alt=""><figcaption></figcaption></figure>

Your new **.csv** file is ready to be submitted to Superwave through your assigned Slack channel.


---

# 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://superwave.gitbook.io/manual/superwave-users-manual/3.-generating-your-inboxes.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.
