Appointment request card — worked example
Last updated: October 11, 2026
Cedar Family Dental keeps a card by the reception desk and one on its door poster: name, phone, a preferred weekday. It is a request, not a booking engine — the front desk works the list in order, and the phone queue stops being the calendar. Nothing on the card stores more than the practice asked for.
Card preview renders in your browser
Sample data：Scan the code on this page — it opens this page. That is the "url never dies" trick in one motion. Everything on the card is fictional; your own version takes your name in the workbench.
Start from a card like this →What happens after the scan
ON THEIR PHONE
One action, ten seconds
Any camera opens the card: no app, no login, no form six questions deep.
ON YOUR SIDE
The answers, live
Submissions land on the data page as they arrive — with the state the card promised: spots left, full, or waitlist.
One question this sample gets asked
Isn't health information sensitive?
Which is why the card asks three fields and nothing more — no diagnosis, no history. The list lives on the practice's data page, and deleting the card deletes the submissions with it.