Customers don’t always behave as we would expect when using our kiosks. In the context of software, this is referred to as the “happy path” where everything goes according to plan.
As kiosk software developers we also must plan for what we’ll refer to as the “sad path.” This is when the customer deviates from the expected behavior.
In this article we’re going to be covering the case where the customer walks away from our kiosk in the middle of their transaction.
Obviously, we don’t want the next customer to continue where the previous customer left off. The new customer needs a fresh start and it would be confusing if they walked up and the kiosk is in the middle of a transaction.
Let’s start by first talking about why customers might abandon their kiosk transaction.
This article is a cautionary tale about one of the costliest and easily avoidable mistakes companies make when developing their first payment kiosk.
One of the most common calls I get as a kiosk consultant is from a project manager or developer asking me how to integrate some payment device (i.e. a bill acceptor) into their kiosk application.
If you’re asking this question, then you messed up a long time ago.
Self-service kiosks are everywhere from street corners to grocery stores and hackers are gunning for your customer’s data. Payment kiosks in particular are attractive targets because cardholder data is easy to monetize.
In this article I’m going to cover several techniques for hardening your kiosks security. Many of these kiosk hardening techniques involves functional changes to your kiosk application, so you’ll need to get your developers involved.
It’s Sunday morning and you’re fiending for a Sausage Egg McMuffin as you walk into McDonald’s. Near the checkout line you’re faced with a row of self-service kiosks and the choice to either order from a kiosk, or a cashier.
That first screen you see on the kiosk (the kiosk attract screen) is a major determining factor in influencing if you opt to order from the kiosk, or the teenager behind the counter.
Since the point of deploying our kiosk is to promote self-service, using the kiosk is obviously the desired outcome. In this article I’m going to cover the key components for creating an engaging kiosk attract screen to help your customers choose your kiosk over interacting with your staff.
Your kiosk attract screen must incorporate the following:
If you’re planning to run your website on a public facing PC or tablet, it’s not hard to imagine what could go wrong if a malicious user were to hijack control of your web browser. KioskSimple is the kiosk browser lockdown software designed specifically to secure your web browser.
In this article, we’re going to cover how to use Google Forms on a kiosk. Since Google Forms kiosk mode does not exist, we decided to create an easy solution for easily and securely deploying Google Forms to a kiosk or tablet.
The process is simple, first you’ll create your Google Form and then deploy it to your kiosk using the browser lockdown software KioskSimple.
KioskSimple makes it a breeze to securely deploy Google Forms in kiosk mode and helps prevent malicious user tampering.