[{"data":1,"prerenderedAt":242},["ShallowReactive",2],{"marketing-blog-blog\u002Fdesigning-a-kiosk-flow-people-finish":3,"marketing-blog-related-blog\u002Fdesigning-a-kiosk-flow-people-finish":223},{"id":4,"title":5,"author":6,"body":7,"category":201,"date":202,"description":203,"draft":204,"extension":205,"image":206,"imageAlt":207,"imageCredit":208,"imageCreditUrl":209,"meta":210,"navigation":211,"path":212,"readTime":213,"seo":214,"stem":215,"tags":216,"__hash__":222},"blog\u002Fblog\u002Fdesigning-a-kiosk-flow-people-finish.md","Designing a kiosk flow people finish","The CheckInHub team",{"type":8,"value":9,"toc":191},"minimark",[10,14,17,22,25,28,32,35,38,61,64,70,74,77,80,147,150,154,157,160,164,167,181,185,188],[11,12,13],"p",{},"A self-check-in kiosk that nobody finishes is worse than no kiosk at all. It looks like a solution, so you staff the door lightly, and then half your guests abandon it halfway through and turn to the steward you were trying to free up. Now you have a queue, a frustrated crew member, and a screen flashing an error that the next person has to clear before they can start. The kiosk has become the bottleneck it was meant to remove.",[11,15,16],{},"The difference between a kiosk that works and one that gathers a crowd of confused guests is almost entirely in the flow. Hardware matters far less than people think. What matters is whether a tired person who has never seen your screen before can get from the first tap to a printed badge without stopping to wonder what to do next.",[18,19,21],"h2",{"id":20},"design-for-the-worst-guest-not-the-best","Design for the worst guest, not the best",[11,23,24],{},"Your kiosk will be used by people who are early for a meeting, mildly stressed, holding a coffee in one hand, and not inclined to read. They will not study instructions. They will tap the biggest thing on screen and hope it is right. If your flow assumes patience and attention, it will fail in exactly the conditions a real door creates.",[11,26,27],{},"So design for that person. Every screen should make the next action obvious within a second or two of glancing at it. If a guest has to read a paragraph to know what to do, the screen has already lost them. The test is not whether the flow is logical to you, who built it; it is whether it is unmissable to someone who is barely looking.",[18,29,31],{"id":30},"cut-every-step-you-can-justify-cutting","Cut every step you can justify cutting",[11,33,34],{},"The number of steps between arrival and finish is the strongest predictor of completion. Each tap is a place where someone can hesitate, misread or give up. Treat every screen as a cost you have to justify.",[11,36,37],{},"A lean self-check-in flow usually looks like this:",[39,40,41,49,55],"ol",{},[42,43,44,48],"li",{},[45,46,47],"strong",{},"Identify."," Scan a QR pass, or look up a name. One action, done.",[42,50,51,54],{},[45,52,53],{},"Confirm."," Show the matched details so the guest knows they are the right record. A single yes.",[42,56,57,60],{},[45,58,59],{},"Collect."," Print or display the badge, or simply confirm they are checked in.",[11,62,63],{},"Three steps. Anything you are tempted to add between them, ask whether it has to happen at the kiosk. Dietary requirements, session choices, marketing consent: most of it can be captured at registration, not at the door with a queue forming. The door is for getting in, not for filling in forms.",[65,66,67],"blockquote",{},[11,68,69],{},"Every screen a guest does not have to read is a guest who finishes.",[18,71,73],{"id":72},"handle-the-unhappy-path-on-screen","Handle the unhappy path on screen",[11,75,76],{},"Happy paths are easy. The flows that send guests to a steward are the unhappy ones: a name that is not found, a code that will not scan, a pass already used. These are where completion rates collapse, so they deserve more design attention than the smooth case, not less.",[11,78,79],{},"For each failure, the screen should do two things: explain what happened in plain words, and offer an obvious way forward that does not require a human.",[81,82,83,99],"table",{},[84,85,86],"thead",{},[87,88,89,93,96],"tr",{},[90,91,92],"th",{},"What goes wrong",[90,94,95],{},"Poor response",[90,97,98],{},"Better response",[100,101,102,114,125,136],"tbody",{},[87,103,104,108,111],{},[105,106,107],"td",{},"Name not found",[105,109,110],{},"\"No match\" and a dead end",[105,112,113],{},"Offer \"register here\" or \"find me by email\"",[87,115,116,119,122],{},[105,117,118],{},"Code will not scan",[105,120,121],{},"Spinning loader forever",[105,123,124],{},"Fall back to a name search after a few seconds",[87,126,127,130,133],{},[105,128,129],{},"Pass already checked in",[105,131,132],{},"A red error the guest cannot clear",[105,134,135],{},"\"You are already checked in, here is your badge\"",[87,137,138,141,144],{},[105,139,140],{},"Guest taps the wrong thing",[105,142,143],{},"Stuck on a sub-screen",[105,145,146],{},"A persistent home or back control, always visible",[11,148,149],{},"The principle behind the right-hand column is the same throughout: never leave a guest at a dead end. A self-service flow earns its keep precisely when it handles the awkward cases without a human, because those are the ones that otherwise generate the queue.",[18,151,153],{"id":152},"make-the-finish-unmistakable","Make the finish unmistakable",[11,155,156],{},"People abandon kiosks not only at the start but at the end, because they cannot tell whether they are done. A guest who is uncertain whether check-in worked will go and ask, which defeats the purpose. The final screen has to say, plainly and largely, that they are checked in and what to do next.",[11,158,159],{},"A clear finish does three things: confirms success in a way visible from a step back, shows the one piece of information they need now (\"you are in, the keynote is in room two\"), and resets itself for the next person within a few seconds so the device is never left mid-flow. That automatic reset matters more than it sounds. A kiosk stuck on someone else's confirmation screen is a kiosk the next guest does not trust.",[18,161,163],{"id":162},"place-the-kiosk-where-the-flow-can-breathe","Place the kiosk where the flow can breathe",[11,165,166],{},"Even a perfect flow fails behind a badly placed machine. A kiosk jammed against the entrance with no room to stand creates a scrum; one tucked too far away gets ignored. Give each device clear space to approach, use and leave, with a steward visible but not hovering, ready for the rare case the flow cannot handle.",[11,168,169,170,175,176,180],{},"For the wider question of when kiosks are the right call at all, ",[171,172,174],"a",{"href":173},"\u002Fblog\u002Fwhen-self-check-in-kiosks-pay-off","when self check-in kiosks pay off"," sets out the economics, and ",[171,177,179],{"href":178},"\u002Fblog\u002Flocking-down-a-kiosk-without-locking-out-guests","locking down a kiosk without locking out guests"," covers keeping the device secure without breaking the flow you just designed.",[18,182,184],{"id":183},"the-closing-thought","The closing thought",[11,186,187],{},"A kiosk is a small piece of software a stranger has to operate, once, under mild pressure, with no training. Judge every screen by whether that stranger finishes. Cut the steps you cannot justify, design the failures as carefully as the success, and make the end so clear that nobody has to ask whether it worked.",[11,189,190],{},"Get the flow right and the hardware becomes almost incidental. CheckInHub's kiosk mode is built around finishing, not features, because a flow people complete is the only kind that actually takes work off your door.",{"title":192,"searchDepth":193,"depth":193,"links":194},"",2,[195,196,197,198,199,200],{"id":20,"depth":193,"text":21},{"id":30,"depth":193,"text":31},{"id":72,"depth":193,"text":73},{"id":152,"depth":193,"text":153},{"id":162,"depth":193,"text":163},{"id":183,"depth":193,"text":184},"Self check-in & kiosks","2026-01-09","A self-check-in kiosk only helps if guests get to the end of it. Here is how to design a flow people complete without asking for help.",false,"md","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1778229757765-7ae794a67b39?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop","A person checking out at a self-service screen","Permadi Creative","https:\u002F\u002Funsplash.com\u002F@permadicreative?utm_source=checkinhub&utm_medium=referral",{},true,"\u002Fblog\u002Fdesigning-a-kiosk-flow-people-finish",6,{"title":5,"description":203},"blog\u002Fdesigning-a-kiosk-flow-people-finish",[217,218,219,220,221],"kiosks","self check-in","self-service","ux","design","6EuICbFKBD9MFBFTeJ4Y9rmF7LEla4y-JM1QnP7y1go",[224,230,236],{"to":225,"title":226,"description":227,"date":228,"category":201,"image":229,"readTime":213},"\u002Fblog\u002Freducing-door-staff-with-unattended-check-in","Reducing door staff with unattended check-in","Unattended check-in lets a small team cover a busy door. Here is where it works, where it does not, and how to set it up well.","2026-04-17","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1702411739534-2961ba90fefd?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",{"to":178,"title":231,"description":232,"date":233,"category":201,"image":234,"readTime":235},"Locking down a kiosk without locking out guests","A self check-in kiosk has to be tamper-resistant and genuinely easy at the same time. The craft is in securing it without making it hostile.","2026-01-30","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1613652038578-a9a988b54a60?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",5,{"to":237,"title":238,"description":239,"date":240,"category":201,"image":241,"readTime":213},"\u002Fblog\u002Fthe-case-for-letting-guests-check-themselves-in","The case for letting guests check themselves in","Self check-in is not about cutting staff. It is about removing a bottleneck and giving guests control of their own arrival. Here is when it works.","2025-11-21","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1764795849694-34b3316b3de4?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",1782495586221]