Why some self-service deployments fail | Kiosk Marketplace
Customer Experience
Why some self-service deployments fail
Some self-service deployments reduce lines, improve throughput and give customers a convenient way to transact. Others sit unused, generate complaints or eventually disappear from locations altogether.
September 1, 2026 by Richard Slawsky — Editor, Connect Media
A technically capable kiosk can still be a failed deployment.
Some self-service deployments reduce lines, improve throughput and give customers a convenient way to transact. Others sit unused, generate complaints, require frequent employee intervention or eventually disappear from locations altogether.
The difference often has less to do with the hardware than with decisions made before and during deployment. Poor placement, confusing interfaces, insufficient employee training, payment problems, accessibility shortcomings, integration difficulties and unrealistic expectations about return on investment can undermine an otherwise capable system.
Dr. Gleb Tsipursky, a behavioral scientist and author of “The Psychology of AI Adoption at Work,” said in an email interview that one of the biggest mistakes is approaching a kiosk deployment primarily as a technology installation instead of recognizing the changes it creates for customers and employees.
“Self-service fails when the technology is installed but the surrounding work system stays the same,” Tsipursky said. “Confusing interfaces, weak staff training, poor exception handling and unrealistic ROI assumptions reinforce one another.”
Location still matters
One of the simplest deployment mistakes is also one of the easiest to overlook: putting the kiosk in the wrong place.
A kiosk needs to be visible at the point where customers naturally encounter the need for it. A check-in kiosk hidden around a corner or a restaurant ordering kiosk positioned away from the entrance may require customers to change their normal behavior simply to find the technology.
Traffic flow matters as well. A kiosk placed in a high-traffic area can create congestion rather than eliminate it, particularly if customers form lines that interfere with entrances, traditional service counters or other kiosks.
Dmitrii Pshenin, product designer and founder of marketing agency Ligeniqo, said in an email interview that operators can underestimate the importance of the environment surrounding a kiosk. A system can function properly but still underperform because customers do not notice it, glare makes the screen difficult to read or lines prevent easy access.
“The best way to improve a deployment is to observe real users in the actual environment, not only test the interface in a quiet lab,” Pshenin said.
Pilot deployments can help operators identify those problems before they are replicated across dozens or hundreds of locations.
The interface asks too much of the customer
Customers generally do not approach a kiosk to learn a new piece of technology. They want to accomplish something.
Every unnecessary screen, unclear instruction or confusing menu adds friction.
Paul DeMott, chief technology officer of Helium SEO, said in an email interview that his company has built digital ordering systems for 14 restaurant chains and has taken over several unsuccessful kiosk projects. In his experience, confusing interfaces cause more deployment failures than the hardware.
DeMott pointed to a fast-casual restaurant chain whose kiosks had a 62% order completion rate two months after deployment. Video showed customers selecting incorrect categories, becoming frustrated and leaving without placing orders.
The interface had been tested by the vendor’s software developers rather than typical customers, he said.
After the ordering flow was redesigned with larger buttons, descriptive labels and a single-column layout, the completion rate rose to 91% within three weeks
The experience demonstrates why usability testing should involve actual customers before kiosks are rolled out widely.
Employees can make or break the deployment
Self-service projects are often presented as customer-facing technology initiatives, but employees play a major role in whether customers adopt them.
Workers need to understand what the kiosks do, how customers are expected to use them and what to do when something goes wrong.
Without training, employees may unintentionally discourage kiosk use. A worker who immediately directs customers to a traditional counter, for example, can undermine an organization’s effort to establish self-service as a normal transaction channel.
Employees also need procedures for handling payment failures, frozen screens and other exceptions.
Tsipursky recommends measuring employee intervention rather than relying solely on transaction counts to evaluate a deployment. If workers repeatedly have to help customers at the same point in a transaction, the kiosk may simply be moving work from one place to another instead of eliminating it.
Tracking where customers stall and where employees intervene can help operators determine whether the underlying problem involves interface design, training, integration or the business process itself.
Payments create a critical failure point
A kiosk can perform flawlessly until the moment the customer tries to pay.
Payment failures are particularly damaging because they occur at the end of the transaction, after the customer has already invested time using the system.
Problems can stem from payment terminals, software, network connectivity, processor integrations or support for particular payment methods. Customers increasingly expect contactless cards and mobile wallets alongside traditional card payments, and an inability to accept their preferred method can lead to abandoned transactions.
But operators also need to design for transactions that do not proceed as expected.
Pshenin said development teams frequently test an ideal customer journey: A person approaches the kiosk, understands the interface, completes the transaction and receives confirmation.
Real customers behave differently. They may be in a hurry, make a mistake, encounter unfamiliar language or have a card declined. If the kiosk does not clearly explain the problem and tell customers what to do next, they may simply abandon the transaction.
Accessibility cannot be an afterthought
Accessibility problems can exclude customers and expose organizations to legal and reputational risks.
A touchscreen positioned too high for a wheelchair user, an interface that depends entirely on visual information or controls that cannot be used by someone with limited dexterity can turn self-service into a barrier.
Accessibility considerations should begin during system design and procurement. That can include physical reach ranges, screen positioning, tactile controls, audio output, text size, contrast and alternative methods of navigation.
Laura Boniello Miller, a former co-chair of the Kiosk Manufacturer Association’s accessibility committee, wrote in a 2019 Modern Restaurant Management essay that accessibility is integral to deployment success.
“Doing so in a manner that is accessible is critical to the success of these kiosk deployments and will well-serve both the restaurant and its guests,” Miller wrote.
Retrofitting accessibility features after hundreds or thousands of kiosks have been installed can be considerably more difficult and expensive than incorporating them from the beginning.
Integration problems surface after installation
A kiosk rarely operates independently.
Restaurant kiosks may connect with point-of-sale systems, kitchen display systems, loyalty platforms and payment processors. Retail kiosks can require access to inventory, pricing and customer databases. Hotel and transportation kiosks may communicate with reservation or ticketing platforms.
The more systems involved, the more opportunities there are for something to go wrong.
A kiosk might successfully accept an order but fail to send it properly to another system. Pricing information may not synchronize. Loyalty accounts may not update correctly. A software change elsewhere in the technology stack can unexpectedly disrupt the kiosk.
Successful deployments, therefore, require more than hardware testing. Organizations need to test the complete transaction journey from the customer’s first touch through every back-end system involved.
ROI expectations can be too optimistic
Another common mistake is expecting too much from self-service technology.
Organizations may justify kiosks primarily through anticipated labor savings. But installing self-service does not necessarily eliminate labor. Employees may still need to assist customers, replenish supplies, clean equipment, resolve technical problems and handle transactions that cannot be completed through the kiosk.
The financial calculation should also include software licensing, payment processing, connectivity, installation, integration, maintenance, field service and eventual hardware replacement.
Ben LoBue, director of revenue operations at experiential marketing platform Snapbar, said in an email interview that unrealistic projections can undermine perceptions of a deployment even when the kiosk performs reasonably well.
“We deliberately quote around nine to 10 captures an hour and let clients add capacity mid-event, because a kiosk that beats a conservative estimate gets renewed and one that misses an optimistic one gets blamed, even when the two performed identically,” LoBue said.
The lesson extends beyond event kiosks. Operators need realistic benchmarks established before deployment and a clear understanding of what constitutes success.
Failure often begins before installation
Warning signs can appear long before the first customer touches the screen: unclear objectives, inadequate customer research, insufficient integration testing, no accessibility plan, limited employee involvement and financial projections based on assumptions rather than measurable operating data.
That makes the pilot stage particularly important. Operators can measure transaction completion rates, abandonment points, intervention rates, transaction times, uptime and customer adoption before committing to a large rollout.
And deployment is only the beginning.
Nicolas Bak, business development director at Move On Tech Service, wrote in response to a LinkedIn query that even a kiosk with a good location, strong user experience and reliable payments can underperform if operators have not planned for field service, replacement parts, technician coverage and response times.
“The install is only day one,” Bak wrote. “What happens on day 200 matters just as much.”
Ultimately, the most successful self-service projects treat the kiosk as one component of a larger customer and operational experience.
Hardware matters. Software matters. But so do employees, customers, payments, accessibility, physical space and the systems operating behind the screen.
When those pieces work together, self-service can deliver substantial benefits. When they do not, even an impressive kiosk can become little more than an expensive screen that customers walk past.
ADA ComplianceHardwareSoftwareCustomer ExperiencePayments
About Richard Slawsky
In addition to writing, Slawsky serves as an adjunct professor of Communication at the University of Louisville and other local colleges. He holds both a Bachelor’s and a Master’s degree in Communication from the University of Louisville and is a member of Mensa and the National Communication Association.
Related Media
Blog
Troubleshooting Slow Adoption to Your Kiosk Pilot
Article
The human touch: How kiosks are transforming retail, restaurants
Blog
How to build kiosks for high-traffic environments
Blog
5 small kiosk trends worth watching
Article
A look back, and a look ahead
Blog
Building Kiosks for High-Traffic Environments
SoftwarePresented ByPROVISIO LLC
Blog
How Self-Service Kiosks Drive Customer Behavior and Increase Sales
Blog
Is Your Kiosk Network Missing Something? The Case for Kiosk Management
Blog
Measuring Kiosk Performance: Are Your Kiosks Meeting Customer Expectations?
White Paper
Simplifying Digital Signage Content Management
Presented by PROVISIO LLC
