Saltearse al contenido
Furbol — How It Works

Cancelling a Game

Esta página aún no está disponible en tu idioma.

Cancelling a Game

This page walks through calling off a game you’re hosting — the taps, what the screen does, and what reaches the players. The rules behind it (who can cancel, what it refunds, when Furbol cancels for you) live on Cancelling a Game (rules).

1. Find the Cancel button

Open the game. In the top-right of the game detail page, tap the three-dot overflow menu.

Among the entries you see as the host — share, report, EDIT GAME, CANCEL GAME — tap CANCEL GAME.

If you’re not the host, the CANCEL GAME row isn’t there. The overflow still shows share and report, but the host-only entries are hidden.

If the game has moved past the feedback window into its results stage, the host entries disappear for the host too — the overflow goes back to the read-only shape. No way to cancel from that point.

2. What happens when you tap

Nothing in between. There’s no “Are you sure you want to cancel?” confirmation dialog. The tap is the commit.

Practically, this means:

  • The cancellation fires immediately.
  • The game detail panel collapses.
  • You’re returned to the games list.
  • The game now shows as cancelled in the list (it doesn’t disappear — the record stays, just marked).
  • No success snackbar at the top. The navigation-back is the confirmation.

Because there’s no dialog, the button itself is the entire flow. If you tapped by mistake, you’re already done — cancelling is a single tap past the overflow.

3. What reaches the players

Everyone on the lineup sees the following:

  • A push notification: “The host cancelled the game.” (Subject to their per-game mute and notification preferences — see Notification Preferences.)
  • They’re unbooked. The game no longer appears in their Playing list.
  • For online-paid games, their wallet hold releases — the pending fee flips back to available balance.
  • The game’s activity log gets a “the host cancelled the game” entry, visible if they open the game’s history.

There’s no message from you attached to the cancellation — Furbol doesn’t collect a reason, and players don’t see one. If you want the players to know why you cancelled, you need to tell them yourself outside the app (group chat, message on the game before you cancel, etc.).

4. The button at different points in the game’s timeline

Because the overflow menu changes shape as the game moves through its stages:

Before kickoff

CANCEL GAME visible in the overflow. Normal flow.

During the game (kickoff to scheduled finish)

Still visible. Rare but supported — e.g., a pitch becomes unplayable mid-match.

During the feedback window (up to 3 hours after the scheduled finish)

Still visible. You can use this to wipe a game that didn’t really happen.

After the feedback window (results stage)

CANCEL GAME is gone from the overflow. The game is locked — ratings, results, activity log all frozen. Nothing you can do from here.

5. What you won’t see in this flow today

Worth naming:

  • No confirmation dialog. One tap past the overflow and it’s done. People used to “Are you sure?” in other apps are the ones most likely to be caught out.
  • No reason field, no optional message. The cancellation is a pure signal — “this game is off”. If you need to explain, that’s on you to do separately.
  • No success toast. The app quietly collapses the game panel and returns you to the list. The game appearing as cancelled in the list is the only visible confirmation.
  • No undo. Cancelled means cancelled; there’s no “bring it back”. If you wanted the game to still happen, create a new one.