Where the tickets
actually pile up.

Find your community in the first row. The second row is what your staff answers every day — and which system answers it with them.

A Discord with no game at all

Software, creators, hosting, study servers.

Integration depth1 / 3
  • Tickets & cited answers
  • Seven languages
  • Moderation & applications

A Minecraft server

Java, Bedrock or both.

Integration depth2 / 3
  • Live status
  • Bans & warns
  • Purchases verified

A FiveM roleplay server

The deepest integration.

Integration depth3 / 3
  • Admin-panel bans
  • Characters in the world
  • Bodycam

And these are
the tickets.

Each card names the system that handles it.

Ban appeals

Opens with the ban history attached.

Moderation

Whitelist

Form, review queue, auto-role, cooldown.

Applications

Payment disputes

Order verified, chargebacks visible, before any refund.

Game servers

Connection failures

The same five checks, walked through before a human.

Tickets and answers

In-game reports

A report command opens a ticket with position and logs.

Moderation

Lost property

Opens with the last session attached.

Game servers

Non-English scenes

One rulebook, players in any language.

Languages

Server networks

One bill, ten Discords, one knowledge base.

Tickets and answers

Raids and spam

A join wave or a flood in chat: throttled, verified, logged. No text stored.

Moderation

Admin voice disputes

A conversation on the record, with consent, reviewed against your rubric.

Bodycam

Characters in the world

A bartender who remembers you and keeps his secrets until the right name.

AI characters

The weekly read

What players asked that your rules could not answer — every Monday.

Tickets and answers

Your staff has answered that one forty times today.

Ten minutes to install. Unlimited tickets from the first one, and seven days of the full thing — on your rules, your players, your Discord.

LoginBook a setup call
FiveBot — who runs it, and what they get asked