Restaurants and cafés
One table tent. Every service.
The tent on the table is the same all day. What people find when they scan it shouldn't be. Here's a café's whole week on one code, live.
Scan it
This is a real code. It's on a real schedule.
The demo café runs six services a day. Scan the card and you land on whichever one is on right now, with a note saying which rule sent you. Scan it again after the next switch and you land somewhere else. The card didn't change.
The strip under it is the week, in your time zone. Bronze is a rule doing its job; the darker the bronze, the later the service.
Right now this code sends people to the menu.
At 4:00 PM it switches to happy hour.
Shown in your time zone. The café keeps Chicago time.
Open where it points right now or scan it. Same code, every day of the year.
The worked example
A café's day, as rules.
Six rules, one exception, one fallback. Twenty minutes to set up. Each destination here is a LinkShift hold page, a small hosted page with a title and a line of text, so you don't even need six web pages to start.
What changes for you
Three things you stop doing.
Reprinting for a menu change
Change the destination, not the tent. The print shop stops being on your critical path for a price change.
Explaining the hours
Closed Monday, brunch on weekends, the holiday week: that's a schedule with exceptions, set once in October, and the code does the explaining.
Guessing what worked
Scans are counted by which rule was active, so you can see whether anyone looks at the happy-hour list, by hour, by day.
Twelve tables
One schedule, many tents.
Twelve tables don't need twelve schedules. Make one "dining room" schedule and have every tent follow it. When table nine gets a birthday party, give that one code a rule of its own for the evening; its own rules win, and tomorrow it's back with the room.
Bigger than one room? The plans grow by how many things you've printed, never by scans. A second location is a second schedule, and the same person can run both.