A bookshop in Kyoto: a playbook for an author evening
Seats booked from a code in the window, the event page in Japanese or English, and a reading list that outlives the night.
An example of how a business like this could use QRiva — not a customer story.
A small independent bookshop on a quiet street holds an author evening every month or so, with room for a few dozen chairs. Seats, languages and the follow-up are the work; the evening itself is the easy part.
Before
Three weeks out
Seats, booked from the window
A poster in the window with a code to a form with a booking field: one slot for the evening, its capacity set to the chairs. When they're gone, the slot stops being offered.
Japanese or English, by the phone
Smart routing on the phone's language sends Japanese phones to the Japanese event page and everyone else to the English one.
A confirmation that answers questions
Each booking becomes a lead. An automation e-mails the person the address, the time and a map link.
During
The evening
The books on the table
A table card opens the evening's page: the books discussed, each in a product block with a short note.
Questions from the room
A one-question form for the audience; the host reads the questions out from a phone.
After
The week after
The reading list stays
The event page becomes the evening's reading list, and the window poster's code now opens it.
Which languages came
Analytics shows the languages of the phones that scanned the poster: a fair guide to whether the next evening needs an interpreter.
The next evening
People who booked are in Leads, tagged with the evening. Those who ticked the consent box can be exported as a CSV for the shop's own newsletter.
Bookings, language routing and automations are on Pro. A shop that only needs the poster and one event page can do that on Free.
More use cases
Ceramics studio
Three codes at a ceramics studio in FesYoga studio
A yoga studio in Bali, set up in five steps
Try your own version
Start free with one dynamic code, a page, a card and a form. Upgrade when the use case needs it.