Questions before the event goes live.

When a guest selects seats, those seats become temporarily unavailable for others. The hold timer gives the guest time to complete the next step, while protecting the event from seats being blocked forever.

Seats may return if the hold timer expires, if a payment notice is cancelled, if the organizer releases the reservation, or if the booking rules are not completed in time.

Yes. ShoofTix can apply limits per mobile number, guest type, row, seat category, or event policy. This is useful for parent-only events, private shows, academy events, and controlled community access.

For live seat maps, guests should complete one reservation flow at a time. Opening multiple flows may create confusion around which seats are actually being held or confirmed.

Yes. Seats may become available again when a hold expires, when an organizer releases seats, when unpaid bookings are cancelled, or when the event team updates the seating plan.

The organizer sets the ticket price, seat categories, free seats, paid extras, and commercial rules. ShoofTix provides the reservation, confirmation, QR ticketing, scanner, and analytics layer.

No. ShoofTix does not need to decide the face value. The event owner defines the price and the event policy, while ShoofTix helps manage the operational flow.

Yes. An event can include free package seats, paid extra seats, private rows, public rows, invite-only seats, or different seat rules depending on the audience.

Yes. ShoofTix can display the organizer’s own Instapay, wallet, or bank transfer instructions. The guest sends a payment notice or receipt, and the organizer confirms the booking from their own page.

ShoofTix can operate without forcing a card gateway by default. If the organizer chooses direct payment, the money goes through the organizer’s own channel. Any bank, wallet, transfer, or provider fees depend on the payment method used.

Depending on the event, the organizer may apply different seat categories, paid extra seats, taxes, handling rules, printed ticket options, or custom event conditions. ShoofTix can make those rules visible in the booking flow.

Yes. This is one of the strongest ShoofTix flows. A guest can mark that they paid or send proof, then the organizer reviews the payment and releases the QR ticket after confirmation.

The organizer can review reservations, see payment notices, confirm paid bookings, cancel invalid holds, track pending seats, resend tickets, and follow the live status of the event.

Yes. ShoofTix is policy-based. Events can have parent-only rows, invite-only access, maximum seats per mobile number, free seats, paid extras, hold timers, or manual approval before QR release.

It means the guest has submitted a payment notice. It does not automatically confirm the ticket. The organizer still reviews the payment proof or transfer details before confirming the booking.

The QR ticket is released after the event rules are satisfied and the organizer confirms the reservation. This helps protect paid events, private events, and manual payment flows.

Yes. ShoofTix can show paid seats, pending payment notices, confirmation speed, cancelled holds, expired reservations, revenue by category, and progress toward event capacity.

Each QR ticket can be checked against live ticket status. The scanner can identify valid tickets, already-used tickets, cancelled reservations, pending payments, or tickets for the wrong event.

The first valid scan can mark the ticket as used. After that, another scan can show that the ticket was already used, helping the entry team prevent duplicate entry.

Yes. ShoofTix can separate roles such as owner, payment reviewer, scanner team, and event admin, so every team member sees only what they need.

Yes. With QR scanning enabled, the organizer can track scan time, entry status, already-used tickets, cancelled tickets, and invalid scan attempts.

ShoofTix collects only what the event flow needs. This may include guest name, mobile number, email, selected seats, reservation status, payment proof, ticket status, and QR scan logs.

This data is needed to operate the event: holding seats, preventing duplicate bookings, showing pending payments, releasing QR tickets, validating entry, and giving the organizer a clear event record.

No. Guest and reservation data should be visible only to the event team roles that need it. Future organizer workspaces can separate access by owner, payment reviewer, scanner team, and admin.

Yes. ShoofTix can connect reservations, payment notices, organizer confirmation, ticket release, and QR scanning so the event team can detect pending, cancelled, duplicated, or invalid activity.