Every message an alliance leader actually has to write, organised by the moment you
need it, and personalised with your state and tag without an account.
Open recruitment post
Recruitment · For state chat and the recruitment channels. Says what you are, not that you are the best.
[{tag}] {alliance} — State {state} — recruiting
What we are: an active alliance that runs every event together and expects you to show up for the ones you sign up for.
What we ask: join rallies when you are online, keep your alliance help topped up, and read the pinned notices.
What we do not ask: a minimum power, a screenshot of your account, or money.
If you are rebuilding after a rough SvS or you are new to the state, say so — we would rather help you catch up than turn you away.
Apply in game to [{tag}], or ask for {chief}.
Approach one player directly
Recruitment · When you have seen someone playing well in a solo alliance. Short, specific, no pressure.
Hi — {chief} from [{tag}] in State {state}.
I saw you at [event or place you noticed them] and you clearly know what you are doing. We are short of people who actually turn up for [the thing they are good at], and I would rather ask you directly than post another advert.
No pitch beyond that. If you are settled where you are, ignore this with no hard feelings. If you want to know what we are like before deciding, ask me anything.
First message to a new member
Welcome and onboarding · Send within the first few minutes. The first message decides whether they read the next one.
Welcome to {alliance}, and thanks for joining.
Three things and then I will leave you alone:
1. Alliance help — tap it whenever you see it. It costs you nothing and it is most of what makes an alliance faster than playing alone.
2. Rallies — join them when you are online. If you are not sure whether you are strong enough, join anyway and ask afterwards.
3. The pinned notices are where event calls go. Read them before an event, not during.
Ask questions in chat. Nobody here minds a beginner question and everyone minds a quiet member more.
— {chief}
Welcome back a returning player
Welcome and onboarding · For someone rejoining after a break. Different message from a new joiner, and usually sent to the wrong one.
Good to see you back in [{tag}].
What has changed since you were last on: [what changed]. What has not: [what is the same].
Do not try to catch up in a week. Pick one thing to rebuild first and tell me what it is, and I will point the alliance at it.
— {chief}
The pinned rules notice
Rules and expectations · The short version that lives in the pin. The long version belongs in the rules generator.
[{tag}] {alliance} — how we run
Show up: join rallies when you are online, and attend the events you signed up for.
Help: keep alliance help topped up. It is free and it is the whole point.
Talk: English in alliance chat so nobody is excluded. Any language you like in private.
Disagree: in private with {chief}, not in alliance chat.
Leaving: tell someone. We will not argue, and you are welcome back.
Inactivity: if you go quiet for [your window] with no word, we may free the slot. A message is all it takes to keep it.
The inactivity conversation
Rules and expectations · The message most leaders put off and then send badly. Private, specific, and it offers a way back.
Hi — this is not a telling-off.
You have been quiet for [how long] and I wanted to check you are alright before I do anything about the slot. Life happens and this is a game.
If you are coming back, just say so and I will hold it. If you would rather step away, say that too and I will take it as read that we part on good terms — you are welcome back whenever.
If I do not hear anything by [your date], I will free the place, and there is nothing personal in that.
— {chief}
Bear Hunt call
Event calls · Post before it opens, not while it is running. The point is that people plan their evening around it.
BEAR HUNT — [{tag}] — starts [time you have set]
Be online and in the alliance before it starts. Set your best squad before you join — a bad squad in a good rally still drags the whole score.
Rally leads: [names]. If you are not a lead, join a rally rather than starting one.
If you cannot make it, say so here beforehand so we do not hold slots for you.
SvS prep notice
Event calls · Sent well before the event, so people have time to bank what they are saving.
STATE OF POWER PREP — [{tag}]
Starting [when]. Between now and then:
- Bank what you are saving rather than spending it. Points are worth more inside the event than outside it.
- Do not start anything long that finishes during the wrong phase.
- Tell me now if you cannot be around for [the phase that matters to you], so I can plan without guessing.
Full phase details are on the state page, not in this message — check there rather than trusting a screenshot from another state.
— {chief}
Alliance Showdown roster call
Event calls · A roster call is a commitment, not a poll. Say what signing up means before people sign up.
ALLIANCE SHOWDOWN — roster for [{tag}]
Reply here if you want in. Signing up means you will be online for the matches, not that you would like to be.
I need to know: your usual online window, and whether you can be there at short notice.
If you are unsure, put yourself down as a reserve rather than not replying — a reserve who turns up is worth more than a starter who does not.
Short reminder, for the day itself
Event calls · One line. Long reminders on the day get skimmed and then ignored.
[{tag}] — [event] is on today, [time]. Be in the alliance and online. Squads set before you join.
Telling the alliance about a merge
Hard conversations · Say it before the rumour does. People forgive the decision far more easily than finding out sideways.
Announcement for {alliance}.
We are merging with [alliance]. Here is the honest reason: [reason].
What it means for you: [what changes]. What does not change: [what stays].
You are not obliged to come. If you would rather go elsewhere, tell me and I will help you land somewhere good rather than pretend to be offended.
Questions in private to {chief} — I would rather answer twenty of them than have anyone guessing.
Stepping someone down from R4
Hard conversations · Private, first, and never as a surprise in the rank list.
I am going to move you back from R4, and I wanted you to hear it from me first rather than see it.
The reason is [specific thing], not [what people will assume]. This is not about how much you play or how much you spend.
You keep your place in the alliance and nothing else changes. If you want the rank back, the route is [what would change your mind], and I mean that rather than saying it.
— {chief}
When the call was yours and it was wrong
Hard conversations · The rarest template on any site like this, and the one that keeps an alliance together.
That was my call and it was wrong.
[What happened.] I decided [what you decided] and it cost us [what it cost].
What I will do differently: [the specific change].
Nobody needs to reply to this. I would rather say it plainly than let it sit.
— {chief}
Introducing yourself to another alliance
Diplomacy · For the leader of an alliance you have not spoken to. Assume they are as tired of drama as you are.
Hello — {chief}, leader of [{tag}] in State {state}.
No proposal attached to this. I would rather know who you are before something happens that makes us talk in a hurry.
What we care about: [the two or three things]. What we do not get involved in: [what you avoid].
If there is anything currently annoying you about us, this is a good moment to say so.
What is different about these
There is a bigger template library than this one. It is on another Whiteout Survival site, it
holds well over a hundred entries, and most of them are chat art — decorative banners and framed
text. If that is what you want, go and get it; we are not going to pretend otherwise on our own
page.
These are a different thing. Every entry here is a message an R4 or R5 has to write because of
something that happened, not because a chat window looked plain: the inactivity conversation you
have been putting off, the merge announcement that has to land before the rumour does, the roster
call that says out loud what signing up commits you to, and the one nobody writes — the message
where the call was yours and it was wrong. Those are the messages that decide whether an alliance
holds together, and they are the ones that are hardest to write at eleven at night.
No numbers in any template, on purpose
You will not find a rally time, a point threshold, a power requirement or a cost in anything
above. Where a number belongs, there is a bracket for you to fill in.
That is a deliberate limit rather than an oversight. Game values change between updates, and a
template with a stale number baked into it does not look stale — it looks confident, gets pasted
into alliance chat, and is wrong in somebody else's window a week later. Numbers on this site come
from a checked ledger with the source and the read date attached, and they live on the pages that
can show that working. A template is not one of those pages. How we
verify explains the rule.
How the personalisation works, and where it stops
What you type in the bar at the top is stored in this browser and nowhere else. There is no
account, no sign-up, no server call and nothing to pay for — which also means it does not follow
you to your phone, and you will have to type it again there. That trade is stated here rather than
discovered later.
Unfilled values show as a visible placeholder like [TAG] instead of vanishing.
A template that silently drops a value is one you paste into chat with a hole in it.