How does it handle a customer calling to cancel a reservation last minute during a rush?

Voksha takes the cancellation details, confirms them back to the caller, and alerts your team straight away so the host can free up the table rather than holding it for a no-show they're still expecting. This matters more during a rush than it sounds, a host who's holding a table for a 7pm reservation that actually canceled at 6:45 but doesn't know it yet is losing seating capacity during the exact window it's most valuable, potentially turning away a walk-in party that would have taken that table.

For restaurants with a deposit or cancellation policy, common for larger parties or peak nights like Valentine's Day and New Year's Eve, Voksha applies whatever window and fee structure you've set, if a cancellation falls inside a 24-hour or same-day window where a deposit is forfeited, it explains that clearly to the caller, and can flag it for a manager if the caller pushes back and wants an exception.

The practical benefit during a genuine rush is speed: a canceled 7pm table that your host knows about by 6:45 instead of discovering it by a confused host at 7:05 when the party never shows gives your team a real shot at reseating it, especially on a night with a waitlist. This small-sounding step has real revenue impact on your busiest nights specifically, since that's when an unexpectedly open table is worth the most and the most likely to otherwise sit empty because nobody knew it was free.