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.
Continue reading “Kiosk Idle Timeout: What Happens When They Walk Away…”
In this article we’re going to plan an example payment kiosk workflow which can be easily adapted to fit your specific requirements. If you’re designing your first payment kiosk, this is a good starting point.
A kiosk workflow is simply an outline of the screens your customers will encounter while using your kiosk. This is a quick and easy way to get your ideas “down on paper”.
By the end of this article you’re going to end up with an easy to understand payment kiosk workflow which you can share with your designers to create user stories and wireframes.
Steps for creating a kiosk workflow…
- List the all the kiosk features
- Separate features into MVP Kiosk features (initial release) and Rev 2 features (subsequent releases).
- Outline the kiosk workflow for the MVP kiosk. You can read more on the benefits of building an MVP kiosk if you’re curious.
Step 3 is what we’ll be covering in this article. Now that we have our kiosk features listed out (Steps 1 & 2), let’s put together a payment kiosk workflow which incorporates our desired feature set.
Continue reading “How to Plan Your Payment Kiosk Workflow”