In a London room running two sittings, the whole margin sits in how fast the first table settles. Catching a server's eye, waiting for the card machine, then splitting six ways can take fifteen minutes of a table you have already sold to someone else.
Pay at table collapses that to whenever the guests are ready, without anyone having to hover.
Large mixed groups are normal in central London and splitting is where service time disappears. Guests split by item or evenly on their own phones, which removes both the queue at the card machine and the awkward table maths.
London guests are attentive to how service charge is presented and tourists frequently ask. Showing it clearly at the point of payment removes a conversation your floor does not have time for.
Move the sliders to your own numbers. The point is not our figures โ it is how little the uplift has to be before the subscription pays for itself.
5% is the conservative default. WowMenu pilot restaurants have reported considerably more, but your own number is the one that matters.
An estimate based on the figures you entered, not a forecast or a guarantee. Actual results depend on your menu, your guests and how the platform is set up.
Yes, by item or evenly, from their own phones.
Yes, clearly at payment, and you control how it is applied.
Yes โ pay at table is optional and can be enabled per service.