Features

Everything your game needs. In one place.

Every Jum feature exists to remove one specific piece of manual admin — here's the problem each one actually solves.

Events

Scheduling & the basics

Problem: Event details get buried mid-chat, edited three times, and half the group misses the update.
Jum solution: One event record — date, time, venue, capacity, registration cut-off — that updates for everyone the moment it changes.
Benefit: Nobody shows up to the wrong pitch, or misses the change nobody saw in the chat.

RSVP

Who's actually coming

Problem: "I'm in" gets buried under fifty other messages, and the organiser is left manually counting replies.
Jum solution: A one-tap Going/Not going, a live headcount, and an automatic waitlist once the event is full.
Benefit: You know exactly who's coming, in real time — no manual tally required.

Team allocation

Fair sides, fast

Problem: Splitting a shifting headcount into fair teams five minutes before kickoff, by hand, every single week.
Jum solution: Auto-assign teams from confirmed attendees, adjust manually if needed, then publish the roster.
Benefit: Balanced teams without the last-minute scramble — and everyone can see which side they're on.

Expenses

Whoever paid, logs it

Problem: Someone always fronts the pitch fee or the drinks, and nobody remembers the exact amount by the time it's split.
Jum solution: Log an expense in seconds; an Admin approves it, and it's added to that event's total automatically.
Benefit: Costs are recorded when they happen, not reconstructed from memory afterward.

Settlement & payment tracking

Who owes who, clearly

Problem: The organiser ends up doing mental maths on who owes what, then chasing transfers one by one, then losing track of who's already paid.
Jum solution: Approved expenses are divided across the right attendees automatically — anyone excluded stays excluded — and each person's balance is marked paid once it's settled.
Benefit: No spreadsheet, no "did you get my transfer?" — just a shared, transparent ledger.

Event history

Nothing lost to scrollback

Problem: "Who came last month?" or "what did we end up paying for the last booking?" means scrolling back through months of chat.
Jum solution: Every past event, its attendees, teams and costs stay on record, searchable per community.
Benefit: A real answer in seconds, not an archaeology dig through group chat.

Community & group coordination

More than one game

Problem: Running more than one group means more than one chat, more than one set of rules, more than one everything.
Jum solution: Each community has its own members, roles, events and ledger — public and discoverable, or private and invite-only, your call.
Benefit: One account, every group you organise or play in, cleanly separated.

Notifications

Only when it matters

Problem: Group chat notifications are either constant noise or so easy to mute that you miss the one that mattered.
Jum solution: Targeted alerts — a spot opened up, teams were published, it's time to settle — with per-category controls over what you get notified about.
Benefit: You hear about what's relevant to you, not everything happening in the group.

Organiser tools

Built for the person running it

Problem: The organiser role is invisible work — approvals, reminders, exclusions, and a dozen small judgment calls, all unpaid and unthanked.
Jum solution: A dedicated Admin view for approving expenses, managing the waitlist, excluding a guest from a split, and publishing settlement — one action list, not five screens.
Benefit: Running the group takes minutes, not an evening.

Ready to Jum?

See it in context, from the first invite to the last settlement.

Walk through the flow Get Jum