Discord partnership application template
Stop answering “hey, partner?” in your DMs. Publish your requirements, ask these questions once, and compare requests side by side.
- Free plan
- Free Premium trial
The template
The first seven are the questions of the Partnership request template in Toscio.
- Your server or project name
- Invite link or website
- Member count
- Describe your server
- What do you offer?
- Your role on that server
- Anything else?
More questions for a serious partner program:
- How many members are active on a normal day?
- What do you expect from us in return?
- How long has your server been running?
- Do you already partner with similar servers?
- Are you the owner? If not, who approved this request?
- Which channel will our partnership appear in?
- Do you have rules on advertising or NSFW content?
- Who should we contact if something goes wrong?
Why each question
| # | What it tells you |
|---|---|
| 1, 2 | The basics. A permanent link matters: an invite that expires breaks your partner list. |
| 3, 8 | Size and real activity. Compare the two: 5,000 members and a quiet chat tells a story. |
| 4 | If the audience overlaps with yours. No overlap means no value for either side. |
| 5, 9 | The deal itself. Vague offers such as "promo" usually mean nothing happens. |
| 6, 12 | If the person can commit. Helpers often apply without asking their owner. |
| 10 | Stability. A two-week-old server may not be there next month. |
| 11 | Whether it's a partner mill: a server with 200 partners gives you very little. |
| 13 | Where you'll really appear. Buried channels don't bring anyone. |
| 14 | Reputation risk. You're putting your name next to theirs. |
| 15 | A real contact, for the day something breaks. |
| 7 | Room for anything the form missed. |
Requirements to publish
Good requests start with clear rules. Post something like this next to your form, and fewer bad ones will arrive:
- At least [500] members and regular activity
- A clear theme that fits ours, and rules that follow Discord's terms
- No NSFW content, no paid server-boost exchanges, no giveaways with entry fees
- A partner channel on both sides, or a joint event
- One post each, updated at most once a month
- Either side can end the partnership with [7] days' notice
Red flags
- A server that looks full but has an empty chat. Open the invite and read the last day of messages before accepting.
- A copied description that doesn't mention your server at all.
- A requester who isn't staff there. Ask who approved it.
- Pressure. "We need an answer today" is never a good sign.
- A huge list of partners. Your post will be one of many, and nobody will read it.
What to send after a yes
A good acceptance message says what happens next, in order: where to post, what text to use, who to contact. Put your ad text in it, so that the partner doesn't have to ask. Then check a week later that both sides have done their part.
Use it in Discord
Most requesters aren't on your server, so the web form open to non-members works better here than a panel: a link on your website is enough, and accepted partners join with @Partner. Your team reads every request in a staff channel, and answers with a preset reason when it's a no. See the partnership requests page and the rejection messages. Toscio doesn't check member counts or activity for you: that part stays with your team.
Questions
What member count should I require for a partnership?
There's no standard number. Pick a floor based on what you'd offer in return, and judge activity rather than size: a small active server is often a better partner than a large silent one.
Should partnerships be mutual?
Usually, yes. Write down exactly what each side does, such as a post, a channel or a joint event, so that nobody feels short-changed later.
How do I end a partnership?
Tell the other owner first, remove their role and their post, then update your partner list. A clause in your requirements makes this much easier.
