[warmly] This is the Tevalis self-service kiosk, with Burger Bite. Let’s follow seven customer journeys, from ordering a favourite to completing an ID check.

First, a quick order. We choose eat in and find the Classic Bite. Clear categories and product images help us decide quickly. Adding it updates the basket total, so the cost stays visible. At checkout, extras and a collection name are optional, keeping the route simple. We choose card and complete the simulated payment. A clear confirmation and order number tell us the order has gone through.

Customisation separates required decisions from optional extras. The main action tells us when a patty choice is still missing. We choose a double, add cheese, and remove the onion. The price updates as we go, so changes have a visible cost. Our selections appear in the basket, making the result easy to check.

Meal building breaks a bigger decision into smaller steps: burger, side and drink. We choose fries with ketchup, then a cola. Showing one stage at a time keeps the screen focused. Before adding the meal, a summary brings all three parts together, giving us a chance to check the combination.

For products without modifiers, we give that space to useful information. The vanilla shake opens with allergens and available nutrition already visible. Customers can check the milk allergen and calories without another tap. Quantity and the main action stay within reach, so the simple product stays simple.

The basket supports changes without starting again. We can edit an item, and eligible combinations offer a meal swap with the saving shown up front. Accepting preserves our choices, including larger fries and cola with no ice. [short pause] Undo restores the original items. That makes the saving easy to try, while keeping the customer in control.

An age-restricted product introduces an ID check before payment. In the counter route, both the product and basket flag the requirement early. The next screen explains the handoff: take a ticket, show ID, and pay with a team member. Saving and printing the order leaves it clearly marked not paid. That distinction prevents a saved order being mistaken for a completed purchase.

The alternative brings a team member to the kiosk. Request updates reassure the customer that help is coming. Staff sign in before recording the ID decision, keeping that action with the team. Approval then unlocks the payment choices. The approved screen still says not paid yet, so completing an ID check never implies that payment has also been taken.

[warmly] Seven journeys, with clear choices and clear outcomes. This is a prototype: payment, printing and staff integrations are simulated.
