Quantities, waitlists and tickets

The claim on a YURN offer is literally a numbered ticket: No. 004 of 012. This page explains the machinery behind it and how to use quantity limits well.

Setting a quantity

When you compose an offer you can set a quantity — 12 tables, 20 loaves, 50 tickets — or leave it unlimited. With a quantity set, the offer page shows a live count: “4 of 12 left” in ticket red. That number is real and it is exact: claims are serialized through a single authoritative counter, so two customers tapping Claim at the same instant can never both get ticket 12 of 12. The count on the page is the count in reality.

Unlimited offers work too — “30% off all weekend” doesn’t need a cap — but limited quantities consistently convert better, because the scarcity is visible and honest.

Sequence numbers

Every successful claim issues the next number in sequence. Your customer sees a perforated ticket stub with their number in large type:

✓ YOU'RE IN
No. 004
of 012
─ ─ ─ ─ ─ ─ ─ ─
Show this at the host stand before 8:00 PM

The number does two jobs. For the customer, it’s proof of a spot — something they hold, not just a message they got. For you, it’s redemption order: when someone shows ticket No. 004, you know exactly who claimed, when, and in what order. Numbers are issued once and never reused, even if the offer later reopens.

When it sells out

The moment the last ticket is claimed, the offer page flips to a sold-out state with a waitlist. Latecomers can still tap — instead of a claim, they get a waitlist position:

• Waitlist tickets carry their own numbers, in order of arrival.
• If a claimed spot goes unused (a no-show, a canceled table), release it from the Ticket book on the offer page, and the first waitlisted customer is called up in order.
• A customer’s waitlist page tells them plainly: “If a spot opens, your number is called in order. Keep this page.”

The waitlist turns your sold-out moment — usually a dead end — into a measure of unmet demand. Twelve tables and thirty on the waitlist is the strongest possible signal to run the offer again, bigger.

The ticket book

Every offer’s page in your portal has a Ticket book: each claim by number, who holds it (first name and last four digits), when it was claimed, and its status. Two actions live there:

• Redeem — the customer showed their ticket; mark it used. This fills the redeemed stage of your funnel.
• Release — a no-show. The slot is freed atomically: the first waitlisted ticket is promoted to a real one, and that customer gets a text — “A spot opened - your waitlist ticket is in!” — with their ticket link. Promotion texts ride the normal pipeline: quiet hours are respected, and anyone who replied STOP is promoted silently without a message. If nobody is waitlisted, the freed slot goes to the next person who taps Claim.

A released ticket’s page flips to a Released state, so it can’t be shown at the counter twice.

Redemption

Claiming is not payment. The customer shows the ticket in person and you honor it — that’s the whole transaction. Mark tickets redeemed from the Ticket book (or just honor them at the counter; redemption marking feeds your analytics but is never required). A claimed ticket that expires with the offer simply expires; nothing is charged to anyone, ever.

Practical guidance

• Undersize your first quantity. Selling out 10 in an hour teaches you more than 100 sitting half-claimed.
• Match quantity to real capacity. The trust you build by honoring every ticket is the asset.
• Let the countdown work. The offer page shows time remaining; pair a real quantity with a real deadline and let both numbers do the selling.